Watch one governed action move from intent to evidence.
This demonstrator uses DGAF's existing bounded AAR_V1 admission validator and the real /api/audit effect path. Choose a valid or adversarial scenario and inspect what the system permits, blocks, executes, and records.
See the basic idea before learning the framework.
You do not need to understand DGAF's architecture first. Run these two cases and compare what changes.
The request has live, scoped authority and an untampered action binding. DGAF should admit it, execute the bounded effect, and emit a receipt.
The same kind of request carries revoked authority. DGAF should deny it before execution and produce no execution receipt.
The important behavior is not simply “allow” or “deny.” It is that execution and evidence remain downstream of explicit authority, the resulting receipt carries no continuing authority, and any consequential follow-on action requires fresh adjudication before new authority can be issued.
Now try the failure modes individually.
Canonical action
Run a scenario to bind an exact action class, target, policy, and parameters.
Delegation + status
Authority must be explicit, scoped, live, and separately verified.
Allow or deny
The validator checks attestation, revocation, expiry, delegation, required scope, verifier state, and action digest.
Not executed
Execution occurs only after admission.
No execution receipt
A denial does not masquerade as execution evidence.
No authority inherited
A denied or unexecuted attempt creates no follow-on authority.
What this result is allowed to mean
A successful bounded engineering demonstration does not promote scientific, independent-validation, efficacy, or High-Assurance state.
See the governed handoff without creating a live mutation path.
This section replays accepted DGAF and ACP semantics from exact source identities. It does not call ACP, mutate a repository, or claim that this cross-system chain executed live.
Measure context exposure without turning the dashboard into a router.
This projection shows accepted ACP characterization from a static local fixture. It does not gate tools, suppress context, invoke ACP, or claim a live-model efficiency result.