If approved in a real system
A matching next step could become eligible under a scoped lease. This demo only records browser state.
Try it: inspect each stage and the exact fixture bytes, then record a simulated decision.
dreq_demo_school_calendar · rev 3 · T3_PRODUCTION · PENDING · Expires 2026-09-05T17:43:04.114Z
WHERE THIS ILLUSTRATED TASK IS NOW
WHAT THIS SYNTHETIC REQUEST CONTAINS
T3 · T3_PRODUCTIONHigh-impact production action · T3
Requested action: deploy.release → demo://school-calendar/production
“Synthetic release of the calendar application to a non-real target.”
A matching next step could become eligible under a scoped lease. This demo only records browser state.
The illustrated request remains blocked. A new request or revision would be needed.
The request remains blocked. Expiry never becomes automatic approval.
UTF-8 · LF · no BOM · no trailing newline
Expected SHA-256sha256:922193aca529a904bc0a61e1ba23786c1e61fdc629a8127adc213284bc1aba6a
Computed SHA-256—
{
"action": "deploy.release",
"allow": ["app/calendar/**"],
"deny": ["credentials/**", "infra/**"],
"request_id": "dreq_demo_school_calendar",
"revision": 3,
"target": "demo://school-calendar/production",
"task_id": "task_demo_school_calendar",
"tier": "T3_PRODUCTION",
"tools": ["demo-deployer"]
}Decision controls remain locked until the displayed fixture hash matches.
This interface changes browser memory only. It does not send a request, create a VESOS record or start an executor. Running and receipt panels are separate synthetic read-only examples.
In a real integration, VESOS governs only actions routed through the connected enforcement point. The adapter and executor validate and enforce the actual command; the kernel never runs it.