← Back

Runtime Admissibility Core

Runtime Admissibility Core evaluates whether a requested execution remains legitimate under current runtime conditions.

Boundary

It does not determine final truth, make domain decisions, or grant legal permission. It recomputes whether the packet establishes enough current state, authority, constraint, and consequence context for execution to remain admissible.

Endpoint

POST /api/evaluate

Core packet shape

{
  "packet_id": "demo-001",
  "system_context": { "domain": "healthcare", "workflow": "discharge-readiness" },
  "runtime_state": { "state_valid": true, "last_validated_at": "2026-05-20T10:00:00Z" },
  "authority_context": { "status": "valid", "issuer": "attending-physician", "scope": ["discharge-review"] },
  "constraint_context": { "action_constrained": true, "allowed_actions": ["prepare-review"] },
  "consequence_boundary": { "level": "high", "scope": "clinical-discharge" },
  "runtime_signals": [{ "source": "monitor", "statement": "oxygen instability detected" }]
}

Outcomes

admissible — state, authority, constraints, and consequence boundary survive current evaluation.
conditional — execution may require warning, revalidation, or operator review.
inadmissible — execution legitimacy fails under the supplied runtime packet.

Customer access