Guard the request entry
The API controller requires submission permissions, ingress controls and schema validation for its governed request route.
apps/api/src/requests/requests.controller.ts, lines 50–104.
Explore an implemented source path and a separate educational example. Neither is a new runtime trace or a claim of customer acceptance.
Source rechecked October 21, 2026 at revision 52edd07d06f30acb4e67fb9b06b59ef2bba2a8ad. The following references describe inspected implementation. Product tests were not rerun.
The API controller requires submission permissions, ingress controls and schema validation for its governed request route.
apps/api/src/requests/requests.controller.ts, lines 50–104.
The pipeline normalizes the request, resolves policy with organization/workspace context and invokes stable policy evaluation and transformation.
packages/orchestration/src/process-enterprise-request.ts, lines 551–585.
The rejected branch returns at line 616. The review-required branch persists its queue/state and returns at line 648. The later provider-execution call is at line 672.
packages/orchestration/src/request-application-service.ts, lines 594–672.
This establishes source branch ordering. It does not establish actual provider nonexecution, complete egress coverage, durable production persistence or the behavior of alternate paths.
The request-service unit test checks that a review-required request is held, a review item records the policy decision, and no provider attempts are recorded. It uses in-memory storage and a fake provider registry.
A separate unit test asserts that a disallowed provider request fails before adapter lookup or an execution attempt. Its own evidence labels network egress as not proven.
packages/orchestration/test/request-application-service.test.ts, lines 1092–1132 and 1423–1487. Assertions inspected October 21, 2026; product tests were not rerun. These unit-test designs do not establish deployed egress prevention, durable persistence or behavior across every path.
This is an inspection of existing unit-test assertions, not an invented product receipt. At source revision 52edd07d06f30acb4e67fb9b06b59ef2bba2a8ad, the test named enterprise request application service unit quarantines review-required decisions before fake provider routing checks the following outcomes.
REVIEW_REQUIREDquarantined0 (both record attempts and fake-store attempt writes)Source: packages/orchestration/test/request-application-service.test.ts, approximately lines 1092–1132, at the revision above. The source assertions were inspected on October 21, 2026. This website update did not rerun the product suite or observe provider/network egress, customer operation or durable production storage.
Suppose an application prepares a tenant support summary. This hand-authored example explains a control decision; it does not run Clariva, call a provider or generate a real receipt.
Input: synthetic support text already within the agreed data scope.
Compare the configured policy, provider-bound input and same-case task quality. Record the build, tenant and route. Detector completeness is not assumed.
Observe the actual execution boundary independently. Log absence alone does not establish no provider call. Review hold needs a tested approval/resume process where included.
Exercise missing or malformed proof, replay, wrong tenant/route, outage, timeout, retry and fallback. Identify paths that are excluded and paths that could bypass Clariva.
A delivered evidence pack is not reviewer acceptance. An evaluation, annual agreement and authorized production operation are separate facts.
Review assurance and data-handling questions