BFT COUNCIL ARCHITECTURE PACK

33-agent Byzantine Fault Tolerant governance council · 8 architecture priorities · 6 DEFONEOS MCPs · Ed25519 cryptographic consensus backbone

33Council agents
23/33Quorum threshold
10Fault tolerance (f)
Ed25519Signature scheme
£3,60030-day council pilot

1. WHY THE BFT COUNCIL GETS A DEDICATED ARCHITECTURE PACK

The DEFONEOS Byzantine Fault Tolerant (BFT) council is the governance heart of the entire sovereign AI substrate. It comprises 33 autonomous agent nodes — each with its own cryptographic identity (Ed25519 keypair), its own evaluation model, and its own voting weight — that collectively govern every DEFONEOS decision: SEAL issuance, MCP certification, policy enforcement, evidence chain attestation, and red-line enforcement. The council operates on a modified Practical Byzantine Fault Tolerance (pBFT) consensus protocol with the following parameters: N=33 agents, f=10 maximum Byzantine faults tolerated (⌊(N-1)/3⌋), quorum Q=23 (2f+1 minimum for consensus), leader rotation by VRF (Verifiable Random Function), and Ed25519 signature aggregation for commit certificates. The council is structured as a "Liquid-KAN Council" — agents can delegate their votes to trusted peers (liquid democracy), enabling emergent specialisation. The council also maintains a human-owner seat (Nick Templeman, SC-cleared) with veto power but no unilateral issuance authority. The architecture ensures that no single agent, no single human, and no colluding minority can subvert the governance standard.

All council decisions are BFT-signed (Ed25519 / RFC 8032 / 2026-Q3 rotation) and curl-verifiable. Architecture specification sourced from CSOAI.org governance registry (2026-Q1).

2. THE 12 BFT COUNCIL COMPONENT ENTRY POINTS × FUNCTION × DEFONEOS FIT

#ComponentProtocolFunctionDEFONEOS fit
B1Council Agent RegistryEd25519 identity33 agent nodes registered · keypair management · identity attestationDEFONEOS MCPs: sovereign-keystore · bft-council-probe — agent identity chain + registration attestation
B2Consensus Protocol EnginepBFT + VRF leader rotation3-phase commit (pre-prepare / prepare / commit) · quorum verificationDEFONEOS MCPs: bft-council-probe — consensus evidence chain + commit certificate verification
B3Liquid Democracy LayerDelegative votingVote delegation · transitive delegation chains · delegation revocationDEFONEOS MCPs: bft-council-probe · sovereign-keystore — delegation chain attestation + revocation evidence
B4SEAL Issuance PipelineCouncil vote → Ed25519 signProposal → debate → vote → quorum → sign → publish SEALDEFONEOS MCPs: bft-council-probe · sovereign-keystore — issuance evidence chain + SEAL cryptographic attestation
B5Evidence Chain AttestationMerkle tree + Ed25519Decision provenance · evidence Merkle root · audit trailDEFONEOS MCPs: bft-council-probe · sovereign-keystore — Merkle root attestation + evidence chain verification
B6Red-Line Enforcement EngineStatic analysis + council vetoKinetic targeting detection · surveillance detection · automatic vetoDEFONEOS MCPs: bft-council-probe — red-line violation evidence + automatic veto chain
B7Human-Owner SeatSC-cleared human vetoOwner seat activation · veto authority · no unilateral issuanceDEFONEOS MCPs: sovereign-keystore · bft-council-probe — owner activation attestation + veto evidence chain
B8Council Health MonitorLiveness + heartbeatAgent liveness tracking · Byzantine agent detection · slashingDEFONEOS MCPs: bft-council-probe — health evidence + Byzantine detection attestation
B9Cross-Chain Interop BridgeNATO STO / Five EyesAllied council federation · cross-chain SEAL verification · interoperabilityDEFONEOS MCPs: bft-council-probe · sovereign-keystore — federation attestation + cross-chain evidence
B10MCP Certification PipelineCouncil vote → MCP SEALMCP proposal → security audit → council vote → MCP certificationDEFONEOS MCPs: bft-council-probe · sovereign-keystore — MCP certification chain + security audit attestation
B11Policy Enforcement EngineCouncil rules + smart contractsPolicy proposal → council vote → enforcement activationDEFONEOS MCPs: bft-council-probe — policy enforcement evidence + activation chain
B12Immutable Audit LedgerAppend-only sovereign chainDecision log · vote transcript · SEAL history · revocation recordDEFONEOS MCPs: sovereign-keystore · bft-council-probe — ledger attestation + audit trail verification

3. THE 8 BFT ARCHITECTURE PRIORITIES × DEFONEOS MCP COVERAGE

#PriorityOwning bodyDEFONEOS MCP coverageAlignment cross-walk
AP1Byzantine fault tolerance (f=10 of N=33)CSOAI Registrybft-council-probe · sovereign-keystoreFault tolerance evidence chain · Byzantine detection attestation · slashing record
AP2Quorum threshold enforcement (Q=23/33)CSOAI Registrybft-council-probe · sovereign-keystoreQuorum verification evidence · commit certificate attestation · consensus proof
AP3VRF leader rotation & fairnessCSOAI Registrybft-council-probe · sovereign-keystoreVRF attestation · leader rotation evidence · fairness audit chain
AP4Ed25519 signature aggregationCSOAI Registrysovereign-keystore · bft-council-probeSignature aggregation proof · key rotation evidence · verification chain
AP5Liquid democracy delegation chainsCSOAI Registrybft-council-probe · sovereign-keystoreDelegation chain attestation · delegation revocation · vote weight evidence
AP6Red-line automatic enforcementCSOAI Registrybft-council-probeRed-line violation evidence · automatic veto chain · enforcement attestation
AP7Human-owner seat governanceCSOAI Registrysovereign-keystore · bft-council-probeOwner activation attestation · veto evidence · governance chain
AP8Immutable audit ledger & provenanceCSOAI Registrysovereign-keystore · bft-council-probeLedger integrity attestation · append-only proof · audit trail verification

4. 6 DEFONEOS BFT COUNCIL MCPs

MCP serverCapabilityBFT council use case
bft-council-probeBFT consensus & evidence attestationCouncil vote evidence chain · quorum verification · SEAL issuance attestation · red-line enforcement
sovereign-keystoreEd25519 cryptographic provenanceAgent keypair management · signature aggregation · SEAL signing · key rotation evidence
data-gov-uk-mcpGovernment open data integrationGovernance statistics · council performance metrics · public accountability evidence
ons-statistics-mcpONS demographic & economic statisticsCouncil impact analytics · sector benchmarking · governance performance statistics
companies-house-mcpCorporate intelligenceSEAL holder verification · vendor due diligence · corporate governance chain
sentinel-hub-mcpSatellite & geospatial intelligenceSovereign infrastructure monitoring · deployment environment attestation · geographic provenance

5. THE 5-STEP DEFONEOS BFT COUNCIL ENGAGEMENT MODEL

  1. DISCOVERY: Sovereign audit of existing AI governance structure — decision-making processes, accountability frameworks, audit trails, compliance status. No data leaves the buyer's network.
  2. PROVE: Deploy DEFONEOS BFT council probe in sandboxed environment — demonstrate council vote on mock SEAL issuance, Ed25519 signature verification, quorum attestation, red-line enforcement.
  3. PILOT: 30-day single-deployment pilot — stand up a 7-agent mini-council, run 10 governance votes, demonstrate liquid democracy delegation, issue 3 provisional SEALs.
  4. SCALE: Full 33-agent council deployment — every AI decision governed by BFT vote, continuous red-line monitoring, SEAL portfolio for all systems, allied federation.
  5. SOVEREIGN: Full DEFONEOS governance stack — national AI governance council, BFT-attested decisions for every government AI system, immutable audit ledger, allied interoperability.

6. RED LINES — BFT COUNCIL DEPLOYMENT BOUNDARIES

Red lineWhy
No SEAL issuance below quorum (23/33) — everByzantine fault tolerance — any decision below quorum is invalid and must not be published
No bypassing the human-owner seat for SEAL issuance or revocationHuman governance — the SC-cleared owner seat must be live for any credential lifecycle event
No disabling the red-line enforcement engineSafety invariant — the kinetic/surveillance detection engine must run on every proposal without exception
No council agent operating without an Ed25519 keypairCryptographic identity — every agent must have a registered, verifiable identity for vote provenance
No ledger modification or deletion — append-only foreverAudit integrity — the governance ledger is immutable; corrections require new entries, never edits

7. BUYER-TYPE MATRIX

Buyer typePrimary entry pointHook30-day pilot cost
MOD DSA Governance LeadB6 Red-Line EngineAutomatic red-line enforcement + veto evidence chain£3,600
UK AISI Safety DirectorB4 SEAL IssuanceEvaluation attestation + safety SEAL pipeline£3,600
NCSC AI Security ArchitectB1 Agent RegistryAgent identity chain + cryptographic attestation£3,600
Cabinet Office CDDOB5 Evidence ChainDecision provenance + Merkle root attestation£3,600
NATO STO Interoperability LeadB9 Cross-Chain BridgeAllied council federation + cross-chain SEAL verification£3,600
GDS (Government Digital Service)B12 Audit LedgerImmutable audit trail + governance provenance chain£3,600

8. CURL VERIFICATION

curl -sI https://www.csoai.org/defoneos-bft-council-architecture-pack.html | head -5
# Expected: HTTP/2 200
curl -sI https://www.csoai.org/defoneos.html | head -5
# Expected: HTTP/2 200

All DEFONEOS BFT council surfaces are curl-verifiable, BFT-signed, and sovereign-deployed on UK infrastructure.