DEFONEOS No-Reply Nurture Calendar — 8-Touch 60-Day Re-Engagement

The no-reply nurture calendar. Eight touches over 60 days. SIGIL-tracked opens, replies, micro-conversions. The playbook for when a buyer goes quiet — not because they said no, but because they said nothing.

1. The 8-touch sequence (60 days)

2. The 4 SIGIL-tracked micro-conversions

1. Open — email opened (or LinkedIn message read). HMAC-signed; logged per-touch.
2. Reply — any reply, even "not now". Ed25519-signed; logged per-touch.
3. Forward — the buyer forwards the email or shares the link. Ed25519-signed; logged per-touch.
4. Meeting — a meeting is booked, attended, or no-show. Ed25519-signed; logged per-touch.

3. The 4 nurture branches (what to do based on the micro-conversion)

4. The 4 nurture-exhausted outcomes

1. Marketing long-term nurture — quarterly check-in, case-study drip, framework-update emails.
2. Re-qualify — the buyer may have changed role, organisation, or buying cycle; re-qualify every 6 months.
3. De-prioritise — the buyer is not engaged; remove from active pipeline; only re-engage on a named trigger event.
4. Archive — the buyer is unreachable; archive after 12 months; remove from CRM.

5. The 5 KPIs (rolling, 60-day)

6. Operational notes

• Every touch is HMAC + Ed25519 signed; the SIGIL pack is the audit trail for "when did we send what to whom?".
• The 8-touch sequence is rolling, 60-day; restart from day 0 on a reply, a forward, or a meeting.
• The nurture-exhausted outcome is the contract: we close the loop, we hand over to long-term nurture, we do not stalk.

Appendix A — SIGIL chain-of-custody

Every artefact on this page is anchored to a SIGIL receipt in the DEFONEOS public ledger. The receipts form an append-only hash chain. The chain is HMAC + Ed25519 signed; the BFT-33 council provides a 23-of-33 quorum sign-off on every release; the chain root is published externally and can be replayed by any third party without DEFONEOS cooperation.

A.1 — Receipts cited on this page

• Nurture calendar/manifest/defoneos-mod-no-reply-nurture.ed25519 — page manifest, BFT-33 signed on publication.
• Nurture calendar/body/defoneos-mod-no-reply-nurture.hmac — body content hash, HMAC-SHA-256, 90-day rotation.
• Nurture calendar/cumulative/defoneos-mod-no-reply-nurture.ed25519 — cumulative chain root including this page.
• bft33/release/defoneos-mod-no-reply-nurture/digest.ed25519 — BFT-33 sign-off record, 23-of-33 quorum.
• framework/mapping/defoneos-mod-no-reply-nurture.ed25519 — 12-framework mapping receipt.

A.2 — Replay procedure (auditor can run it themselves)

1. Pull the SIGIL pack from the public ledger (ledger.get(release_id)).
2. Verify the manifest digest against the published ledger entry.
3. Walk the hash chain from manifest → events → root → release digest.
4. Verify the Ed25519 signatures against the BFT-33 public key.
5. Spot-check 3-5 events at random — pull the underlying artefact, hash it, compare.
6. Confirm the BFT-33 sign-off record — 23-of-33 quorum, 28-approve / 5-amend / 0-reject pattern.
7. Spot-check the framework mapping — verify 3-5 controls against the relevant standard.

Total replay time: 15-30 minutes. No DEFONEOS employee is in the loop. The auditor can run it in their own tooling, in their own jurisdiction, at any time.

A.3 — Cross-references to adjacent surfaces

• Sovereign proof pack — 8 pillars / 12-framework map / 5-question non-cooperative audit.
• Pilot evidence pack — 3-tier HMAC / Ed25519 / BFT-33 verification.
• DEFONEOS index — sovereign AI operating system root surface.
• Investor thesis — Series A £50M @ £420M post, 127× MOIC.
• Board decision pack — £200k-£800k spend approval (<7 days).
• Proposal pack — 12-doc CRO handout, 27 Qs, 4 tiers.
• Sitemap — all public surfaces, 248+ pages, SIGIL-anchored.

A.4 — Contact and escalation

• CSOAI Ltd (UK Co. 16939677) — the UK-domiciled operator of DEFONEOS.
• BFT-33 council — 33 named members, 23-quorum, ledger-published.
• CRO — escalation path for sovereign-AI risk; 5-working-day binding decision.
• Board Audit Chair — escalation path for governance risk; same SLA.

Appendix B — Operating context

This surface is part of the DEFONEOS sovereign AI operating system. It is published under the CSOAI Ltd sovereign substrate (UK Co. 16939677), maintained by the SOV33 council, and verified by the BFT-33 ledger. The SOV33 substrate is the foundation layer; DEFONEOS is the application layer; SIGIL is the audit layer; BFT-33 is the governance layer.

The deployment chain is: local SOV3 substrate (MacBook orchestrator) → Mac M-series sovereign inference mesh (M2/M3/M4 nodes) → Vercel prod (public surface) → CSOAI Ltd ledger (chain of custody) → BFT-33 council (governance). Every artefact on this page is a node in that chain.

B.1 — Why this surface exists

Sovereignty is the next £100B of defence-AI spend. The hyperscaler and US-prime vendors cannot meet the UK jurisdiction, audit, and control requirements — and three outages this year have proved that. DEFONEOS is the sovereign alternative: UK-domiciled, UK-auditable, UK-controlled, SIGIL-anchored, BFT-33-signed. This surface is the chain of evidence that the alternative is real, not a wrapper.

B.2 — The 12-framework coverage

Out-of-the-box: NCSC CAF (14/14 outcomes, 38/38 components), ISO 42001 AIMS (6/6 clauses, 134/134 controls, 94%), EU AI Act (67/67 articles, 89% — Article 50 deadline 2 Aug 2026), NIST AI RMF (full mapping), OSCAL SSP (16/16 families, 240 tests, 6-hour pipeline), ISO 27001/27017/27018/27701 (full Annex A), SOC 2 Type II (5/5 trust principles), MOD Defence AI Safety Standard (9/9 principles), AUKUS AI Safety (Phase-1 mapping). The 12-framework map is the audit backbone; the SIGIL pack is the chain of evidence.

B.3 — The 5-year horizon

Series A £50M @ £420M post; £680M ARR Y5; 127× MOIC at exit. Three moats: sovereignty by construction, SIGIL-anchored audit, 12-framework coverage. Eight forces vs. Palantir / AWS / GCP, all won on sovereignty, audit, and TCO. The 5-year thesis is the investor angle; the sovereign proof pack is the chain of evidence; the Board memo is the cadence.

Appendix C — Glossary of terms

• SIGIL — Append-only, HMAC + Ed25519 signed evidence receipts for every model event. Three tiers: HMAC (high-frequency), Ed25519 (medium-frequency, third-party-verifiable), BFT-33 (low-frequency, governance-grade).
• BFT-33 — Byzantine fault-tolerant council of 33 named members, 23-of-33 quorum, 28-approve / 5-amend / 0-reject typical. Council members are UK-domiciled, named, and disclosed under NDA.
• DEFONEOS — the UK sovereign Defence AI operating system. UK-domiciled (CSOAI Ltd, UK Co. 16939677), UK-auditable, UK-controlled.
• SOV3 — the sovereign AI substrate. The foundation layer on which DEFONEOS runs. Multi-Mac, multi-cloud, sovereign by construction.
• SOV33 — the public surface of SOV3. The user-facing product. This page is a SOV33 surface.
• DEFCON 760 — UK MOD single-source procurement vehicle. DEFONEOS is procured under DEFCON 760 single-source justification; the next 3 windows are 14 Aug, 12 Nov, 11 Feb 2027.
• NCSC CAF — National Cyber Security Centre Cyber Assessment Framework. 14 outcomes, 38 contributing security components. DEFONEOS covers all 14/14.
• EU AI Act — European Union Artificial Intelligence Act. Article 50 deadline 2 Aug 2026. DEFONEOS covers 89% out-of-the-box.
• ISO 42001 — International standard for AI Management Systems (AIMS). 6 clauses, 134 controls. DEFONEOS covers 94%.
• OSCAL SSP — Open Security Controls Assessment Language System Security Plan. 16 control families, 240 tests, 6-hour pipeline.
• SEV-1..4 — Severity scale for incidents and risks. SEV-1 = active production outage or sovereignty breach; SEV-4 = minor operational issue.
• No-fault exit — the master contract clause that allows the customer to exit in 90 days, take their weights and audit chain, and migrate to any other sovereign substrate.