Synthesis Ledger

02 Consensus Math

02 / Consensus Math: The Drift Detection System

The Synthesis Ledger does not rely on subjective human reviews. It operates on Consensus Mathā€”a deterministic framework where every AI interaction is audited against its permanent Arweave blueprint. This is the Drift Detection System (DDS) in action.

The Logic: The Basis Points of Sovereignty (BPS)

In the Horpestad Standard, integrity is not a "pass/fail" grade. It is a high-resolution metric called BPS. One basis point represents 0.01% of logic alignment. A perfect score of 10,000 BPS signifies 100% adherence to the Atomic blueprint.

The BPS Calculation Formula

To ensure this is copyable for developers and academics, the logic for calculating the Basis Points of Sovereignty is defined as:

BPS = ( SUM( Validation_i * Weight_i ) / Sensitivity_Max ) * 10,000

Where:

  • Validation_i: A binary value (1 or 0) representing whether a specific logic field in the AI output matches the Arweave schema.
  • Weight_i: The criticality assigned to that field (e.g., financial calculations have higher weight than prose style).
  • Sensitivity_Max: The total possible weight-sum defined in the Atomic's custom_outputs.

The Adversarial Audit Cycle

Every time the Sovereign Engine runs, it executes a three-stage mathematical reconciliation:

  1. The Brain Phase: The raw AI reasoning is generated.
  2. The Auditor Phase: A secondary, adversarial model scans the Brain's output for "Logic Drift" or "Hallucination" by comparing it to the JSON Schema stored at ar://Y544...LM.
  3. The Reconciler Phase: The final BPS score is calculated and prepared as a payload for the Base Mainnet Ledger.

Thresholds and Quality Strikes

The Ledger enforces a hard-coded 7800 BPS floor.

  • BPS >= 9500: šŸŸ¢ STABLE. The logic is operating at peak efficiency.
  • 9500 > BPS >= 7800: šŸŸ” DEGRADED. The logic is still functional but showing signs of drift.
  • BPS < 7800: šŸ”“ CRITICAL. This triggers a Quality Strike.

Example: Audit Failure

If a user runs an audit where the liquidity_ratio calculation deviates from the Arweave blueprint:

  • Expected: 0.85
  • Received: 0.62
  • Result: BPS drops to 7,234.
  • Action: System issues a Quality Strike and anchors the failure hash to the Ledger.

Governance: Strike Protocol

Under the governance of the Genesis 90 Council, if an Atomic accumulates 3 Quality Strikes, the Ledger marks it as isObsolete = true at the Registry address: 0x3fB0a9a5755f43A044ff0A9E9aC4B55f96220ECa. Once obsolete, the recipe is decommissioned, forcing the ecosystem to upgrade to a superior version.