From organizational intent to governed AI execution.

Coverage comes from the integration boundary. LSAS Platform does not universally intercept every network request, employee AI session, or autonomous agent.

1. 01

   Resolve Authority

   Identify the authenticated application, tenant, environment, assigned policy version, and permitted route. Resolve any recorded active alignment and the admitted provider destination.

   The caller's identity and server configuration establish the boundary. A prompt or client-supplied role cannot widen it.

   Application identity · Exact policy version · Authority checks
2. 02

   Inspect Input

   Validate supported text or JSON shapes and run configured checks before outbound work. Reject unsupported inputs; apply and recheck a supported transformation when the policy requires it.

   An unsafe or unsupported request can be stopped before it reaches an external service.

   Ingress findings · Required intervention · Actual input transformation
3. 03

   Bound Execution

   For an admitted provider call, bind the registered skill to its destination, policy context, deadline, and budget. Recheck authority around execution.

   Permission applies to a specific supported operation. Unsupported tools and destinations cannot expand the grant.

   Execution grant · Effect intent · Adapter result
4. 04

   Enforce Thresholds

   Evaluate the actual returned artifact with the selected policy and supported validators. Apply supported transformations on the server and revalidate the result.

   A rule that requests redaction is different from a redaction that was completed successfully.

   Egress findings · Transformations applied · Revalidation
5. 05

   Decide at Runtime

   Release eligible output, release a validated transformation, block it, or hold it. The supported nonclinical review profile requires approval of the exact artifact before release.

   A hold or escalation is not permission to release. Changed content, expired authority, or a different audience invalidates approval.

   Final disposition · Release or hold receipt · Exact artifact binding
6. 06

   Record the Decision

   Retain the policy context, rule findings, derived evidence, and execution receipts associated with the decision. Keep intermediate findings separate from the final release outcome.

   Reviewers can inspect which controls ran and what was released or withheld, within the recorded evidence scope.

   Correlated decision record · Policy provenance · Audit history

{
  "message": "Contact engineer@example.invalid about the sample project.",
  "nested": [{ "phone": 5551234567 }]
}

{
  "message": "Contact [REDACTED_EMAIL] about the sample project.",
  "nested": [{ "phone": "[REDACTED_PHONE]" }]
}

Permitted

ALLOW or ALLOW_WITH_WARNINGS may release eligible content. A warning can remain part of the evidence.

Redacted

Release requires a supported transformation and successful revalidation. An input redaction is distinct from the final output disposition.

Blocked

The boundary withholds the protected payload. A rejected request does not become a successful external action.

Held

An escalation, failed revalidation, or unsupported requirement withholds content. A hold does not mean a reviewer has approved it.

A recorded policy evaluation is evidence of the recorded controls. It does not automatically establish regulatory compliance, factual or clinical correctness, downstream delivery, or verified business outcomes.