Loading Decision Continuity…

New decision + Repeated reassessment → Shared source impact →

Records stay in this browser and origin. Export to transfer history. Use fictional codes and synthetic material; do not enter identities or confidential evidence.

Your reasoning, kept in view

Give a decision
a traceable foundation.

Define the approval and its source. Capture a later version. Follow the exact assumption it challenges, then decide what changes.

01 / Establish the original basis

What are you approving, and why?

Create an original synthetic approval. The baseline requests documents:read only; declared grants are entered independently. Nothing is authenticated or observed at runtime.

Assigned for this rehearsal only. This code is not proof of identity or consent.
Structured rule: request-remains-read-only. A later documents:write request warrants reassessment; grants are a separate fact.
Interpreted as UTC; must not be in the future.
Baseline declared grants · independent of the request
Import history Inspect, then restore

Choose a Decision Continuity JSON export, maximum 1 MiB. Nothing is uploaded. Inspection writes nothing; confirmation restores only a missing record and opens its workspace. Different existing history cannot be overwritten.

Synthetic technical demonstration. No live source checks, real access revocation, authentication, remote sharing or operational assurance.