See what governs
the decision.

Circular Deduction is the methodology. The first six states govern the consequential decision:

1. Frame
2. Derive
3. Contradict
4. Reconcile
5. Commit
6. Extract

Commit completes the authorized decision. Downstream execution, verification and observed outcomes remain separately accountable. Extract establishes candidate learning.

Authorization, implementation, verification and learning closure must remain distinguishable.

Verified evidence

Corroborated information with source authority and material limitations preserved.

Supplied claim

Information presented by a source but not yet independently established.

Assumption or inference

A premise or reasoned conclusion distinguishable from evidence.

Unknown, Contradicted, Stale, Superseded

Distinct conditions that carry into residual risk and can trigger reconsideration until evidence or accountable authority resolves them.

Independent support remains necessary

A prior accepted conclusion establishes historical state; it cannot validate its own substantive correctness in a later cycle. Material reuse preserves provenance and requires independent or newly observed support appropriate to the current claim.

A practical example

“The vendor can deploy in ten weeks” remains a vendor claim conditional on integration readiness and data quality. The schedule is not established until those dependencies are tested.

Reconsideration

New conflicting evidence challenges an assumption, identifies the affected basis and reopens the decision. The resulting disposition may be revised, conditioned, deferred or rejected.

External governing systems → ECOS

Standards, regulation, policy, contracts, authority structures, methods, controls and systems of record contribute bounded, attributed and versioned inputs. Source, applicability, authority, evidence state and admission lineage remain explicit.

ECOS → Decision Cockpit

ECOS supplies governed state. The Cockpit displays it; the Cockpit does not own evidence or authority.

Cockpit request → validation → Decision Basis Record

A deliberate, authorized request is checked against current conditions. Durable records change through explicit governed state transitions.

Aegis → ECOS

Analysis, challenge and candidate proposals remain bounded inputs. Aegis cannot authorize, accept risk or write authority state.

The Decision Seam

A bounded point where evidence, authority, constraints or readiness govern permission to create material consequence. The surrounding external system retains its own identity.

Before an input affects the Decision Basis, the architecture resolves source/version, applicability, authority, evidence state and its control or gate effect.

Governance translation

External Governance Object → Governance Primitive → Applicability → Authority Resolution → Evidence Requirement / Evidence State → Control or Gate Effect → Decision Basis → Assurance Output.

FEED, HOST, GOVERN and GATE describe interoperability functions; their depiction does not establish unrestricted enterprise integration.

Five connected layers

1. Accountable Human Authority: purpose, permitted data and action, residual risk, commitment, closure and release.
2. Human and domain language: people describe the decision in the language of their work.
3. Aegis intent translation: analysis and challenge within explicit boundaries; material ambiguity calls for clarification.
4. ECOS and Decision Review: governed context and review of evidence, authority, commitments, verification, risk and reconstructability.
5. Cockpit, Decision Basis Record and Integration Gateway: inspect state, retain the as-of justification and admit attributable external requirements.

From questions to controls

What do we actually know?

Evidence-state classification separates evidence, claims, assumptions and gaps.

What does not add up?

Contradiction review connects conflicting evidence to its decision effect.

Does the decision still hold?

A reconsideration gate reopens material changed conditions.

Who actually decides?

Recommendation, approval, risk acceptance, commitment and execution remain distinct.

Can we defend this?

Decision / Artifact Assurance examines evidence, contradiction, authority and release readiness.

Translation integrity

Material ambiguity and its resolution are retained. Qualitative states such as Confirmed, Ambiguous, Clarification required and User-corrected describe the translation; they do not supply authority.

Five truths remain reconstructable

State truth

Accepted state-changing events establish current decision state under the applicable evidence and authority gates. Activity completion alone grants no entitlement.

Governing truth

Each consequential transition refers to an identified governing version. Later rules cannot silently rewrite its basis.

Authority truth

Decision rights are bounded and distinct from participation, technical access, recommendation and implementation capability.

Execution truth

The record distinguishes proposer, authorizer and executor, and whether the executed object matched what was approved.

Evidence truth

Source identity, classification, admission status, limitations and transformation lineage remain attached.

Commit and receipt are separate

The design contract distinguishes WITHHELD, READY, COMMITTED and RECONCILIATION REQUIRED. Readiness permits eligible Human Authority to review a deliberate commitment. Committed state does not itself establish VERIFIED Decision Assurance Ledger (DAL) evidence.

Where committed state lacks matching receipt evidence, reconciliation is required; another commitment must not be inferred as the remedy. Current conditions and authority must be rechecked by the authoritative server at execution.

Records across the lifecycle

The Decision Basis Record preserves point-in-time history, authority, commitments, evidence, assumptions, contradictions, uncertainty and execution provenance. The DAL is the record layer across the lifecycle, not a reasoning stage.

Reported completion, approved action, executed action, observed outcome and authorized human closure remain distinct.

Design candidates and limits

Ledger of Judgment and Double-Entry Deduction remain proposed historical-reconstruction and reconciliation disciplines subject to compatibility, integrity, replay and independent verification gates. These bounded reference controls do not establish production IAM/RBAC, universal interoperability or client-validated outcomes.

Challenge the rule as well as the behavior

Ask whether the system behaved correctly under the current rule, whether the rule itself is correct, and whether the process that created or changed it is trustworthy.

Material findings can move from behavior to governance of behavior to assurance of the governance process. An assurance failure can reopen the review even when a revised rule appears reasonable.

Public architecture

• Layer relationships and evidence-state grammar
• Contradiction, reconsideration, authority and assurance concepts
• Evidence posture and controlled-pilot boundaries
• Human-language and canonical-control relationships

Controlled implementation

• System prompts and provider-routing logic
• Private scoring and evaluator calibration
• Private registries and identity internals
• Confidential benchmark, client or employer material