Process & Architecture
How a Decision Forum session works.
Every Decision Forum session follows a constitutionally enforced process — from question intake through cryptographically sealed Evidence Bundle. No step is optional. No shortcut is permitted by the architecture.
The Decision Forum Process
A real-world scenario: evaluating a $50M acquisition.
Your board is evaluating an $85M acquisition target. Integration risk is substantial. Regulatory exposure is unclear. Here is what a Decision Forum session produces — and why it matters when the decision is later questioned.
Question Framing
Scenario
The board chair submits: "Should the board approve the proposed acquisition of [Target Company] at the $85M valuation, given current market conditions, integration risk, and regulatory exposure?"
Mechanism
The question is cryptographically timestamped upon submission. The Decision Forum session is opened. All subsequent events are recorded to EXOCHAIN.
Legal Significance
Establishes the evidential perimeter. Timestamp satisfies FRE 901(b)(9).
Independent Panel Analysis
Scenario
Five frontier AI models — from independent providers, with no coordination — analyze the acquisition question in parallel.
Mechanism
Models include Claude, GPT, Gemini, Grok, and DeepSeek — selected to minimize training correlation and maximize perspective diversity. Each produces a complete, independent analysis.
Legal Significance
Multi-source independence eliminates single-point-of-bias objection.
Deliberation Rounds
Scenario
Each model reviews the other models' analyses. Initial convergence is measured: 78%. Specific disagreements are identified and surfaced.
Mechanism
Models revise positions based on each other's reasoning — not on authority, but on argument. Convergence is re-measured after each round. The process continues until convergence threshold is reached or a Minority Report is warranted.
Legal Significance
Deliberation record demonstrates consideration of multiple perspectives.
Adversarial Review
Scenario
The built-in Adversarial Review challenges the emerging consensus. It identifies: regulatory exposure in EU market (underweighted by panel); integration timeline underestimated by 40%; key personnel retention risk not adequately modeled.
Mechanism
The Adversarial Review is not optional and cannot be bypassed. It is a separate process designed to find flaws in the consensus — not to validate it.
Legal Significance
Demonstrates stress-testing of the decision — central to Business Judgment Rule defense.
Minority Report
Scenario
One model maintained that the valuation premium was unjustified given comparable transactions. This dissenting view did not converge with the majority.
Mechanism
Minority Reports are preserved permanently and included in the Evidence Bundle. They cannot be removed or suppressed. They prove the board considered — and documented — the opposing case.
Legal Significance
Documented dissent is often more valuable than consensus in litigation defense.
Decision Record Generation
Scenario
Final Panel Confidence Index: 91%. The Decision Record is generated, cryptographically signed, identity-verified, and recorded to EXOCHAIN with deterministic finality.
Mechanism
The Evidence Bundle includes: panel composition, all analyses, deliberation transcripts, adversarial review findings, minority report, convergence scores, participant identity attestations, bailment contract reference, and EXOCHAIN checkpoint.
Legal Significance
Satisfies FRE 901, 803(6), and 902(13/14). Self-authenticating. No network access required for verification.
Trust Architecture
EXOCHAIN: the constitutional substrate.
EXOCHAIN is not a blockchain in the consumer sense. It is a DAG-based event-sourced ledger with Byzantine Fault Tolerant consensus and deterministic finality — purpose-built for evidentiary use cases.
DAG-Based Event Sourcing
Directed Acyclic Graph architecture ensures every event has a cryptographically verified causal chain. Events cannot be inserted retroactively.
BFT Consensus
Byzantine Fault Tolerant consensus means the ledger reaches agreement even if a subset of nodes behaves maliciously. No single node controls finality.
Deterministic Finality
Once a Decision Record achieves finality on EXOCHAIN, it is mathematically immutable. There is no fork mechanism, no rollback, and no administrative override.
Constitutional Rules
Governance rules are enforced cryptographically — not by policy or administrators. The architecture cannot circumvent its own rules, even under legal compulsion.
PII/PHI Isolation
No personally identifiable or protected health information ever touches the ledger. Identity attestation is handled through cryptographic proofs, not raw data.
Open Source & Audited
EXOCHAIN is open source. The codebase is publicly auditable. External security audits are published. Trust is not claimed — it is verifiable.
Legal Standing
Architectural alignment with Federal Rules of Evidence.
Evidence Bundle admissibility is not a marketing claim. It is an architectural design decision. Each element of the Evidence Bundle corresponds to a specific evidentiary requirement.
FRE 901 — Authentication
Rule Text (Summary)
The proponent must produce evidence sufficient to support a finding that the item is what the proponent claims it is.
How decision.forum Addresses This
EXOCHAIN provides cryptographic proof of integrity. The Evidence Bundle includes the EXOCHAIN checkpoint reference, cryptographic hash of all content, and timestamp of finality. No manual chain-of-custody documentation required.
FRE 803(6) — Business Records
Rule Text (Summary)
Records of a regularly conducted activity: made at or near the time of the event; by someone with knowledge; kept in the course of regularly conducted activity; making the record was a regular practice.
How decision.forum Addresses This
Decision Forum sessions are conducted as a regular business practice. Records are generated at the time of deliberation, not reconstructed. Session logs are maintained in the ordinary course of governance.
FRE 902(13/14) — Self-Authenticating Electronic Records
Rule Text (Summary)
Machine-generated records certified by a qualified person, or records produced by an electronic process or system that produces an accurate result.
How decision.forum Addresses This
Evidence Bundles are self-verifying — they carry their own cryptographic proof of integrity and do not require live network access or witness testimony to authenticate.
Evidence Bundle admissibility determinations are made by courts on a case-by-case basis. The above describes the architectural alignment with Federal Rules of Evidence. Consult qualified legal counsel regarding admissibility in specific jurisdictions and proceedings.
Governance Model
The AI-IRB: a three-branch governance structure.
The AI-SDLC Institute governs decision.forum's methodology through a published, peer-reviewable set of Standard Operating Procedures. The governance model draws explicitly on the separation of powers principle — legislative, executive, and judicial functions are kept structurally independent.
Legislative
AI-IRB
Defines the SOPs, methodology, and governance standards. Sets the rules that all Decision Forum sessions must follow.
Executive
Holons
Executes Decision Forum sessions according to AI-IRB standards. Conducts the deliberation, manages panel coordination, generates Decision Records.
Judicial
CGR Kernel
Enforces constitutional rules on EXOCHAIN. Reviews disputes, validates compliance, and maintains the integrity of the governance model.
40+ Standard Operating Procedures are published on GitHub and auditable by any party — clients, regulators, opposing counsel, or independent researchers. No black boxes. No proprietary methodology that can be challenged as unverifiable.
View AI-SDLC Institute SOPsSee a live Decision Forum session.
The most effective way to understand decision.forum is to observe a session in the context of a governance challenge you are currently facing.