Decision workspace Evidence → reasoning → review
Does this decision still hold?
See what changed, follow the supporting records, and preserve the reason for your next decision.
How this workspace works
One source is stored once. Each decision keeps its own rule, review and outcome. Earlier workspaces retain their original formats.
Select a saved v7 continuation above or import its complete history below. To start a new case, create or restore a v6 rehearsal, then explicitly create its v7 continuation. This page does not migrate records automatically.
01 / Establish a shared baseline
Start with a decision you can trace.
Create three explicitly simulated starting decisions: a request boundary, a declared-grant boundary, and a production hold pending context. The synthetic baseline requests read, separately declares read granted, and leaves deployment Unknown. Nothing is saved until you submit.
Current workspace
Your decisions, in context.
Follow the evidence behind one decision. Current rule results and human reviews stay separate.
02 / Follow the consequence
Inspect supporting relationships.
Select any node to inspect exact references. The trail compares the latest capture with each applicable decision basis; earlier events remain in the history. It is not a replay of what was known at every past moment.
Clarification / preserve both questions
Earlier uncertainty. A separate reassessment.
Inspect the reasoning
Select a trail element.
Explore a source, evidence version, assumption, decision, review or outcome. Inspecting does not write records.
Decision basis / recorded history
What changed between recorded states?
Choose one decision and two recorded states to inspect their exact evidence, source declarations, reviews and outcomes. Separate the capture supporting the decision from the latest known capture and a pending review's frozen target. Selections stay in memory and write nothing. Reload starts with the Production decision and latest state at both endpoints.
An event endpoint shows preserved facts immediately after that event was recorded. Either endpoint can be latest, earlier or the same; comparison direction follows validated recorded references, not source capture-time sorting.
Historical views show preserved facts. Source receipt metadata belongs to its exact capture; missing or invalid metadata is not filled from a later revision. Rule versions were not recorded, so historical rule evaluation is unavailable. Declarations supply no source authentication or runtime assurance.
The v7 recorded-basis inspector includes evidence questions and human responses only when they had been recorded in the selected perspective. Satisfaction addresses the declared-context requirement; it does not replace the frozen review, approve production or change the decision basis.
Source file / inspect before capture
A new revision. An explicit next step.
Inspect one bounded synthetic JSON source file. Compare its declared fields against the latest saved capture and preview each decision's explicit rule. Nothing is uploaded, fetched or saved until you confirm capture.
- 01Choose a declared revision
One file, one canonical source.
- 02Inspect exact differences
Prospective impacts, no new records.
- 03Confirm a capture
Human review remains a separate action.
Use the downloaded source-file v1 template, maximum 8 KiB. This input accepts the defined synthetic artifact, not arbitrary documents or exported histories. Source references and timestamps are declarations; no live source is queried.
Inspect saved source-file receipts
Choose either source-file intake here or manual evidence entry below. Both append immutable captures; neither opens a review or records a human outcome automatically.
03 / Preserve the next capture
Record once. Compare across three decisions.
Enter synthetic evidence directly, or inspect a versioned source file above. For the demonstration, add a write request, retain read-only declared grants, and keep context Unknown. This produces affected, no relevant change, and unresolved applicability. No live system is queried. Pending reviews retain their exact earlier captures.
04 / Accountable reassessment
One outcome belongs to one decision.
When a later declaration clarifies a deferred review, preserve the earlier unanswered question and open a separate review explicitly. Replacement records responsibility and exact evidence links; it does not approve production. Return to the original v5 rehearsal.
Turn an unanswered question into a clear evidence requirement.
Create a separate v7 continuation to record what evidence a deferred production question needs, who is responsible, and which later capture a person evaluated. The original v6 history stays in its existing storage record. No requirement or human response is generated automatically.
Evidence requirement / a separate human response
What would answer the deferred question?
Turn a deferred Unknown production review into an explicit question, required evidence and a reassessment trigger. A person evaluates a later capture and records why it is sufficient or insufficient. Addressing the declared-context requirement does not change the decision, approve production or establish observed runtime behavior.
Continuation and original history references
1. Define the evidence needed
The selected decision in Human review determines the question. This first contract asks for a later capture declaring Production; explanatory text does not execute additional rules.
2. Record a human response
Capture evidence using the existing form above. Each response uses an exact later source event recorded at or after the requirement. An insufficient response remains intact; another attempt requires a newer capture than the one previously evaluated.
3. Preserve the question and every response
A satisfied requirement closes only this evidence question. Use explicit review replacement and a separately recorded human outcome to reassess the decision. Earlier deferrals, holds and evidence remain unchanged.
05 / Keep earlier reasoning
Shared evidence. Preserved histories.
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 original workspace. Different existing history cannot be overwritten.
Review before restoring
Consistency checks do not prove authenticity. Reviewer codes are unauthenticated; browser storage is editable.
Synthetic technical demonstration. No practitioner validation, live source monitoring, runtime assurance, authentication, cloud sharing or AI decisions.