EU AI Act Article 50 — 20 days to seal | Get passport
Co-pilot proof pack

Evidence Room Index

A buyer-safe evidence-room map for DEFONEOS: which proof object to send, which claims are live, which are draft, and which require Nick as the owner gate.

8evidence shelves
5bundle recipes
12framework mappings
0sensitive-data links
Use now: open this page during the owner workflow, copy the relevant block, verify the honesty register, then log the result in the DEFONEOS CRM. This is designed for a 30 minute action window, not for passive reading.

Evidence-room purpose

A buyer should not need to trawl 200 pages. This index turns the DEFONEOS estate into a clean evidence room: what exists, what it proves, what is draft, and what needs owner validation.

Evidence-room shelf map

The shelf map is the default order for a buyer due-diligence folder.

ShelfContentsStatus
Identity and supplierCompany number, public contact, registered office, domain ownership, responsible ownerOwner verified before send
Security postureCyber Essentials status, CE Plus plan, retention controls, access controls, incident pathHuman-gated for CE certification
AI governanceJSP 936 mapping, human oversight, transparency, red-line register, BFT governance routeDesigned and documented
Technical proofMCP registry, 240-test references where available, Vercel byte-verification, deployment logsLive pages plus local evidence
CommercialPricing card, 90-day pilot SoW, payment milestones, procurement vehiclesDraft unless buyer validates route
Case studiesIllustrative public-service scenarios, no classified or sensitive operational dataIllustrative only
ProvenanceSIGIL files, SHA hashes, sitemap entries, C2PA-ready media notesLocal plus ledger when reachable
Owner gatesDSP, SC, CE Plus, DASA, DIANA, UKDI, first sendNick action required

Core links to send

These are the links most likely to move a buyer from curiosity to validation.

Evidence bundle recipes

Send one of these bundles instead of improvising.

Buyer questionBundleEmail line
Can this pass governanceJSP 936, AI governance, red-line register, evidence vaultThe governance layer is designed first. These links show the control map and the honesty register.
What does it costPricing card, 90-day pilot SoW, deal economicsThe cleanest route is a capped 90-day pilot with explicit milestones.
Is it sovereignSovereignty page, deployment comparison, data room indexThe surface is UK-sovereign by design and separates public facts from owner-gated evidence.
Can we see a demoLive demo fallback script, digital twin page, sensor layerThe public demo is intentionally non-sensitive and excludes personal surveillance.
Who signs assuranceBFT council page, DEFONEOS-SEAL register, honesty registerThe credential is not issued without quorum. This page shows the route, not a false certificate.

Due-diligence checklist

Before sending an evidence-room bundle, run these checks.

Evidence-room manifest block

Paste this into a buyer email when asked for proof.

DEFONEOS evidence room — public links only
1. Governance: /defoneos-jsp936 and /defoneos-compliance-crosswalk
2. Security posture: /defoneos-security and /defoneos-threat-model
3. Sovereignty: /defoneos-sovereignty and /defoneos-deployment-comparison
4. Commercial: /defoneos-mod-pricing-card-onepager and /defoneos-mod-90-day-sovereign-pilot-sow
5. Pilot route: /defoneos-mod-meeting-notes-to-sow
6. Provenance: /defoneos-evidence-vault and tick-67-sigil.json

Honesty: live public evidence, draft commercial route, owner-gated certifications, no endorsement claim.

Byte-verification protocol

Before sending a buyer to an artefact, verify that the canonical alias serves the same bytes as the local file. This avoids the stale-alias trap.

cd /Users/nicholas/clawd/csoai-static-deploy2
for p in defoneos-mod-pricing-card-onepager.html defoneos-mod-90-day-sovereign-pilot-sow.html defoneos-mod-meeting-notes-to-sow.html; do
  local_bytes=$(wc -c < "$p")
  remote_bytes=$(curl -sL "https://csoai-static-deploy2.vercel.app/${p%.html}" | wc -c)
  code=$(curl -sL -o /dev/null -w "%{http_code}" "https://csoai-static-deploy2.vercel.app/${p%.html}")
  echo "$p local=$local_bytes remote=$remote_bytes http=$code"
done

If the values differ, redeploy before sending. A 308 on the .html route is normal because cleanUrls redirects to the extensionless path.

Evidence status vocabulary

Use this exact vocabulary in emails and proposals.

StatusMeaningAllowed phraseForbidden phrase
LIVEPublic page or artefact returns HTTP 200 and byte matches local source.Live public artefactCertified evidence
DRAFTContent prepared but not submitted to a buyer or authority.Draft for owner reviewApplication submitted
DESIGNEDControl or workflow has a documented design but no external exercise yet.Designed control pathOperationally proven
OWNER-GATEDRequires Nick personal, company, payment, or authentication action.Owner-gated next stepCompleted by agent
ILLUSTRATIVEScenario or case study used for explanation only.Illustrative non-sensitive scenarioReal MOD case study

Buyer due-diligence questions and answers

QuestionEvidence-room answerHonesty guardrail
Are you accredited?Show governance route, Cyber Essentials gate, and DEFONEOS-SEAL process.Do not claim completed accreditation before owner gate.
Can you handle classified data?Explain public-source and synthetic demo boundary, plus future secure route.Do not accept classified data in the public pilot.
Are you replacing existing platforms?Position as sovereign evidence and integration layer that can sit beside incumbent systems.Do not claim rip-and-replace.
What is open source?Explain open sovereign surface, MCP architecture, and public proof links.Do not imply all buyer integrations are public.
How do we procure?Route through DASA, G-Cloud, prime partner, direct award threshold, or discovery.Buyer must validate procurement path.

12-framework crosswalk

Every page in this tick is written as an owner-executable artefact and an audit trail. These mappings are design mappings, not third-party certifications.

FrameworkHow this page mapsHonesty status
EU AI ActTransparency, human oversight, logging, post-market monitoring, and high-risk discipline when a workflow crosses into regulated public-service use.Designed control language. Verify per-buyer before external submission.
GDPR and UK GDPRData minimisation, lawful basis notes, retention windows, subject-access response path, and no personal-surveillance pattern.Designed control language. Verify per-buyer before external submission.
JSP 936Assurance case language, operator accountability, safety case evidence, and escalation logging suitable for UK defence AI review.Designed control language. Verify per-buyer before external submission.
JSP 440Protective marking, supplier-security posture, evidence handling, and separation of public facts from owner-gated sensitive data.Designed control language. Verify per-buyer before external submission.
NIST AI RMFMap, Measure, Manage, and Govern rows for every buyer artefact, with clear residual-risk ownership.Designed control language. Verify per-buyer before external submission.
ISO 42001AI management-system controls, role ownership, change control, review cadence, and documented competence.Designed control language. Verify per-buyer before external submission.
NIST PQCCryptographic-agility language, no false PQC certification claim, and upgrade path for signed evidence bundles.Designed control language. Verify per-buyer before external submission.
NATO STANAGInteroperability language only, no NATO endorsement claim, and neutral alliance-compatible evidence formatting.Designed control language. Verify per-buyer before external submission.
AUKUS Pillar IIAUKUS-compatible technology framing only, no partnership claim unless a signed letter exists.Designed control language. Verify per-buyer before external submission.
OSCALMachine-readable control catalogue and component-definition path for the evidence room.Designed control language. Verify per-buyer before external submission.
Five Eyes export disciplinePublic-source and EAR ITAR awareness note, no controlled technical data in the page.Designed control language. Verify per-buyer before external submission.
C2PA 2.0Content provenance, artefact signing, and media lineage notation for decks, screenshots, and demo recordings.Designed control language. Verify per-buyer before external submission.

Honesty register

The register below is deliberately explicit so the artefact stays usable in a UK-sovereign procurement conversation without overclaiming.