Turnkeeper · synthetic walkthrough

Execution authorization

Any system may propose an action. Turnkeeper controls whether production may execute exactly that action — once — under the required decision process. This page is synthetic local fixtures only; not a hosted API and not GA.

Synthetic attack demo. No production authorization ledger, customer data, or enforcement call is used. Hosted issue/verify/consume APIs are Implemented behind default-off project gates (not generally available).

3. Matching execution

The enforcement endpoint presents the exact approved effect and receives ALLOW.

Approved effect

action: restrict_messaging
resource_ref: subj_user_8192
duration_hours: 24
parameter_digest: 012fcc42ca35488a…

Authorization artifact

artifact_id: authz_demo_restrict_match
audience: enforcement.prod
expires_at: 2026-08-07T13:00:00.000Z
nonce: nonce_authz_demo_restrict_match

Matching execution

ALLOW

Enforcement presents the same action, subject, and parameters. Digest matches; artifact is consumed.

Spine first. Vertical second.

Safety Intelligence and Ward feed high-stakes decisions into this boundary. Detectors and review tools may propose effects; production may execute only what Turnkeeper authorizes exactly once.

Ward Safety Intelligence walkthrough Turnkeeper Ward