Request lifecycle
1. Application declares intent and constraints2. Local input is extracted and sanitized3. PrivacyReceipt records the transformation4. Resolver selects context under budget5. Trust and policy gates evaluate the plan6. Router selects an allowed processing destination7. Only approved context reaches the model8. Receipts record delivery, route and outcome9. Future invalidations update caches and derivativesThe target enforcement vocabulary is deliberately limited:
| Decision | Meaning |
|---|---|
ALLOW | The request satisfies applicable technical policy. |
SANITIZE | Transform sensitive content before continuing. |
ROUTE_LOCAL | External processing is not permitted; use a local model. |
REQUIRE_HUMAN | A qualified reviewer must make or confirm the decision. |
DENY | The operation cannot proceed under the active policy. |