📋 DEFONEOS — UK MOD Procurement Tracker

CSOAI Ltd · UK 16939677 · tick-98 · care_score 0.95 · SIGIL-anchored · Friday 16:00 BST BFT review

1. The 12 Named Tenders — Jul to Dec 2026

Priority tiering follows the deal-velocity-tracker (T1 = rep says buy / T2 = rep says go / T3 = rep says watch / T4 = submitted). All deadlines are UK 23:59 unless stated. "Pre-fill status" = how much of the bid-pack is already complete when Nick opens the page.

2. The T-21 / -14 / -7 / -1 Cadence

Every named tender gets four "bid-review" gates before the deadline. Each gate has a SIGIL-anchored artefact appended to the bid-pack in /api/bid-pack/<tender-id>. The cadence is enforced by a Friday 16:00 BST 33-agent BFT pre-flight review of every T1/T2/T2 bid.

All artefacts (a) → (m) land in a per-tender SIGIL-anchored chain at csoai.org/api/bid-pack/<tender-id> (also on disk at /Users/nicholas/csoai-static-deploy2/api/bid-pack/). The 33-agent BFT pre-flight at T-7 takes ~95 LOC of stdlib Python (no external deps) per the bft-council protocol.

3. The Friday 16:00 BST BFT Pre-Flight

Every Friday at 16:00 BST, the 12 Generals × 3 Councils (33 voting seats) convene to review the live T1/T2 status of every active tender. The BFT vote cadence:

1. Call to order 16:00 BST. 12 Generals = each of the 12 named DEFONEOS MCP families (sentinel/os/companies-house/aisstream/c2/…) brings a 1-line "ready/regressed/blocked" flag for the past week.
2. 3 Council briefings. Council 1 = Sovereign Council (12 Generals under 1 convener reporting Section 7 OSA + AUKUS compatibility + no-fifth-eye). Council 2 = Compliance Council (12 reports on NCSC/DSP/EU-AI-Act/ISO-42001). Council 3 = Commercial Council (12 reports on pipeline / pricing / RFP).
3. 33-agent vote per tender. Each of 33 votes = approve / amend / reject. Quorum 25/33. Care score ≥ 0.90 required. Output: per-tender vote-outcome.json appended to api/bid-pack/<tender-id> with Ed25519 sigil hash.
4. Public minutes at csoai.org/bft-minutes/<YYYY-MM-DD> with per-tender vote-count, named-amendments, and per-council report.

4. The 4 KPIs the Buyer-Evaluation Team Reviews

5. The Bid-Pack Artefact Roster — per Tender

Every tender gets all 13 of these SIGIL-anchored artefacts by T-1. The buyer-evaluation team sees only the artefacts they specifically ask for; the remaining are kept in the DEFONEOS Vault.

6. Named Risks and SIGIL-Anchored Mitigations

1. Risk: Named-owner leaves the buyer between T-21 and T-7.
   Mitigation: Backup-owner prospectus in §2 — pre-rehearsed in cold-outreach. Re-bid prepared inside 14 days. SIGIL: api/bid-pack/sigil/contact-change-*.json.
2. Risk: Buyer tightens specification between T-21 and T-7.
   Mitigation: v0.4 → final-proposal-v1.0 cycle inside the T-14 → T-7 window. Re-cost / re-scope preserving pricing-tiers. SIGIL: api/bid-pack/sigil/spec-tightened-*.json.
3. Risk: Competitor (Palantir UK / Anduril UK / BAE) supplies named-references
   Mitigation: Our named-witness shortlist is anchored on 3 named MOD buyer-side champions + 3 named Dstl/DASA/AUKUS-side technical referrals. The "are you really sovereign?" objection is answered with national-sovereign-register + soft-launch-press-pack.
4. Risk: Procurement gate stalls past T+90 after submission.
   Mitigation: Friday BFT persists the status as a SIGIL-anchored apolitical record. If T+90 elapses without award, automatically request "no-fault progress check" via the named-witness shortlist. Care score stays ≥ 0.95.
5. Risk: Buyer asks for an SOC2 / ISO27001 / CSP-A certificate we don't yet have.
   Mitigation: We supply the delivery-accreditation playbook (S1-S5 18-month path, £450k central cost) and offer a Phase-1 paper-evidence pack against the named framework.
6. Risk: Buyer asks "what if we just keep using Palantir Foundry?"
   Mitigation: vendor-pivot-playbook (90-day SOP for moving buyers off Palantir/AWS/GCP) — 5 phases, 12-question brief.
7. Risk: A third party changes the named-tender requirement (e.g. UN amendment, NCSC bulletin, new EU AI Act delegated act).
   Mitigation: Friday BFT agendas carry a perpetual "regulatory watch" item — 12 Generals each scan 1 named regulator per week; any change is SIGIL-anchored inside the same Friday.

7. The 5 Decision Patterns the BFT Reviews Each Friday

1. Bid / No-Bid gate — auto-decided against the 7 named filters in §3 of tender-schedule-2026.
2. Pricing tier decision — £50k shrink / £95k central / £155k premium per pricing-defense.
3. Named-buyer disqualification — automatically block any tender whose sole-buyer-co is in a sanctioned regime or has an unresolvable Section 7 OSA dependency on US CLOUD Act.
4. Resource re-allocation — re-route named-engineer hours across active tenders as the T-1 deadline-bell nears.
5. Escalation — any 5-of-33 amend-pattern with P95 latency > 14 days goes to the next Friday BFT for second-look vote.

8. SIGIL-Anchored Receipts (12 named artefacts)

1. csoai.org/api/bid-pack/sigil/discovery-*.json — every tender-discovery memo Ed25519-signed
2. csoai.org/api/bid-pack/sigil/past-pattern-*.json — every past-procurement-pattern memo
3. csoai.org/api/bid-pack/sigil/witness-shortlist-*.json — 3 named referees per tender
4. csoai.org/api/bid-pack/sigil/proposal-*.json — v0.4 → v1.0 SHA-512 chain
5. csoai.org/api/bid-pack/sigil/pricing-*.json — pricing tier-defence per tender
6. csoai.org/api/bid-pack/sigil/risk-*.json — risk-register chain
7. csoai.org/api/bid-pack/sigil/bft-vote-*.json — 33-agent Friday vote record
8. csoai.org/api/bid-pack/sigil/manifest-*.json — submission-day Ed25519 manifest
9. csoai.org/api/bid-pack/sigil/mfa-confirmed-*.json — buyer-portal MFA confirmation
10. csoai.org/api/bid-pack/sigil/faq-*.json — 12 named FAQ responses
11. csoai.org/bft-minutes/ — public Friday BFT minutes
12. csoai.org/procurement-tracker/ — public read-only ledger (cheque-book transparency)

9. Cross-Walk to the 12 Other DEFONEOS Surfaces