Define the boundary before the call.

OCLITH2 min read

A task is not an unrestricted request

A caller may need a classification without needing source documents, credentials or internal rules. A useful capability interface describes that distinction before execution starts.

The Cell Manifest declares accepted input types, allowed return fields and withheld field groups. It also declares a request lifetime and a sample privacy budget limit. The owner can inspect all of these values before publication.

Check both directions

The first boundary check happens on the incoming request. It validates the task, selected fields, input scope, expiry, revocation state and available budget.

The second happens on the candidate result. Even a permitted request can receive an invalid response from an execution adapter. The Guardian must reject a result with undeclared fields rather than letting an upstream component widen the disclosure policy.

The local Console exposes both checks. Asking for a forbidden source field fails at the request boundary. A diagnostic candidate containing an extra field fails at the output boundary. Neither case proceeds to a successful Capsule.

Compile a concrete rule

The compiler validates a complete JSON Manifest, normalizes its field lists and computes a SHA-256 digest over canonical JSON. The policy digest excludes its own field. The same normalized policy therefore produces the same digest in the browser and server.

A stable digest answers a narrow question: is this the normalized policy that was recorded? It does not establish that a private runtime enforced it. Network and persistent memory flags remain declarations until the execution environment implements them.

Inspect the actual sample

Open the Policy tab to see a complete Manifest. Use the Console to modify and compile it, then observe which checks depend on the change.

Public sample rules make the mechanism reproducible. They are not confidential rules, and a clean pattern result is not a security certification. The boundary and the scope of the implementation should remain equally easy to inspect.

Read the privacy model.