Documentation / evidence

A decision is useful when its scope is clear.

Explore an implemented source path and a separate educational example. Neither is a new runtime trace or a claim of customer acceptance.

Source walkthrough

From a governed request to a recorded outcome.

Source rechecked October 21, 2026 at revision 52edd07d06f30acb4e67fb9b06b59ef2bba2a8ad. The following references describe inspected implementation. Product tests were not rerun.

1

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.

2

Resolve policy and prepare input

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.

3

Reject, hold, or reach eligible execution

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.

Tests and their limits

What the existing tests actually check.

Review hold before fake provider routing

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.

Rejection before provider selection

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.

What the code-backed test asserts

Review required. No simulated provider attempt recorded.

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.

Decision action
REVIEW_REQUIRED
Stored lifecycle state
quarantined
Review item
Present with the corresponding policy decision
Provider attempts in the test
0 (both record attempts and fake-store attempt writes)
Test dependencies
In-memory store and fake provider registry

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.

See the neighboring rejection test and its limits
Synthetic decision example

Three outcomes. One illustrative policy.

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.

Synthetic · educational illustration

Allow a request within the illustrative policy.

Input: synthetic support text already within the agreed data scope.

DecisionContinue toward the configured route
Reviewer inspectsPolicy, tenant binding and recorded outcome
Provider observationNo execution observation in this illustration
Test the represented boundary

Agree cases before asserting coverage.

Allow and transform

Compare the configured policy, provider-bound input and same-case task quality. Record the build, tenant and route. Detector completeness is not assumed.

Reject and hold

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.

Failure and bypass

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.

Reviewer checklist

Make the evidence answer one assertion.

  1. Requirement and authority: name the assertion, workflow and reviewer who can accept it.
  2. Boundary and configuration: record ingress, provider/egress, excluded paths, build, policy, tenant and environment.
  3. Observed decisions: provide allowed, transformed, denied and held cases within the permitted data boundary.
  4. Independent corroboration: include provider or boundary observations where needed for the claimed result.
  5. Utility and limitations: show workload provenance, holdout, quality, latency, failures, denominators and open defects.
  6. Conclusion: record accepted within scope, rejected or undetermined. Keep production permission separate.

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