Skip to main content
Circular Deduction™

Dry Run · a guided decision rehearsal

Rehearse the decision before commitment.

Follow one infrastructure launch through seven explanations. Inspect the basis, the Human Authority boundary and what must happen next.

Go directly to the detailed decision view →

SYN-LAUNCH-01 v1.0 · D-01 · AUTHORED SYNTHETIC CASE

Can the initial phase launch?

Current method context: Reconcile · C2 unresolved

HUMAN AUTHORITY · ILLUSTRATIVE PROGRAM SPONSOR

HOLD

Commitment WITHHELD · no launch authorized

Before Frame · Materiality Gate — separate from the 6+1. This specimen does not establish a materiality category or select a route. Inspect the gate explanation →

Six decision states + one distinct adaptation state

Explore in any order. Selection changes the explanation only; it does not complete a state or change HOLD.

frame

Define the commitment first.

The decision, its boundary and the accountable role remain visible throughout the rehearsal.

Decision D-01

Authorize the initial launch phase?

Whether to authorize the initial phase of an infrastructure launch within the reconciled scope and funding basis, subject to verified supplier mobilization and required concurrence.

SYN-LAUNCH-01 v1.0 · authored scenario as of 2026-10-14.

Scope boundary

A specific commitment, with limits.

In scope
Initial-phase launch review.
Outside scope
Later phases, spending, contracting and operational execution.
Before reconsideration
Supplier evidence reviewed and applicable concurrence recorded.

Current basis: scope and funding aligned; supplier mobilization unverified. The illustrative program sponsor has recorded HOLD.

derive

Read the claim. Keep its limits.

Inspect the four source excerpts. Their inclusion in this authored example does not make them sufficient for launch.

E1 · Scope baselineReviewed within the authored fixture

SYN-SCOPE-01 v1.1 · fictional date 2026-10-14 · Program planning role

The launch package covers the initial phase only. Later phases are excluded and require separate review.
Can support
The bounded initial-phase scope; it does not prove delivery readiness.
Limit
Fictional baseline; it does not establish delivery readiness or authorize work.

Retained SYN-SCOPE-01 v1.0 · 2026-10-13
The scope includes the initial-phase launch and later-phase preparation.

E2 · Funding confirmationAligned to E1 within the authored fixture

SYN-FUND-01 v1.1 · fictional date 2026-10-14 · Funding owner role

The funding basis applies to the initial phase described in SYN-SCOPE-01 v1.1. It does not cover later phases or constitute a spending instruction.
Can support
The funding basis aligned to E1; it is not a spending instruction.
Limit
Fictional scope and funding reconciliation; no actual allocation or payment authority.

Retained SYN-FUND-01 v1.0 · 2026-10-13
The funding basis covers the initial phase only.

E3 · Supplier readiness claimSupplied claim; mobilization unverified

SYN-SUPPLIER-01 v1.0 · fictional date 2026-10-13 · Supplier lead role

Resources are expected to be available for the initial phase. The dated mobilization plan and crew availability evidence have not yet been provided.
Can support
That the supplier made a readiness claim; it does not verify mobilization.
Limit
A supplied claim is not verified readiness. Its falsity is also not established.
E4 · Applicable requirementsSource identified; concurrence applicability remains open

SYN-LAUNCH-CONDITIONS v1.0 · fictional date 2026-10-14 · Fictional source owner role

SYN-R01: confirm launch resources with dated mobilization and crew evidence. SYN-R02: establish and record applicable concurrence before a launch authorization is considered.
Can support
The identified fictional requirements; concurrence applicability remains open.
Limit
Requirements are fictional. The required concurrence scope remains unresolved; no legal or conformance finding.
A1 · explicit, unverified assumption: Required resources remain available through the intended mobilization window.
Owner: Supplier lead. E3 is the stated basis, not proof of availability.
Explore the five evidence admission checks →

contradict

Make the actual conflict visible.

Two different kinds of challenge remain distinguishable: a reconciled mismatch and an unmet evidence condition.

C1 · historical conflict

Earlier scope exceeded the funding basis.

E1 v1.0 included later-phase preparation. E2 v1.0 funded the initial phase only.

The earlier mismatch remains in the record after resolution.

C2 · current challenge

A readiness conclusion lacks required support.

E3 expects resources to be available. E4 requires dated mobilization and crew evidence, which is missing.

This challenges a launch-ready conclusion. It does not establish that the supplier claim is false.

Withholding an item from use does not erase its claim, its provenance or the unresolved concern. C2 remains in view.

reconcile

Resolve what is supported. Preserve what is open.

Reconciliation explains what changed in the basis and why the remaining condition still matters.

C1 · resolved, history retained

Scope and funding now reference the same phase.

E1 v1.1 excludes later phases. E2 v1.1 references that exact scope.

Recorded fictional review: 2026-10-14. Owner: Program review lead.

C2 · unresolved, bounded

Carry the launch dependency into the next action.

The missing mobilization and crew evidence remains a launch condition. Applicable concurrence also remains open.

Owner: Program review lead. No acceptable exposure limit or permission to launch is invented.

1 · ObtainSupplier lead supplies dated mobilization and crew evidence.
2 · ReviewReview lead assesses the evidence and establishes the concurrence route.
3 · ReconsiderThe sponsor makes a separate disposition after the prerequisites are met.

Current method context: Reconcile. C2 remains unresolved. Reading the next explanation does not advance the decision.

commit

See who may decide—and why commitment is withheld.

This stage explains the authority boundary. It does not simulate a completed launch commitment.

Human Authority · SYN-AUTH-01 v1.0

Illustrative program sponsor

Review the initial phase and withhold launch pending the required basis. Any future launch authorization requires applicable concurrence and separately satisfied conditions.

Authored role context only. The visitor is inspecting this role and receives no decision authority.

Commitment boundary

Launch commitment WITHHELD.

Recorded disposition: HOLD.

Supplier mobilization and crew availability are unverified; applicable concurrence remains open.

Actual authorization: NONE. Execution permission: NONE.

Inspect the recorded HOLD and its consequences
Disposition
HOLD — authored sponsor determination.
Rationale
Supplier mobilization and crew availability remain unverified; the applicable concurrence condition also remains open.
Next permitted work
Evidence supply and review; establish the concurrence route.
Reconsideration
A separately recorded sponsor determination after the updated basis and required concurrence.
What does not follow
No launch, spending, contracting or operational execution is authorized.

extract

Leave with a reconstructable basis.

Records remain useful during HOLD. They preserve the evidence, authority, uncertainty and next work; outcome learning is not yet established.

STATE AT THE RECORDED DISPOSITIONSnapshot ↗Inspect HOLD, the evidence gaps and recorded conditions.BASIS, TENSIONS AND AUTHORITYDecision Basis Record ↗Inspect sources, retained history, rationale and next actions.
  1. ACT-01
    Supplier lead · Provide a dated mobilization plan and evidence of crew availability for the initial phase.Before a new launch recommendation · Open
  2. ACT-02
    Program review lead · Check the new evidence against the launch scope, update C2 and the Decision Basis, and establish the applicable concurrence route with the rightful source authority.After ACT-01 and before sponsor reconsideration · Open
  3. ACT-03
    Accountable sponsor · Reconsider HOLD when the updated basis is ready and required concurrence is recorded.After ACT-02 and the required concurrence evidence · Awaiting prerequisites

These are authored specimens, available for inspection and download in the detailed record below. Navigation does not create a durable platform record or validate an operational outcome.

+1 · Governed adaptation

Reconsider the decision. Govern adaptation separately.

A changed source can reopen the decision basis. Reinsert addresses a different question: whether validated learning warrants changing the governing system.

Decision reconsideration

Changed evidence → affected basis reviewed.

For example, supplying a dated mobilization plan meets TR-01. It prompts review of E3, A1 and C2; crew evidence and concurrence still need separate assessment.

This is an explanation of a defined trigger. No new evidence arrival is simulated.

+1 Reinsert · not reached

Validated learning → governed adaptation review.

This specimen contains no operational outcome observation or validated learning for a governing-system change.

Current identified source: SYN-LAUNCH-CONDITIONS v1.0. No replacement version or adaptation authorization is issued.

Inspect the four recorded reconsideration triggers
TR-01 · Dated mobilization or crew evidence is supplied, changed or withdrawn.

Return C2 to evidence review; no automatic release.

Preserve the prior basis as-of. Record the changed source, affected relationships and review rationale in any future revision. No new version is created here.

TR-02 · The scope or funding baseline changes.

Reopen affected E1/E2 relationships and assess whether C1 remains resolved.

Preserve the prior basis as-of. Record the changed source, affected relationships and review rationale in any future revision. No new version is created here.

TR-03 · The governing source version, authority remit or concurrence requirement changes.

Reassess applicability and authority; preserve the historical basis as-of.

Preserve the prior basis as-of. Record the changed source, affected relationships and review rationale in any future revision. No new version is created here.

TR-04 · Resource availability or a material operating condition changes.

Revisit A1 and the affected launch dependency before further consideration.

Preserve the prior basis as-of. Record the changed source, affected relationships and review rationale in any future revision. No new version is created here.

The explanation is complete; the decision remains on HOLD. Next work: ACT-01 → ACT-02 → separate Human Authority reconsideration. Governed adaptation remains unperformed.

A public teaching example. No live AI, real authorization, operational execution or durable platform record. Website privacy

Discuss a decision like this →

↑ Return to the guided rehearsal← How Circular Deduction worksStart a Decision Review →

Detailed decision view

Initial-phase infrastructure launch

SYN-LAUNCH-01 v1.0 · D-01 · Current context: Reconcile

Human Authority · illustrative program sponsorHOLDCommitment WITHHELD · no launch authorized

C2 · unresolved

Supplier mobilization and crew availability are unverified; applicable concurrence remains open.

Next · Supplier lead

Provide dated mobilization and crew evidence. Review and separate sponsor reconsideration follow.

Synthetic case · no real authorization, execution, live AI or durable platform record.
Inspect the Snapshot →Inspect the record →

One decision. Its current basis.

Evidence status
Gaps
Contradiction status
Presented
Authority validity
Valid
Commitment / gate posture
Withheld
Reconsideration trigger set
Defined (4)
Record linkage
Snapshot

Authority validity is limited to the authored sponsor remit. Record linkage is a static Snapshot. Governing context explains these six fields; it is not a seventh field.

Current method context

Reconcile: unresolved C2 remains presented. The human HOLD is recorded; no launch commitment or completed outcome verification is represented.

Primary uncertainty

E3 supplier claim does not establish dated mobilization and crew availability. C2 stays unresolved.

Frame → Derive → Contradict → Reconcile → Commit → Extract. +1 Reinsert separately governs adaptation. These states are not an automatic completion sequence.

Four evidence lines. One explicit assumption.

E1 · Scope baseline

SYN-SCOPE-01 v1.1 · Fictional date 2026-10-14 · Program planning role

Authored source excerpt

The launch package covers the initial phase only. Later phases are excluded and require separate review.
State
Reviewed within the authored fixture
Limitation
Fictional baseline; it does not establish delivery readiness or authorize work.
Retained prior source version

SYN-SCOPE-01 v1.0 · Fictional date 2026-10-13

The scope includes the initial-phase launch and later-phase preparation.

Inspect the C1 reconciliation

Return to the basis ↑ · Outputs ↑

E2 · Funding confirmation

SYN-FUND-01 v1.1 · Fictional date 2026-10-14 · Funding owner role

Authored source excerpt

The funding basis applies to the initial phase described in SYN-SCOPE-01 v1.1. It does not cover later phases or constitute a spending instruction.
State
Aligned to E1 within the authored fixture
Limitation
Fictional scope and funding reconciliation; no actual allocation or payment authority.
Retained prior source version

SYN-FUND-01 v1.0 · Fictional date 2026-10-13

The funding basis covers the initial phase only.

Inspect the C1 reconciliation

Return to the basis ↑ · Outputs ↑

E3 · Supplier readiness claim

SYN-SUPPLIER-01 v1.0 · Fictional date 2026-10-13 · Supplier lead role

Authored source excerpt

Resources are expected to be available for the initial phase. The dated mobilization plan and crew availability evidence have not yet been provided.
State
Supplied claim; mobilization unverified
Limitation
A supplied claim is not verified readiness. Its falsity is also not established.

A1 assumptionC2 challengeACT-01 next actionDecision Basis Record

Return to the basis ↑ · Outputs ↑

E4 · Applicable requirements

SYN-LAUNCH-CONDITIONS v1.0 · Fictional date 2026-10-14 · Fictional source owner role

Authored source excerpt

SYN-R01: confirm launch resources with dated mobilization and crew evidence. SYN-R02: establish and record applicable concurrence before a launch authorization is considered.
State
Source identified; concurrence applicability remains open
Limitation
Requirements are fictional. The required concurrence scope remains unresolved; no legal or conformance finding.

Inspect applicable requirements

Return to the basis ↑ · Outputs ↑

A1 · Resource availability assumption

Required resources remain available through the intended mobilization window.

State
Explicit and unverified
Owner
Supplier lead
Effect
Cannot be used as proof of launch readiness; revisit on dated evidence or changed availability.

Return to the basis ↑

Reconciliation preserves the unresolved.

C1 · Scope and funding mismatch
Resolved in the authored fixture
What is challenged
Earlier E1 v1.0 included initial-phase launch and later-phase preparation; E2 v1.0 funded the initial phase only.
Disposition
The fictional review dated 2026-10-14 narrows E1 v1.1 to the initial phase and makes E2 v1.1 reference that exact scope. Later phases are excluded. This is a scope reconciliation, not a verified cost estimate.
Retained history and boundary
Retain the original mismatch and its dated disposition. Resolution of C1 does not resolve C2 or grant authority.
Owner
Program review lead

Inspect E1Inspect E2Record history →

Return to the basis ↑

C2 · Supplier mobilization unverified
Unresolved and bounded to the launch dependency
What is challenged
Treating the package as launch-ready would conflict with the requirement for dated mobilization and crew evidence, which is absent.
Disposition
Carry the challenge forward. Obtain evidence, review it and seek Human Authority reconsideration; do not infer permission from a readiness claim.
Retained history and boundary
C2 records a conflict between a proposed readiness conclusion and an unmet evidence condition. It does not assert that the supplier claim is false.
Owner
Program review lead

Inspect E3Inspect E4Inspect A1Next action →

Return to the basis ↑

Human disposition and governing context.

Role and remit · SYN-AUTH-01
Human disposition: HOLD. The gate remains WITHHELD. Actual authorization and execution permission: NONE.
Illustrative role
Illustrative program sponsor
Role-context reference
SYN-AUTH-01 v1.0
Remit
Review the initial phase and withhold launch pending the required basis. Any future launch authorization requires applicable concurrence and separately satisfied conditions.
Validity
Valid within the authored role context only
Concurrence
Required concurrence scope and evidence are not yet established
Rationale
Supplier mobilization and crew availability remain unverified; the applicable concurrence condition also remains open.

SYN-AUTH-01 is authored role context, not an eighth evidence thread or a real appointment. Identity and participation do not create decision authority.

Governing context

SYN-LAUNCH-CONDITIONS v1.0: confirm launch resources (SYN-R01) and establish and record applicable concurrence (SYN-R02). Concurrence remains open. No source interpretation or compliance finding is created.

Inspect requirement mapping

Recorded next work.

Supplier evidence, review and concurrence, then separate sponsor reconsideration. No automatic release.

ACT-01 · Supplier lead · Open

Provide a dated mobilization plan and evidence of crew availability for the initial phase.

Due condition
Before a new launch recommendation
Completion evidence
Dated plan, crew availability evidence, identified source and applicable scope; submission alone does not resolve C2.
Dependencies
C2, E3, SYN-R01

Return to C2 · Decision Basis Record · Outputs ↑

ACT-02 · Program review lead · Open

Check the new evidence against the launch scope, update C2 and the Decision Basis, and establish the applicable concurrence route with the rightful source authority.

Due condition
After ACT-01 and before sponsor reconsideration
Completion evidence
Recorded evidence assessment, disposition rationale, updated limitations and identified concurrence requirements; review completion does not authorize launch.
Dependencies
ACT-01, E4, SYN-R02

Return to C2 · Decision Basis Record · Outputs ↑

ACT-03 · Accountable sponsor · Awaiting prerequisites

Reconsider HOLD when the updated basis is ready and required concurrence is recorded.

Due condition
After ACT-02 and the required concurrence evidence
Completion evidence
A separately recorded Human Authority disposition within scope. No release from HOLD is preselected or simulated by navigation.
Dependencies
ACT-02, C2, SYN-R02

Return to C2 · Decision Basis Record · Outputs ↑

Reconsideration conditions

TR-01 · Dated mobilization or crew evidence is supplied, changed or withdrawn.

Return C2 to evidence review; no automatic release.

TR-02 · The scope or funding baseline changes.

Reopen affected E1/E2 relationships and assess whether C1 remains resolved.

TR-03 · The governing source version, authority remit or concurrence requirement changes.

Reassess applicability and authority; preserve the historical basis as-of.

TR-04 · Resource availability or a material operating condition changes.

Revisit A1 and the affected launch dependency before further consideration.

Inspect the authored records.

All six specimens describe the same HOLD. They are representative documents, not runtime-generated durable records.

01 · Snapshot — state at the decision

SYN-SNAP-01 v1.0 · SYN-LAUNCH-01 v1.0 · Synthetic specimen · As of 14 October 2026

Decision
Whether to authorize the initial phase of an infrastructure launch within the reconciled scope and funding basis, subject to verified supplier mobilization and required concurrence.
Scope
Initial launch phase only. Later phases, spending authority, contracting and operational execution are outside this specimen.
Human disposition
HOLD · illustrative program sponsor
Gate and execution
WITHHELD · actual authorization NONE · execution NOT PERFORMED
Basis
E1–E4; A1 unverified; C1 resolved with history; C2 unresolved. Required concurrence remains open.

A static authored snapshot. It does not establish runtime generation, persistence, signature, or a real decision.

Return to outputs ↑ · Return to the decision ↑

02 · Decision Basis Record — sources, tensions and authority

SYN-DBR-01 v1.0 · SYN-LAUNCH-01 v1.0 · Synthetic specimen · As of 14 October 2026

Decision and bounded object

Whether to authorize the initial phase of an infrastructure launch within the reconciled scope and funding basis, subject to verified supplier mobilization and required concurrence.

Initial launch phase only. Later phases, spending authority, contracting and operational execution are outside this specimen.

Source references and tensions

E1 · Scope baseline

SYN-SCOPE-01 v1.1 · Reviewed within the authored fixture Fictional baseline; it does not establish delivery readiness or authorize work.

E2 · Funding confirmation

SYN-FUND-01 v1.1 · Aligned to E1 within the authored fixture Fictional scope and funding reconciliation; no actual allocation or payment authority.

E3 · Supplier readiness claim

SYN-SUPPLIER-01 v1.0 · Supplied claim; mobilization unverified A supplied claim is not verified readiness. Its falsity is also not established.

E4 · Applicable requirements

SYN-LAUNCH-CONDITIONS v1.0 · Source identified; concurrence applicability remains open Requirements are fictional. The required concurrence scope remains unresolved; no legal or conformance finding.

A1 · Resource availability

Required resources remain available through the intended mobilization window. Explicit and unverified.

C1 · Scope/funding

The fictional review dated 2026-10-14 narrows E1 v1.1 to the initial phase and makes E2 v1.1 reference that exact scope. Later phases are excluded. This is a scope reconciliation, not a verified cost estimate.

C2 · Supplier mobilization

C2 records a conflict between a proposed readiness conclusion and an unmet evidence condition. It does not assert that the supplier claim is false. Unresolved and bounded to launch.

Governing context

SYN-LAUNCH-CONDITIONS v1.0 is fictional. SYN-R01 requires dated resource evidence; SYN-R02 requires the applicable concurrence route and recorded concurrence before launch authorization is considered. Source authority does not confer organizational authority. No compliance or legal finding is represented.

Human Authority and recorded disposition

Human disposition: HOLD. The gate remains WITHHELD. Actual authorization and execution permission: NONE.
Illustrative role
Illustrative program sponsor
Role-context reference
SYN-AUTH-01 v1.0
Remit
Review the initial phase and withhold launch pending the required basis. Any future launch authorization requires applicable concurrence and separately satisfied conditions.
Validity
Valid within the authored role context only
Concurrence
Required concurrence scope and evidence are not yet established
Rationale
Supplier mobilization and crew availability remain unverified; the applicable concurrence condition also remains open.

SYN-AUTH-01 is authored role context, not an eighth evidence thread or a real appointment. Identity and participation do not create decision authority.

Recorded next actions

ACT-01 · Supplier lead

Provide a dated mobilization plan and evidence of crew availability for the initial phase. Due: Before a new launch recommendation. State: Open.

ACT-02 · Program review lead

Check the new evidence against the launch scope, update C2 and the Decision Basis, and establish the applicable concurrence route with the rightful source authority. Due: After ACT-01 and before sponsor reconsideration. State: Open.

ACT-03 · Accountable sponsor

Reconsider HOLD when the updated basis is ready and required concurrence is recorded. Due: After ACT-02 and the required concurrence evidence. State: Awaiting prerequisites.

Authored decision history

H-01 · Initial basis

14 October 2026, fictional. Earlier E1 v1.0 included later-phase preparation; E2 v1.0 funded only the initial phase. C1 was presented. Supplier readiness was claimed; dated verification was absent.

H-02 · Scope reconciled

14 October 2026, fictional. E1 v1.1 excludes later phases; E2 v1.1 references the exact revised scope. C1 is resolved with the original mismatch retained. C2 remains unresolved.

H-03 · Human disposition

14 October 2026, fictional. The illustrative sponsor records HOLD. Gate WITHHELD; concurrence remains open; ACT-01–ACT-03 are recorded. No launch is authorized or performed.

Reconsideration conditions

TR-01 · Dated mobilization or crew evidence is supplied, changed or withdrawn.

Return C2 to evidence review; no automatic release.

TR-02 · The scope or funding baseline changes.

Reopen affected E1/E2 relationships and assess whether C1 remains resolved.

TR-03 · The governing source version, authority remit or concurrence requirement changes.

Reassess applicability and authority; preserve the historical basis as-of.

TR-04 · Resource availability or a material operating condition changes.

Revisit A1 and the affected launch dependency before further consideration.

Closure and learning

No launch, outcome verification, decision closure or authorized Reinsert is represented. Working records remain useful during HOLD. Recorded triggers are not active monitoring.

Representative document content only. This is not a runtime-generated, signed or durably stored platform record. Every organization, role, date and source in this case is fictional.

Return to outputs ↑ · Return to the decision ↑

03 · Action register — owners, evidence and reconsideration

SYN-ACT-01 v1.0 · SYN-LAUNCH-01 v1.0 · Synthetic specimen · As of 14 October 2026

ACT-01 · Supplier lead · Open

Provide a dated mobilization plan and evidence of crew availability for the initial phase.

Due condition
Before a new launch recommendation
Completion evidence
Dated plan, crew availability evidence, identified source and applicable scope; submission alone does not resolve C2.
Dependencies
C2, E3, SYN-R01

Return to C2 · Decision Basis Record · Outputs ↑

ACT-02 · Program review lead · Open

Check the new evidence against the launch scope, update C2 and the Decision Basis, and establish the applicable concurrence route with the rightful source authority.

Due condition
After ACT-01 and before sponsor reconsideration
Completion evidence
Recorded evidence assessment, disposition rationale, updated limitations and identified concurrence requirements; review completion does not authorize launch.
Dependencies
ACT-01, E4, SYN-R02

Return to C2 · Decision Basis Record · Outputs ↑

ACT-03 · Accountable sponsor · Awaiting prerequisites

Reconsider HOLD when the updated basis is ready and required concurrence is recorded.

Due condition
After ACT-02 and the required concurrence evidence
Completion evidence
A separately recorded Human Authority disposition within scope. No release from HOLD is preselected or simulated by navigation.
Dependencies
ACT-02, C2, SYN-R02

Return to C2 · Decision Basis Record · Outputs ↑

Four recorded reconsideration conditions

TR-01 · Dated mobilization or crew evidence is supplied, changed or withdrawn.

Return C2 to evidence review; no automatic release.

TR-02 · The scope or funding baseline changes.

Reopen affected E1/E2 relationships and assess whether C1 remains resolved.

TR-03 · The governing source version, authority remit or concurrence requirement changes.

Reassess applicability and authority; preserve the historical basis as-of.

TR-04 · Resource availability or a material operating condition changes.

Revisit A1 and the affected launch dependency before further consideration.

This register assigns fictional roles only. No real tasks, reminders or monitoring are created. Received evidence and reviewed evidence remain distinct.

Return to outputs ↑ · Return to the decision ↑

05 · Requirement map — source to evidence and condition

SYN-MAP-01 v1.0 · SYN-LAUNCH-01 v1.0 · Synthetic specimen · As of 14 October 2026

SYN-R01 · Confirm launch resources
source
E4
name
Confirm launch resources
evidence
Dated mobilization and crew availability material; E3 alone is insufficient
state
Unmet evidence condition
responsibility
Supplier lead supplies ACT-01; program review lead assesses under ACT-02
SYN-R02 · Record concurrence
source
E4
name
Record concurrence
evidence
Identified applicable concurrence route and recorded concurrence before a launch authorization is considered
state
Interpretation and concurrence remain open
responsibility
Program review lead establishes the route with rightful source authority; sponsor observes the boundary

Fictional requirements. Traceability does not establish legal interpretation, certification, or conformance.

Return to outputs ↑ · Return to the decision ↑

06 · Authority and gate model — conditions and consequences

SYN-GATE-01 v1.0 · SYN-LAUNCH-01 v1.0 · Synthetic specimen · As of 14 October 2026

G1 · Basis review

name
Basis review
owner
Program review lead
condition
Review E1-E4, retain A1, preserve C1 history and bound C2
effect
Missing evidence or unresolved applicability returns the package for work

G2 · Human disposition

name
Human disposition
owner
Illustrative program sponsor
condition
Review within the initial-phase remit
effect
HOLD recorded with rationale, conditions and next actions; no launch authorized

G3 · Reconsideration

name
Reconsideration
owner
Program review lead then accountable sponsor
condition
Evidence assessed and applicable concurrence established and recorded
effect
A separate future sponsor determination; no automatic release or preselected outcome

A design specimen, not an enforced runtime control. Changed evidence, scope, source version, authority or concurrence returns the affected basis to review. No exception or automatic release is offered.

Return to outputs ↑ · Return to the decision ↑

Navigation in this browser session.

Local navigation only; clears on reload. Separate from the authored H-01–H-03 history in the record. This is not a durable event ledger or a signed receipt.

  1. Public synthetic case opened. HOLD and WITHHELD remain unchanged.

Decision Under Examination · Controlled Demonstration

Examine one consequential decision.

Follow one public-safe decision as evidence is tested, contradiction remains visible, and accountable authority determines whether it may advance.

CD-DEMO-001SyntheticPublic-safeWithheld

Aegis assists. ECOS governs. You retain authority.

Examine CD-DEMO-001

Synthetic governance context for CD-DEMO-001: Current state · SYNTHETIC SESSION PROJECTION. Materiality · CONSEQUENTIAL. External Governing Systems · synthetic source context only. Governing version · synthetic demo baseline. As-of · current browser session only. Human Authority · simulated boundary only; no real authorization. Execution · NOT AUTHORIZED / NOT PERFORMED. Evidence lineage · synthetic fixture / provenance-aware display. Governance Translation · system/source/version/bounded-object/applicability/authority/evidence/control context is illustrative only. Reinsert · NOT YET REACHED. Adaptive-authority review · NOT INVOKED. These context fields sit around the six universal state fields; they do not create authority, persistence, a durable Decision Basis Record, standards status, regulatory compliance, or production interoperability.

  1. 01EvidenceBasis made visible
  2. 02ContradictionMaterial conflict exposed
  3. 03ReconciliationDisposition recorded
  4. 04Human AuthorityAccountability retained
  5. 05Commitment

    Human Commit controlled

  6. 06RecordDecision basis reconstructable

Circular Deduction™ · Functional Demonstration

Change the conditions. Examine what matters—and why the gate moves.

Decision Cockpit™ is the common operating surface for one consequential decision inside a Decision Biosphere. Threshold establishes identity and tenant context; it does not confer Human Authority. The Cockpit exposes six governed state fields: evidence status, contradiction status, authority validity, commitment / gate posture, reconsideration trigger set, and record linkage.

Governed change is made legible as cause → state → rationale → trace. The interface foregrounds current state, the most consequential unresolved condition, the authority boundary, the next permitted action, and the consequence of that action.

This public version is a controlled, synthetic demonstration. The local trace keeps 30 events and clears on reset or reload.

Demonstration only.No real organization, decision, certification, or Aegis status is represented.

Where the Method Stands →Review how this synthetic demonstration fits the current maturity boundary.

DECISION COCKPIT™ · COMMON OPERATING SURFACE

One governed state grammar across demo, pilot, and future product tiers.

The Cockpit presents governed decision state. External Governing Systems are projected through Governance Translation as bounded context around the six universal fields: system/source and version, bounded object, applicability, source authority, organizational Human Authority, evidence requirement/state, relationship or control effect, conflict/precedence, and reconsideration.

These remain context—not new state fields and not transferred authority. When bound to the Decision Basis Record, governing context is preserved as-of the decision; later source changes trigger reconsideration rather than rewriting history.

This public demonstration remains synthetic and does not establish compliance, certification, live enterprise enforcement, or production interoperability.

Evidence status
Sufficient · Gaps · Unknown
Contradiction status
Reconciled · Presented
Authority validity
Valid · Invalid · Not yet designated
Commitment / gate posture
Ready · Withheld · Conditioned · Rejected
Reconsideration trigger set
Defined (n) · None defined
Record linkage
Session-only demonstration; no durable Decision Basis Record is created.
Decision Basis Record · Not generated in public demo
A durable record is created or versioned only on explicit state-changing events in pilot or future product tiers after the required governance and evidence gates are met.

Capability maturity is evidence-gated.

Current public demo

Synthetic fixture · session-local state · no live AI · no enterprise integration · no durable Decision Basis Record · no real authorization.

Pilot-grade candidate

Persistent pilot ID, named roles, provenance-aware evidence, persistent trace, reconsideration triggers, and bounded record export only after identity, retention, privacy/security, and authority gates are satisfied.

Future product candidate

Connector-backed evidence, identity-backed policy, workflow-integrated transitions, automated watch conditions, and persistent linked records remain future capabilities until their evidence and security gates are met.

Synthetic scenario · infrastructure capital decision

Decision Cockpit™

Select a vendor and architecture for a hypothetical $4.8M regional fiber resilience upgrade.

Commitment / gate postureAT RISKEvidence is incomplete.
  1. 1Evidence
  2. 2Contradiction
  3. 3Reconciliation
  4. 4Human Authority
  5. 5Commitment
  6. 6Decision Basis Record

Change the conditions

Control state

Reset
Evidence sufficiency
Contradiction state
Human authority
Decision package
Simulated record-linkage status

System interpretation

Decision package state

EvidenceGAPS
ContradictionsPRESENTED
AuthorityVALID
PackageBOUND
Decision Basis RecordNOT GENERATED
AegisACTIVE
Human Authority BoundaryCOMMITMENT GATE — HOLD

Commitment cannot advance until Human Authority reviews the current package and the Decision Basis Record is healthy. Material evidence gaps remain.

Test commitment gate

Why this posture?

  • Material evidence gaps remain.
  • An unresolved contradiction is visible to authority and requires explicit judgment.

Session trace · reconstructability demonstration

State-change trace

Local demonstration trace · latest 30 events · clears on reset or reload
  1. Synthetic demonstration initialized.

What the demonstration is showing

01

Analysis is not authority.

Aegis can support the package, but the model never becomes the accountable decision-maker.

02

Contradictions cannot disappear.

Material disagreement must be dispositioned or explicitly presented to the human authority.

03

Record health matters.

An unresolved record-linkage state cannot be represented as healthy merely because the recommendation looks strong.

04

Assurance is not automatic certification.

The Cockpit can maintain evidence and surface posture. Formal certification remains an independent human decision.

Decision Under Examination

Explore the method applied to a complete synthetic decision.

Follow one public-safe decision through evidence, contradiction, reconciliation, Human Authority, commitment, and a reconstructable record.

Synthetic demonstrationNo real client matter
Examine the decision

Decision under examination · Synthetic demonstration

CD-DEMO-001 · PUBLIC-SAFE FIXTURE

Authorize a phased regional fiber expansion.

Follow one consequential decision through evidence, contradiction, accountable authority, commitment, and a reconstructable release record.

Evidence coverage78%
Validation checks6 / 8
Residual risks2Material · unresolved
Designated Decision AuthorityNot yet designatedAuthority required · decision not granted

Decision architecture

The examination path remains visible.

Shape, label, and state carry meaning independently of color.
  1. Decision NucleusEXAMINING
  2. Evidence Orbit78% COVERED
  3. Assumption Veil1 HYPOTHESIS
  4. Contradiction Faultline1 OPEN
  5. Authority GateNAMED HUMAN
  6. Commitment LockNOT GRANTED
  7. Consequence TraceRELEASE HELD
  8. Reconsideration ArcRETURN DEFINED
Reveal evidence basis

Structured evidence

Every claim carries state, provenance, and limitation.

Synthetic values; no client or independent-validation claim.
CLM-001Tested

Demand forecast supports phased entry.

Provenance: Synthetic planning model v0.3
Limitation: No field demand validation

CLM-002Operationally Observed

Construction window is operationally feasible.

Provenance: Public-safe operating pattern
Limitation: Not route-specific

CLM-003Hypothesis

Take-rate reaches the financial threshold.

Provenance: Synthetic scenario assumption
Limitation: Requires market validation

CLM-004Contradicted

Existing route diversity is sufficient.

Provenance: Synthetic architecture review
Limitation: Redundancy evidence conflicts

DesignedTestedIndependently ReviewedOperationally ObservedClient ValidatedHypothesisUnknownContradictedStaleSuperseded

Assurance report snapshot

The release consequence follows the evidence.

System analysis informs the package; a named person retains authority.
Residual risk · RSK-02Route diversity remains unresolved.

Material contradiction propagates forward; commitment cannot inherit a healthy state.

Named human authorityDesignated Decision Authority · Not yet designated

Aegis may analyze and prepare. It cannot authorize or commit this decision.

Release consequenceWITHHOLD · RETURN FOR EVIDENCE

No capital authorization. Return after redundancy and demand evidence receive explicit disposition.

Synthetic demonstration. No client data, independent validation, production authorization, or release approval is represented.

Decision ID, state, focus, and return context are preserved in each transition.

Continue the work

Move from demonstration to a bounded decision review.

Use the method to understand the governing logic, start with one consequential decision, or return to the Decision Biosphere to orient to the broader environment.

Start a Decision ReviewExplore the MethodReturn to Biosphere
INVESTOR REVIEW CONTEXT

You just saw the governed operating surface of the 6+1 architecture.

This public Cockpit runs on a labeled synthetic fixture—the governance pattern is demonstrated; the data is synthetic by design. Return to the Investor Brief for the statefulness/IP thesis, interoperability model, evidence boundary, and infrastructure-scale hypothesis.

Return to Investor Brief