This synthetic workflow demonstrates Nisaba's general gate: bind the claim to evidence, policy, authority, and current state before allowing action. Here, the gate blocks an unsupported release, repairs only failed records, completes the clear case automatically, or pauses for roles assigned by this example's policy.
Reading the public-safe trace.
The reference trace is sanitized and synthetic-only.
Every statement cites a validated source record. No model-written fact is canonical.
Evidence and policy judgment stay separate.
The available actions come from fixed policy and your assigned role.
Raw bytes and hashes remain available only inside technical details.
Loading the authenticated reference trace.
Loading the governed lifecycle receipts.
Loading execution scope.
These are logical Gemini/ADK roles. Authority is enforced by Nisaba's deterministic kernels, not by model prose or separate AI identities.
Run isolated attempts against the same kernels and inspect each refusal.
Identifiers, hashes and the append-only ledger are secondary to the business decision.