🛡️ DEFONEOS: BFT Council — Red-Line Motions History

Full red-line audit trail. Red-line motions are the highest-stakes motions in the BFT council: they require a 27/33 supermajority (vs. 23/33 standard), R5 (Public & Research) endorsement, and R1 owner cosign. This page lists every red-line motion since the council's activation, with vote tallies, amendments, and the specific red-line vector that triggered the motion class.

Red-line threshold: 27/33 (81.8%) · ring-distinct approval: R2≥4/6, R3≥5/8, R4≥6/12, R5≥4/6 · owner cosign required for SEAL.
Snapshot: 2026-07-17T03:30:00Z · Source: BFT minutes (tick-117) + red-line audit log.

📊 Red-Line Motion Aggregate (2026 Q1-Q3)

Total Red-Line Motions

38 / 142

26.7% of all motions are red-line class. Average approval rate: 99.1%. Average amendments per red-line: 0.42.

RED-LINE

Red-Line Approval

38 / 38

100% approval. 0 rejections. 16 motions required 33/33 unanimous (constitutional-class + red-line).

CONSENSUS

Red-Line Vetoes

Zero motions blocked by R5 (Public & Research) red-line veto. All red-line vectors cleared on first review.

CLEAN

Amendments Integrated

16 red-line motions received R5 amend proposals. All 16 were integrated into rolled motion text before final vote.

REFINED

Owner Cosign Rate

38 / 38

100% owner cosign on red-line motions. R1 Ed25519 signature on every motion. SEAL-eligibility preserved.

SEAL-READY

Audit Trail Completeness

100%

All 38 red-line motions byte-verifiable, Ed25519-signed, BLAKE3-anchored to SIGIL stream, public-record.

VERIFIABLE

🔴 Red-Line Vector Coverage

Each red-line motion is triggered by one or more of the 7 red-line vectors. Coverage breakdown:

Red-Line Vector	Motions Touched	Description	Last Invoked
US CDN	14	Detection of US-content CDN (Cloudflare, Fastly, Akamai-US, Cloudfront) on sovereign MCPs.	2026-07-09 (M-128)
US Root CA	3	Detection of US-trusted root CA (DigiCert, Sectigo-US, Let's Encrypt via US-edge) on sovereign certificate chain.	2026-06-22 (M-104)
US Cloud API	11	Detection of US hyperscaler API endpoint (aws.com, azure.com, gcp.com) in sovereign MCP code path.	2026-07-12 (M-131)
US NTP	2	Detection of US-NTP-pool.time.nist.gov or time.google.com dependency in sovereign time sync.	2026-05-14 (M-061)
US Telemetry	9	Detection of US-vendor telemetry beacon (Sentry, Datadog, Mixpanel, Segment.io).	2026-07-04 (M-118)
US-Vendor JS	6	Detection of US-vendor JavaScript (Google Analytics, Mixpanel, Hotjar) loaded by sovereign surfaces.	2026-07-01 (M-115)
Kinetic Patterns	0	Detection of strike-package / find-fix-finish / kill-order patterns. HARD STOP — never observed.	N/A

📜 Full Red-Line Motion History (Most Recent First)

M-140 — SBOM-type-breakdown publication RED-LINE

Date: 2026-07-17T03:00:00Z · Triggered by: SBOM category classification change (10 sensor / 8 defence / 7 civil-service / 3 compliance / 2 core).

Tally: 33/33 (R1✓ R2:6 R3:8 R4:12 R5:6) · Amendments: 0 · Owner cosign: ✓

Result: PASSED UNANIMOUS. SBOM-type-breakdown page deployed static-only on www.csoai.org (20711b). Tick-118 expansion surface.

M-137 — Pen-test summary publication (PT-2026-Q3-C2) RED-LINE

Date: 2026-07-16T20:30:00Z · Triggered by: PT-2026-Q3-C2 cycle results publication — security evidence domain.

Tally: 33/33 (R1✓ R2:6 R3:8 R4:12 R5:6) · Amendments: 0 · Owner cosign: ✓

Result: PASSED UNANIMOUS. Pen-test summary deployed (18317b). 0 CRIT / 0 HIGH / 3 MED→0 / 9 LOW→0 reported.

M-136 — Disclosure policy PGP key rotation RED-LINE

Date: 2026-07-16T20:00:00Z · Triggered by: Ed25519 disclosure PGP key rotation (fingerprint refresh, exp 2028-05-14).

Tally: 33/33 (R1✓ R2:6 R3:8 R4:12 R5:6) · Amendments: 0 · Owner cosign: ✓

Result: PASSED UNANIMOUS. New PGP fingerprint published on disclosure policy (16013b). 3 backup channels unchanged.

M-131 — US-cloud-API detection in compliance-passport-mcp RED-LINE

Date: 2026-07-12T08:00:00Z · Triggered by: Initial scaffold referenced aws-sdk for s3 backup; replaced with sovereign OCI-equivalent.

Tally: 32/33 (R1✓ R2:6 R3:7 R4:12 R5:6) · Amendments: 1 (R3 amend: explicit OCI-only mandate) · Owner cosign: ✓

Result: PASSED. aws-sdk dependency removed from all 30 MCPs. SBOM refreshed.

M-128 — US-CDN detection in observability dashboard RED-LINE

Date: 2026-07-09T14:00:00Z · Triggered by: Initial observability stack referenced Cloudflare R2 for log archival; replaced with sovereign Hetzner Storage Box.

Tally: 33/33 (R1✓ R2:6 R3:8 R4:12 R5:6) · Amendments: 0 · Owner cosign: ✓

Result: PASSED UNANIMOUS. Cloudflare R2 removed. Logs archived on Hetzner Storage Box (DE/EU).

M-118 — US-telemetry detection in cesium-globe-mcp RED-LINE

Date: 2026-07-04T11:00:00Z · Triggered by: Initial Cesium-ion usage included Bing Maps Aerial; replaced with sovereign OS Open Zoomstack.

Tally: 33/33 (R1✓ R2:6 R3:8 R4:12 R5:6) · Amendments: 0 · Owner cosign: ✓

Result: PASSED UNANIMOUS. Bing Maps replaced. Cesium globe now sovereign-only basemap.

M-115 — US-vendor-JS detection on public surfaces RED-LINE

Date: 2026-07-01T15:00:00Z · Triggered by: Google Analytics 4 detected on tick-100 csoai.org landing; removed CSP-bypass.

Tally: 33/33 (R1✓ R2:6 R3:8 R4:12 R5:6) · Amendments: 0 · Owner cosign: ✓

Result: PASSED UNANIMOUS. GA4 removed. CSP tightened. Tick-108 IR-TLS-CSP-bypass resolved.

M-104 — US-root-CA detection in certificate chain RED-LINE

Date: 2026-06-22T10:00:00Z · Triggered by: Initial cert chain included Sectigo-US root; replaced with sovereign HARICA TLS root.

Tally: 31/33 (R1✓ R2:5 R3:8 R4:12 R5:6) · Amendments: 2 (R2 amend: HARICA cross-sign + R3 amend: cert pinning) · Owner cosign: ✓

Result: PASSED. HARICA TLS adopted. Cert pinning active on www.csoai.org.

M-061 — US-NTP detection in sovereign time-sync RED-LINE

Date: 2026-05-14T09:00:00Z · Triggered by: Initial time sync referenced time.google.com; replaced with sovereign NTP pool (uk.pool.ntp.org).

Tally: 33/33 (R1✓ R2:6 R3:8 R4:12 R5:6) · Amendments: 0 · Owner cosign: ✓

Result: PASSED UNANIMOUS. All sovereign MCPs now sync to uk.pool.ntp.org only.

🔁 Red-Line Process Diagram

Red-line motion lifecycle (canonical):

  1. Detection         — red-line vector scanned across 30 MCPs + 569 pages
  2. Motion drafted     — R3 (Compliance) or R5 (Public) sponsors
  3. Quorum check       — 27/33 supermajority required
  4. Ring-distinct gate — R2≥4/6, R3≥5/8, R4≥6/12, R5≥4/6
  5. Amendments         — any ring may amend; rolled into text
  6. Final vote         — recorded with Ed25519 sig + BLAKE3 anchor
  7. Owner cosign       — R1 signs for SEAL-eligibility
  8. Public minutes     — deployed to /defoneos-bft-council-public-minutes.html
  9. SBOM refresh       — if motion changes SBOM category, sbom-index refreshes
 10. SIGIL anchor       — motion nonce appended to SIGIL stream

🧷 Cross-Links

BFT Council Public Minutes — full motion history (142 motions, tick-117)
Council Vote Tally Probe — real-time tally endpoint design (tick-118)
Vote Tally by Ring — per-ring drill-down (tick-119)
SBOM Index — 30 MCPs indexed + 7-vector red-line scan (tick-117)
SBOM Type Breakdown — per-MCP risk + SEAL-eligibility (tick-118)
Pen-Test Summary — PT-2026-Q3-C2 results (tick-116)
Disclosure Policy — PGP fingerprint + 8 promises (tick-116)

✅ Verdict: 38/38 red-line motions approved. 100% owner cosign. 0 R5 vetoes. 16 amendments integrated. All 7 red-line vectors scanned across 30 MCPs + 569 pages. 35/35 ring red-line vectors PASS. Compartment csoai-defoneos only.