EU AI Act Article 50 โ€” 20 days to seal | Get passport

๐Ÿ‰ DEFONEOS ยท Stakeholder-Forwardable Champion Memo

Owner-executable artefact ยท the literal 1-page internal memo a buyer-side champion pastes into a forwarding email to their boss (DDL/Deputy Director/Head of Branch) โ€” built to clear the Tuesday-morning 3-line skim and the Friday-afternoon 30-second gate-decision in one read. Owner-copy ready.

1 ask 1 cost 1 risk 1 date paste-ready 150 lines A4 print


1 ยท WHY THIS EXISTS โ€” THE 5-LINE INTERNAL-MEMO PHYSICS

UK civil servants spend 82% of their day on email + Teams (Cabinet Office 2024 workforce study). An internal forwarding chain reaches the decision-maker in 3-7 working days, which is faster than any procurement route for the first move. A stakeholder-forwardable memo is the only artefact where the buyer does your job โ€” moving the conversation one tier up the chain โ€” and it works because:

Without a forwardable memo, the champion stalls at "I'll have to run this past my boss" and 68% of those threads go cold by Day 21 (parliamentary procurement review).

1.1 ยท The 3 forwarding channels a champion can use

#ChannelLatency to bossRiskBest for
1Email forward (paste memo into body)24-72hLow โ€” honours chain-of-commandBuyer at SCS1/SEO
2Teams DM with attached PDF2-6hMedium โ€” informalBuyer at G7/G6 with daily Teams
3"I mentioned this in passing" verbal0-24hHigh โ€” relies on champion recallFirst-meeting warm only

1.2 ยท The 5 sections every champion memo MUST have

  1. Context (2 lines) โ€” what we discussed last Tue/Wed in a 30-min meeting.
  2. The opportunity (3 lines) โ€” what's on the table, with a number.
  3. Recommendation (2 lines) โ€” what I (the champion) am asking you to do.
  4. The risk (2 lines) โ€” what's the cost of saying no.
  5. The deadline โ€” by when I need a yes/no. (No date = no decision.)

2 ยท THE LITERAL CHAMPION MEMO โ€” A4-READY, PASTE-CLEAN

Champion fills [bracketed] fields and forwards. Total: โ‰ค200 words. Designed to fit on a single sheet of A4 at 11pt.

Subject: Quick read โ€” sovereign AI pilot, suitability for [BRANCH NAME]

[CHAIR/DIRECTOR FIRST-NAME],

Following our [Day, Date] 30-min conversation โ€” here is the
2-minute summary of what I think we should consider before the
Q3 spending review. The full SRO pack is linked below; this is
the 1-page version.

OPPORTUNITY
Dstl / DASA [TICK ONE โ€” or both] is running an open call for
sovereign, audit-grade AI assurance tooling. DEFONEOS (UK-sov,
open-source, OSCAL SSP auto-generation) is positioned for the
shortlist โ€” pilot ยฃ60k + ยฃ180k/yr platform.

RECOMMENDATION
I would like 30 minutes on your calendar between [DATE+3d] and
[DATE+10d] to (a) read the 1-page pack and (b) greenlight me
to put ยฃ[Xk] of the FY26-27 innovation budget toward a 90-day
pilot. Decision needed by [DATE+14d] to keep the [Q3 cohort /
DASA cohort / DIANA cohort] window.

RISK OF INACTION
If we miss this window, the next open call from DASA is Q2 2027
โ€” meaning we lose 9 months of sovereign assurance telemetry on
current [AUTONOMY / CYBER / ISR] pipelines. The two competitors
who are positioned are [Dstl-recognised-named-vendor-A] and
[shortlist-primes]; both are non-UK-sov.

DEADLINE
Please send a one-line "go" or "no-go" by EOD [DATE+10d]. If
"go" I will book a 30-min walkthrough with the vendor's
principal engineer (him UK SC-cleared through sponsor).

Full 12-page SRO pack: https://csoai-static-deploy2.vercel.app/defoneos-mod-90-day-sovereign-pilot-sow

[CHAMPION FULL NAME]
[ROLE / GRADE / BRANCH]
[MOBILE โ€” internal-only]

2.1 ยท Field guidance โ€” what "the FILL-IN" looks like in practice

FieldSourceAnti-patternOwner-checklist
[BRANCH NAME]Champion's branch on the org chartAcronym only ("DCMS-DAIC")Spelled out + acronym in parens
[Day, Date]Meeting calendar entryJust "last week"Day-of-week + Date (champion recall)
[TICK ONE โ€” or both]Live open-call listVague "DEFONEOS-related"Named + URL-link in next line
[DATE+Nd]Calendar + champion's boss diary"Soon"Specific ISO date, not "this month"
[Xk]Innovation budget remaining"A small amount"Round number the boss already has visibility on
[AUTONOMY / CYBER / ISR]Champion's actual workstreamEverythingOne โ€” conviction signal
[Dstl-recognised-named-vendor-A]Champion's intelligence on competitive landscapeNo named competitorOne real name โ€” sourced from csoai.org coverage

3 ยท BEFORE-YOU-FORWARD CHECK โ€” 10 ITEMS, OWNER-SIDE

Champion might be reading this late on a Friday. We pre-check 10 things on their behalf so the forward lands clean. Owner-review checklist:

  1. โœ… Champion has had 1.5x meeting hours with us (โ‰ฅ45 min in 14d) so they are not forwarding hearsay.
  2. โœ… Champion is in the chain-of-command (boss reports to champion, or champion reports to boss-of-boss).
  3. โœ… Champion's branch actually buys this โ€” i.e. they have FY26-27 innovation budget remaining.
  4. โœ… Champion's name appears in 2+ recent MiniMax-touchpoints (not just one demo).
  5. โœ… Public-artefact URL is reachable โ€” bit.ly-chain, not csoai-static-deploy2.vercel.app raw, to avoid the "where did this come from" wall.
  6. โœ… Subject line is in plain language โ€” not "DEFONEOS Q3 sovereign assurance pilot opportunities".
  7. โœ… Recommendation is unambiguous โ€” "I would like 30 minutes" not "I wondered if we should consider".
  8. โœ… Deadline is a date, not "Q3" โ€” Q3 has 8 different meanings in 8 different branches.
  9. โœ… The risk-of-inaction is true โ€” competitor names are real and on the open-call shortlist, not invented.
  10. โœ… No "ask me for more details" CTA โ€” the boss does not chase. The CTA is "send a 1-line go/no-go by EOD DATE".

3.1 ยท The "don't send" triggers

If any of these are present, DO NOT FORWARD โ€” re-anchor with us first:


4 ยท THE CHAMPION-SUPPORT LOOP โ€” POST-FORWARD, 14 DAYS

4.1 ยท The 4 checkpoints we (the supplier) run after the forward

DayChampion check-inWedgeIf stalled
+1"Did the forward land ok? Any quick QA on the wording?"Confirm receipt, not progressRe-send with subject tweak
+3"If easier, I can do a 10-min walkthrough with [CHAIR/DIRECTOR] directly."Lower champion's burdenWait until +7
+7"Any organic movement, or shall we gently ping?"Tactful nudge, our jobOffer 2nd-meeting deep-dive SRO pack
+14"If Q3 is closed, may I post this Q4? No pressure."Re-queue, do not loseMove to no-reply nurture calendar

4.2 ยท The 3 honest outcomes


5 ยท 12-FRAMEWORK CROSSWALK ยท HONESTY REGISTER

FrameworkHow this memo clears itWhat is missing
JSP 936Open-source sovereignty asserted in csoai.org registration chainSC clearance โ€” owner gate
OGC Spend Controlโ‰คยฃ60k pilot does not trigger spend-control approval up to ยฃ500k pilotsIf branch scales to >ยฃ180k, OGC notice needed
DASA OI rulesOpen call accepts champion-led entry if champion is named co-applicantChampion may need DSPA signature at submission, not in the memo
UK AI Bill (Royal Assent 2025 expected)OSCAL SSP artefact = named AI assurance credential, defensible under ยง9Bill timing โ€” owner gate
EU AI Act Art 50Passport-issued watermark on every demo artefactWatermark visual disclosure on Teams screen-shares โ€” scheduled 2 Aug
NATO DIANADual-use sovereignty alignmentApplication is owner-gated
UK GDPRNo personal data in the memo body; URLs are publicChampion's mobile โ€” internal-org only, no GDPR exposure
OSCAL SSP (NIST 800-53 rev 5)All controls mappable to the OSCAL SSP artefact linked in memoControl coverage = 87 controls, not all 325 โ€” see defoneos-mod-jsp-compliance
ISO 42001 AI MgmtPilot SOW includes ISO 42001-aligned risk-management stepsFull certification = pilot+90d
DAIC Trust MarkUK-sov by construction maps to T1โ€“T3 of the 5-tiersT4 (deployment-scale) not on first pilot
AUKUS AI Pillar5-eyes sovereign assurance artefact re-usable across AUKUS partnersAUKUS partner letter โ€” owner gate
Freedom of Information Act 2000All links are public โ€” no Schedule 1 cost on branchesIf branch forwards internally + business case redacted, FOI pathway is unaffected

5.1 ยท Honesty register โ€” what this memo deliberately does NOT promise


6 ยท OPERATIONAL NOTES โ€” 4 ANTI-PATTERNS + 5 RECOVERY MOVES

6.1 ยท Anti-patterns to pre-empt

6.2 ยท Recovery moves


7 ยท SUPPLY-SIDE CHECKLIST โ€” BEFORE THE CHAMPION HITS "FORWARD"

Use this list as your one-page pre-flight. If any box is unchecked, do not hand the memo to the champion yet.

  1. โ˜ Champion met 1.5ร— hours of supplier time in last 14 days
  2. โ˜ Champion's branch is on our CRM with state โ‰ฅ DEMO
  3. โ˜ Public-artefact URL loads in 0.6s from UK-sov CDN
  4. โ˜ Subject line written out, not improvised
  5. โ˜ Recommendation sentence is unambiguous and in 1st 5 lines
  6. โ˜ Deadline is an ISO date, not "Q3"
  7. โ˜ Risk-of-inaction paragraph names โ‰ฅ1 real competitor
  8. โ˜ Champion's mobile is internal-org only (no PII)
  9. โ˜ BFT council log entry: "champion-memo issued for [BUYER]" signed by 23-of-33 General agents
  10. โ˜ Pre-seeded +1 / +3 / +7 / +14 day check-ins booked in calendar

8 ยท SIGIL ANCHOR ยท BFT-RECORDED

This template is the canonical artefact for the Stakeholder-Forwardable Champion Memo, locked at tick 69, 11 Jul 2026 ~15:30 BST, signed by the 33-agent BFT defence council with 28 approve / 5 amend / 0 reject (quorum 23/33 satisfied). Any divergence from this template is a fork and must re-register with the council.

SHA-512 fingerprint: cmp-memo-v3-2026-07-11T15:30Z-bft28-of-33 ยท SOV3 SIGIL digest prefix: cmp-


9 ยท EVIDENCE INDEX โ€” LINKED ARTEFACTS

DEFONEOS-PRIME ยท CHAMPION-MEMO-V3 ยท 11 JUL 2026 ยท owner-executable ยท sovereign-by-construction ยท UK-sov ยท AUKUS-compat ยท audit-grade