How Circular Deduction works
See the basis.
Understand the next move.
Bring one consequential decision, its supporting material and the people accountable for it. Examine the evidence, tensions, Human Authority and next actions together.
One authored synthetic example. No real authorization, live AI or durable platform record.
Can the initial phase launch?
Scope and funding aligned. Supplier mobilization unverified.
Gate WITHHELD · no launch authorized
C2 remains unresolved.
A readiness claim does not establish a dated mobilization plan or crew availability. Required concurrence also remains open.
Next action · Supplier lead
Provide dated mobilization and crew evidence before a new recommendation. Review and human reconsideration follow separately.
One fixed example. Explore in any order. The disposition stays HOLD.
Bring the decision
Define the commitment before reviewing the evidence.
The example sponsor is considering the initial phase of an infrastructure launch. Scope and funding have been aligned, but supplier mobilization is still unverified.
The review establishes what supports the decision, what remains open and who may act.
- What you bring
- Decision, stakes, accountable owner, commitment condition, attributable source material and handling constraints.
- What the review supports
- A structured basis linking sources, assumptions, challenges and governing conditions.
- What you can inspect
- E1 scope · E2 funding · E3 supplier claim · E4 requirements · A1 assumption
The example is limited to the initial phase. No launch, later phase, spending or operational execution is authorized.
Examine the basis
See what holds—and what still needs evidence.
The dated scope/funding reconciliation resolves C1 and retains its history. C2 remains open because a readiness claim does not establish a dated mobilization plan or crew availability.
The review carries that condition into the record and next action.
- Resolved, with history
- C1 · Scope/funding mismatch — the initial phase is now aligned. Later phases remain excluded.
- Unresolved and bounded
- C2 · Supplier mobilization — missing verification prevents a launch-ready conclusion.
- Follow one evidence path
- E3 supplied claim → C2 challenge → ACT-01 evidence request → Decision Basis Record
You supply attributable material. The review examines relevance and limits. Separately authorized Aegis analysis remains distinct from source evidence and human judgment.
Human Authority
Make the disposition and consequence explicit.
The illustrative program sponsor records HOLD within the initial-phase review remit. Supplier mobilization is unverified and the applicable concurrence condition remains open.
The next step is evidence and review, followed by a separately recorded human reconsideration.
- Human disposition
- HOLD — an authored sponsor decision, not a visitor-selectable outcome.
- Gate posture
- WITHHELD — a representation of unresolved conditions, not the Cockpit making a decision.
- Role and remit
- Inspect SYN-AUTH-01 — review and withholding only; future launch requires separately satisfied conditions.
Actual authorization: NONE. Execution permission: NONE. Selecting an explanation never clears C2 or changes HOLD.
Record and next actions
Leave with a basis another reviewer can reconstruct.
The Snapshot shows the recorded state and conditions. The representative Decision Basis Record preserves sources, assumptions, tensions, governing context, authority and next actions.
Working records exist before a disposition and remain useful during HOLD.
Completing an evidence task does not automatically authorize launch. A new Human Authority disposition must be separately recorded.
Attributable, inspectable, bounded
Follow the evidence.
Read the supplied claim, see the challenge it creates, then follow the owner and next action. All source material here is fictional.
E1 · Scope baseline
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
The scope includes the initial-phase launch and later-phase preparation.
E2 · Funding confirmation
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
The funding basis covers the initial phase only.
E3 · Supplier readiness claim
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
E4 · Applicable requirements
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.
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.
C1 · Scope and funding mismatch
- 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
C2 · Supplier mobilization unverified
- 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
Human Authority · role, remit and concurrence
- 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.
Representative deliverables
Inspect what you receive.
Populated specimens from the same case. The agreed service scope determines your actual outputs; the four services are separate choices.
01 · Snapshot — state at the decision
- 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.
02 · Decision Basis Record — sources, tensions and authority
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
SYN-SCOPE-01 v1.1 · Reviewed within the authored fixture Fictional baseline; it does not establish delivery readiness or authorize work.
SYN-FUND-01 v1.1 · Aligned to E1 within the authored fixture Fictional scope and funding reconciliation; no actual allocation or payment authority.
SYN-SUPPLIER-01 v1.0 · Supplied claim; mobilization unverified A supplied claim is not verified readiness. Its falsity is also not established.
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.
Required resources remain available through the intended mobilization window. Explicit and unverified.
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 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
- 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
Provide a dated mobilization plan and evidence of crew availability for the initial phase. Due: Before a new launch recommendation. State: 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: After ACT-01 and before sponsor reconsideration. State: Open.
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
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.
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.
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
Return C2 to evidence review; no automatic release.
Reopen affected E1/E2 relationships and assess whether C1 remains resolved.
Reassess applicability and authority; preserve the historical basis as-of.
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.
03 · Action register — owners, evidence and reconsideration
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.
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.
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.
Four recorded reconsideration conditions
Return C2 to evidence review; no automatic release.
Reopen affected E1/E2 relationships and assess whether C1 remains resolved.
Reassess applicability and authority; preserve the historical basis as-of.
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.
04 · Linked decisions — dependencies and accountable owners
HOLD · Owner: Program sponsor. Supplier evidence and applicable concurrence.
Evidence required · Owner: Supplier lead. Supplier lead supplies ACT-01; program review lead assesses under ACT-02.
Not yet undertaken · Owner: Program sponsor. ACT-02 complete and concurrence evidence recorded.
D-02 supplies part of the basis for D-03. D-03 may reconsider D-01 under the applicable authority and conditions. Links do not transfer authority or replace execution systems.
05 · Requirement map — source to evidence and condition
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.
06 · Authority and gate model — conditions and consequences
- 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
- 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
- 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.
Responsibility model
Clear work. Explicit ownership.
The review organizes the basis. Your accountable people retain the decision and operational responsibilities.
Your team
Own the context and decision.
Identify the decision, supply attributable evidence, explain operational constraints and establish the accountable Human Authority. Named client or supplier owners carry out agreed actions.
Circular Deduction
Structure the review and record.
Examine sources, assumptions and tensions. Make the governing conditions and next work inspectable. Prepare the agreed output and support further review within scope.
Accountable Human Authority
Decide within an established remit.
Review the basis, obtain required concurrence, record the disposition and determine reconsideration or closure. Tool access, analysis and review readiness do not confer authority.
What your team should expect before work begins
Agree the bounded decision, source owners, subject experts, accountable sponsor, review touchpoints and acceptance criteria.
Identify source volume, readiness, access permissions and handling constraints. Use an agreed channel before sharing confidential evidence.
The proposal establishes outputs, responsibilities, timing and fees. Do not infer a standard turnaround or effort commitment from this example.
Where authorized, Aegis can assist analysis, challenge and reconstruction. Analytical output remains labeled and subject to human review.
Owners carry out agreed actions. Continuing monitoring, source watching, reminders and further review exist only when explicitly scoped.
From one decision to the platform
The roles behind the experience.
Understand the worked example first. Explore the architecture when it helps assess your intended use.
One decision sits within a wider governed environment. Enter through Threshold. Orient in the Biosphere. Govern in the Cockpit.
Threshold
Identity, entry and tenant context. Signing in does not create decision authority.
Decision Biosphere
The bounded environment for decisions, evidence, actors and governing context.
Decision Cockpit
The operating surface that makes one decision’s governed state inspectable.
Decision Basis Record
The reconstructable record. The public specimen is an authored document example.
ECOS supplies governed state and context. Aegis provides bounded analytical assistance. Accountable humans retain decision authority.
Inspect the operating architecture and integration boundary
Governance Translation connects identifiable source requirements to bounded evidence needs and decision conditions. Source authority and organizational Human Authority remain distinct. The Cockpit presents governed state and requests; it does not independently authorize commitment or write the durable record.
The Integration Gateway architecture preserves source identity, version, applicability, evidence state and limitations. A bounded internal reference connector has technical validation; that does not establish generally available enterprise integration, continuous ingestion or client workflow performance.
Inside the Decision Architecture →The canonical 6+1 Method →Aegis role and authority →
Capability-status map
What is shown. What is available.
A polished demonstration, a scoped service and an operational platform capability require different evidence.
| Capability | Status | What that means |
|---|---|---|
| Public guide and Cockpit | Synthetic demonstration | Inspect this authored case, sources, tensions and records. No live AI, source verification or real authorization. Inspect context → |
| Document specimens | Representative content | Six populated examples. A download copies authored content; it is not a runtime-generated durable record. Inspect context → |
| Four services | Offered by agreed scope | Decision Review, Project & Program Decision Review, Governance Translation and Decision Governance Design. A proposal establishes the work and fee. Inspect context → |
| Assisted analysis | Bounded engagement support | Permitted inputs, handling, tools and review are agreed. AI output does not become source evidence or decision authority. Inspect context → |
| Authenticated access and trials | Separate qualification | Public demonstration access does not establish client portal availability, tenant isolation, a trial agreement or operating acceptance. Inspect context → |
| Persistence and execution controls | Qualification required | Retention, recovery, durable receipts, authority enforcement and atomic changes require separately qualified engineering. Inspect context → |
| Enterprise integration and monitoring | Controlled development | Reference evidence does not establish generally available connectors or continuous ingestion. Recorded reconsideration triggers are not active watches. Inspect context → |
| Outcomes and assurance | Evidence remains bounded | This example does not establish quantified savings, guaranteed outcomes, certification or independent client validation. Inspect context → |
Your next decision
Bring the decision you need to examine.
Start with a brief, non-confidential summary: what is being decided, why it matters now and the output you need. We review fit and agree scope, responsibilities, handling, timing and fees before work begins.
An inquiry creates no engagement or authorization.
