defoneos.mod/launch-day-72-hour-battle-rhythm · csoai.org · ship-grade · tick 97

DEFONEOS — Launch-Day 72-Hour Battle Rhythm · 17-19 Jul 2026

The hour-by-hour, owner-by-owner, SIGIL-anchored battle rhythm that takes DEFONEOS from T-72 (14 Jul Wed) through T+72 (20 Jul Sun). Eight named owners. Seventeen SIGIL-anchored gates. A 33-agent BFT council on hourly stand-up from T-24 to T+24. A hostile-question containment matrix. A 7-day post-mortem template pre-built. The single document the launch team runs the week from.

Window coveredT-72h Wed 14 Jul 00:00 → T+72h Sun 20 Jul 23:59 BST

Named owners8 (Press, Comms, Eng, BFT, Ops, Legal, Growth, Owner)

SIGIL-anchored gates17 (every gate SIGIL-emitted at PASS)

BFT stand-upsHourly T-24 → T+24 (49 stand-ups), then 6-hourly through T+72

Hostile-Q containment matrix14 named press/journalist archetypes × pre-drafted response

Post-mortem template7-day retro pre-built, ready to fill T+72

Risk gates3 hard abort criteria (any one → pause launch)

AuthorityDEFONEOS Sovereign Architecture Board · ratified tick 97

1. The Eight Owners & Their Spans of Control

Owner	Role	Span	Paging
OWNER Nick Templeman	Strategic + sign-off on any >£0 ask	Everything — final word	24/7
PRESS DEFONEOS Communications	Media relations, OpEd placements, hostile-Q handling	All inbound press; OpEds; embargoed list	24/7 T-24 → T+72
COMMS DEFONEOS Social	Tweets, LinkedIn, email, community Discord	All outbound social + Discord + email blasts	24/7 T-12 → T+72
ENG SOV3 / SOV33 substrate on-call	Uptime, deploy, MCP registry, page redirects	All technical surfaces	24/7 T-72 → T+72
BFT 33-agent council chair	Hourly vote on go/no-go, hostile-Q framing, post-mortem	All SIGIL-anchored decisions	24/7 T-24 → T+24, then daily
OPS DEFONEOS Operations	HubSpot deal pipeline, MFA data rooms, BFT voting tool	All customer-facing systems	24/7 T-12 → T+72
LEGAL External counsel on retainer	Pre-clearance of every public statement; libel review	All outbound text + public claims	08:00-22:00 BST T-72 → T+72
GROWTH DEFONEOS BD	Buyer-discovery calls, partnership intros, DASA/NATO DIANA submission	All buyer + partner interactions	08:00-20:00 BST T-72 → T+72

2. The 17 SIGIL-Anchored Gates

Every gate SIGIL-emitted on PASS. SIGIL chain is the immutable launch record. Any gate FAIL = pause launch + 33-agent BFT emergency vote.

#	Gate	Time	Owner	PASS criterion
G1	Tech stack GREEN	T-72h Wed 09:00	ENG	All 30 MCPs reachable, all 60 pages HTTP 200, sitemap 200
G2	Press list locked	T-72h Wed 12:00	PRESS	Embargoed list of 30 named journalists signed-in by 12:00
G3	OpEds submitted	T-48h Thu 09:00	PRESS	2 OpEds filed (The Times + Computer Weekly) — both acknowledged
G4	BFT sign-off on launch assets	T-48h Thu 17:00	BFT	Vote ≥25/33 approve on launch artefact set
G5	Press release embargoed	T-24h Fri 07:00	PRESS	300-word press release embargoed to 17 Jul 07:00 BST — confirmed by 30 journalists
G6	Social pre-scheduled	T-24h Fri 12:00	COMMS	15 tweets + 5 LinkedIn + 1 press release scheduled in Buffer + Hootsuite
G7	Data rooms provisioned	T-24h Fri 15:00	OPS	12 named buyer data rooms provisioned, MFA + 30-day expiry enforced
G8	Discord ready	T-24h Fri 17:00	COMMS	Launch-day Discord thread pinned, BFT-monitored
G9	Hostile-Q matrix reviewed	T-24h Fri 18:00	LEGAL	14 hostile-Q rows cleared by external counsel
G10	HARD ABORT #1: Tech RED	T-4h Fri 03:00	ENG	If any P0 surface 5xx or 30x-loop: HALT + BFT vote
G11	HARD ABORT #2: Press walkback	T-4h Fri 03:00	PRESS	If >3 named journalists signal walkback: HALT + BFT vote
G12	Launch GO/NO-GO	T-2h Fri 05:00	BFT	33-agent BFT GO/NO-GO vote; ≥25 GO = launch
G13	Press release unlocks	T+0 Fri 07:00	PRESS	Embargo lifts at 07:00:00 BST; press release fires
G14	First-pour tweet fires	T+0 Fri 07:01	COMMS	Tweet #1 of 15 fires at 07:01:00 BST
G15	LinkedIn post fires	T+1h Fri 08:00	COMMS	LinkedIn #1 of 5 fires at 08:00 BST
G16	Mid-launch BFT vote	T+24h Sat 07:00	BFT	Vote: continue, pivot, or pause. ≥25 continue required.
G17	Post-mortem template open	T+72h Sun 20:00	OWNER	7-day retro template instantiated, all owners assigned 3 questions

3. The Hour-by-Hour Battle Rhythm (T-72 → T+72)

T-72h — Wed 14 Jul (Pre-launch prep)

Time	Owner	Action
09:00	ENG	G1: tech stack GREEN check — all 30 MCPs + 60 pages probed
10:00	OWNER	Approve all launch-day comms
11:00	LEGAL	Begin hostile-Q matrix review
12:00	PRESS	G2: press list locked + embargo confirmations sent
14:00	GROWTH	Buyer-discovery calls — 8 calls booked for launch week
16:00	BFT	Daily BFT stand-up — review hostile-Q draft
18:00	OPS	Pre-provision all data rooms — test MFA + expiry
20:00	COMMS	Begin social queue pre-loading into Buffer
22:00	OWNER	EOD report — sigil-anchor

T-48h — Thu 15 Jul (Press placement)

Time	Owner	Action
09:00	PRESS	G3: OpEds submitted to The Times + Computer Weekly
11:00	LEGAL	Libel review of all 15 tweets + 5 LinkedIn posts
13:00	COMMS	Final social calendar pre-load complete
15:00	ENG	Final sitemap regen — 471 URLs verified
17:00	BFT	G4: BFT sign-off on launch assets (vote ≥25/33)
19:00	OWNER	Owner-GO confirmed in writing
21:00	OPS	Discord launch-day channel opened, mods briefed
23:00	OWNER	EOD report — sigil-anchor

T-24h — Fri 16 Jul (Final lockdown)

Time	Owner	Action
07:00	PRESS	G5: press release embargoed to 30 journalists
09:00	ENG	Continuous uptime monitoring — 5-min probes
12:00	COMMS	G6: social fully scheduled (15 tweets + 5 LinkedIn + 1 press release)
15:00	OPS	G7: 12 data rooms provisioned, MFA + expiry verified
17:00	COMMS	G8: Discord thread pinned, BFT on rotation
18:00	LEGAL	G9: hostile-Q matrix final-pass cleared
19:00	BFT	BFT stand-up — review all 9 G-gates — vote confidence
21:00	OWNER	EOD report — all gates green
23:00	OWNER	Final go/no-go sleep check

T-4h — Fri 17 Jul 03:00 (HARD ABORT CHECK)

Time	Owner	Action
03:00	ENG + PRESS	G10 + G11: HARD ABORT check — tech RED? press walkback? If yes → HALT + BFT emergency vote
04:00	BFT	Emergency BFT vote if either G10 or G11 tripped
05:00	BFT	G12: GO/NO-GO vote — ≥25/33 GO required to launch
06:00	OWNER	Owner-GO confirmed in writing — final
06:30	COMMS	Pre-launch buffer load — confirm schedule

T+0h to T+6h — Fri 17 Jul 07:00-13:00 (Launch window)

Time	Owner	Action
07:00	PRESS	G13: Embargo lifts. Press release fires.
07:01	COMMS	G14: Tweet #1 fires ("DEFONEOS is live — UK sovereign public services OS, audit-grade, signed, neutral").
07:30	PRESS	First press inquiry response — hostile-Q matrix in play
08:00	COMMS	G15: LinkedIn #1 fires.
09:00	BFT	Hourly BFT stand-up begins — vote: continue / pivot / pause
10:00	GROWTH	First buyer-discovery call of launch week
11:00	ENG	Tech uptime check — 1-min probes
12:00	OWNER	First-hour SIGIL — record launch metrics
13:00	OWNER	6-hour launch metrics review

T+24h — Sat 18 Jul 07:00 (Mid-launch BFT vote)

Time	Owner	Action
07:00	BFT	G16: Mid-launch BFT vote — continue / pivot / pause. ≥25 continue required.
08:00	OWNER	Day-1 retro opened in retro template
12:00	OPS	First buyer inquiries triaged — first data room accesses recorded
18:00	GROWTH	First partnership inbound reviewed
22:00	OWNER	EOD Day-1 SIGIL

T+48h to T+72h — Sun 19-20 Jul (Cooldown)

Time	Owner	Action
Sun 09:00	BFT	6-hourly stand-up cadence resumes
Sun 14:00	OWNER	Day-3 review — pivot / continue decision
Sun 20:00	OWNER	G17: Post-mortem template open, 3 questions per owner
Mon 21 Jul 09:00	BFT	Weekly BFT cadence returns
Mon 21 Jul 12:00	OWNER	Launch-week SIGIL emitted — retro starts

4. The 14-Row Hostile-Q Containment Matrix

Each row: archetype, real hostile Q, SIGIL-anchored response (≤280 chars tweet-safe). Drafted by PRESS + LEGAL, BFT-voted.

#	Archetype	Hostile Q (paraphrase)	Response skeleton
H1	Open-source sceptic	"Another 'open-source' Defence OS — and what makes it real and not vapourware?"	"30 MCPs live, 60 pages public, 15 repos cloned, all SIGIL-anchored. We publish the receipts."
H2	AUKUS sceptic	"AUKUS-compatible is marketing. Show the technical interop."	"AUKUS AI interoperability requires sovereign data + audit-grade supply chain. National Sovereign Register has 18 attestations, Ed25519-signed."
H3	National-security sceptic	"Open-source Defence AI is a foreign-intelligence gift."	"Open ≠ uncontrolled. Every artefact Ed25519-signed. No fifth-eye dependency. Section 7 OSA + UK GDPR + EU AI Act compliant."
H4	Procurement cynic	"MOD won't buy from a 1-person UK Ltd."	"DSP registered; Cyber Essentials filed; SC clearance in process; DASA bid ready. We're a Tier-1 supplier in formation, not a startup."
H5	Vendor-funder sceptic	"Who's funding you? VC strings?"	"CSOAI Ltd UK 16939677 — no VC, no foreign capital. Sovereign by construction."
H6	Anti-AI press	"This is just another AI hype launch."	"AI is one layer of an 8-layer sovereign substrate. Defence layer doesn't even use generative AI by default — it's C2 + ISR + compliance."
H7	"Where's the team?"	"Single founder, no staff — how do you scale?"	"33-agent BFT council + sovereign agent mesh — we're a sovereign AI OS, not a 50-person consultancy. The substrate scales itself."
H8	Anti-cryptography	"Ed25519 / SIGIL — that's not real security theatre."	"Ed25519 = same primitive as Bitcoin + Signal + WireGuard. SIGIL = immutable evidence chain, mathematically tamper-evident."
H9	"Not invented here"	"This re-wraps existing OSS — what's novel?"	"The novel layer is sovereign-by-construction: audit-grade, signed, neutral. No fifth-eye. UK-sovereign, AUKUS-compatible. The OS stack is novel."
H10	EU AI Act purist	"EU AI Act Article 50 — transparency obligations?"	"Article 50 5/5 compliant. EU Cyber Resilience Act Annex I 13/13 ready. We treat compliance as a feature, not a tax."
H11	"Open-source means free"	"If it's open-source, why would anyone pay?"	"Open-source ≠ free-as-in-beer. Support contracts, sovereign hosting, compliance-as-a-service, DEFONEOS-SEAL certification. £95k–£1.4M contracts."
H12	"What's the moat?"	"Any incumbent can clone this — what's your moat?"	"Sovereign-by-construction: NCSC SC-01 CAF 14/14, Ed25519 SIGIL chain, 33-agent BFT council. The moat is the receipt chain."
H13	"Why not buy Palantir/Anduril?"	"Why bother with open when Palantir/Anduril already do this?"	"Foreign CLOUD Act exposure + fifth-eye dependency + closed source. UK public sector needs a sovereign alternative. DEFONEOS is that."
H14	"What's the kill shot?"	"If DEFONEOS fails, what fails?"	"UK public-sector AI remains vendor-locked to foreign CLOUD Act exposure. The sovereignty window closes. We don't think this is acceptable."

5. The 3 Hard Abort Criteria

Tech RED: any P0 surface 5xx or 30x-loop for >30 consecutive minutes during T-24 → T-4. → HALT + 33-agent BFT emergency vote (≥25 continue required within 2h).
Press walkback: >3 of 30 embargoed journalists signal walkback or pull coverage during T-12 → T-4. → HALT + OWNER personal call to each walkback.
Adverse legal: external counsel flags any outbound text as legally unsafe at T-2h. → HALT + emergency counsel review + rewrite before T-1h.

6. The 7-Day Post-Mortem Template (pre-built, ready to fill T+72)

Three questions per owner × 8 owners = 24 base questions. Plus 5 cross-cutting BFT questions. Total 29 questions, all evidence-anchored.

#	Question	Owner	Output type
1-3	What worked? What didn't? What would you change?	Each of 8 owners	3-paragraph narrative + 3 SIGIL-anchored evidence links
4-6	Which BFT vote surprised you? Which hostile Q caught you off-guard? Which gate was tightest?	PRESS + COMMS	3-paragraph narrative + SIGIL links
7-9	What SIGIL gates slipped? What 5xx did we see? What didn't deploy?	ENG + OPS	Tabular — every gate listed, every drift recorded
10-12	Which data room had highest conversion? Which press had highest pickup? Which partnership advanced?	GROWTH	Tabular — conversion %, pickup count, partnership stage
13-15	Which legal call-out did we miss? Which public statement required walkback? Which libel risk emerged?	LEGAL	Narrative + diff
16-18	Which BFT vote was closest? Which General dissented? Which vote pattern surprised?	BFT	Vote tabular + dissent narrative
19-21	What did the owner sleep on? What got dropped? What came back better?	OWNER	3-paragraph reflective narrative
22-24	What 3 things would we re-do? What 3 to drop? What 3 to keep?	OWNER	3×3 table — pre-formatted
25-29	Cross-cutting: Was the soft-launch a sovereign moment? Did the SIGIL chain hold? Did the press land? Did buyers move? Did partners move?	BFT + OWNER	5 one-paragraph verdicts

7. The 4 KPIs Tracked Hourly During T-24 → T+72

KPI	Source	Owner	Hourly threshold
Tech uptime	ENG probes	ENG	>99.5% (≤6 min downtime/hour)
Press pickup	PRESS tracker	PRESS	>5 named outlets/hour during T+0 → T+6
Social engagement	COMMS dashboard	COMMS	>10k impressions/hour T+0 → T+6
Buyer signal	GROWTH tracker	GROWTH	>2 named buyer inbounds/hour T+2 → T+24

8. Hand-off & Cadence After T+72

Mon 21 Jul 09:00: weekly BFT stand-up cadence resumes.
Mon 21 Jul 12:00: launch-week SIGIL emitted; retro owners assigned 3 questions each.
Fri 24 Jul 17:00: full 7-day retro closed, BFT vote on changes for week 2.
Mon 28 Jul 09:00: week-2 cadence: weekly BFT, daily PRESS, daily GROWTH, on-call ENG.
Fri 31 Jul 17:00: launch + 2-week review, BFT vote on scale-up or pivot.

SIGIL: T97-launch-day-72-hour-battle-rhythm-3a8f5b7c9d2e · care_score 0.96 · BFT 33-agent vote: 30 approve / 3 amend / 0 reject (quorum 28/33)
Authority: DEFONEOS Sovereign Architecture Board, ratified 2026-07-14
License: Open — UK MOD / public-sector press / defence primes free to cite with SIGIL preserved
Owner: DEFONEOS Owner + 8 named launch owners · launch@csoai.org