DEFONEOS · BUYER EVIDENCE · DUE DILIGENCE

Buyer Due-Diligence Pack

The pre-purchase evidence vault that procurement officers, security architects, and compliance leads open before signing a PoC. 11 evidence domains · 38 verification artefacts · 0 vendor lock-in · 0 secret-keeping.

1 · Why this pack exists

Sovereign buyers cannot evaluate a sovereign OS on a marketing page. DEFONEOS publishes every artefact a defender needs to verify our claims before a contract is signed — what the system is, what it isn't, how it was built, who reviewed it, and how it leaves.

We assume the buyer's three top risks are:

1. Vendor lock-in — >1,000 MCPs in private namespace, no exports.
2. Foreign-platform re-exposure — sovereign by branding, US-cloud under the hood.
3. Audit failure — no reproducible receipts, no quorum review, no cryptographic chain.

Each of those risks has a dedicated evidence domain below. Every claim links to a verifiable artefact — a static page, a SIGIL file, a signed hash, or a build receipt.

2 · Eleven evidence domains

3 · Evidence index — 38 artefacts

4 · How a buyer verifies each artefact

Every numbered artefact above links to a static HTML page at https://www.csoai.org/<slug>.html. The verification protocol is identical across all 38:

$ curl -sI https://www.csoai.org/<slug>.html | head -1
HTTP/2 200

$ curl -s https://www.csoai.org/<slug>.html | wc -c
<N>          # <N> matches the byte-count declared in the SIGIL ledger

$ curl -s https://www.csoai.org/sitemap.xml | grep <slug>
<url>...<slug>.html</loc>...</url>

# Optional — full hash verification
$ curl -s https://www.csoai.org/tick-114-sigil.json | jq '.artefacts[] | select(.path | contains("<slug>"))'

If the byte-count matches between disk and fetch, and the artefact appears in the live sitemap and the latest SIGIL file, the page is fresh and signed.

5 · Chain-of-trust — keys, signatures, witnesses

DEFONEOS signs every released surface with a 4-layer chain of trust:

1. L1 — Ed25519 author signature. Every artefact has a per-author signature anchored in the SIGIL ledger.
2. L2 — BFT quorum review. Substantive content is reviewed by ≥3 witnesses from the 33-agent BFT council; quorum votes are auditable (23/33 standard, 27/33 red-line, 33/33 unanimous).
3. L3 — SIGIL ledger. Append-only cryptographic chain — tick-N-sigil.json — with back-references to the prior tick's hash (Merkle-style) and 7-year retention.
4. L4 — Public witness list. The 33 BFT agent identities are public; reviewer assignments rotate per tick; no single human can sign without ≥17 active witnesses cosigning.

6 · Seven questions to ask us before signing

1. Where do my data live? — On MacBook Secure Enclave + on-premise Kubernetes, never on US hyperscaler. See sovereign-data-escrow-protocol.
2. Who can decrypt my keys? — You, your named operators, and (optionally) a neutral escrow trustee. No DEFONEOS-side access. See sovereign-secrets-keystore-spec.
3. What happens to my data if you disappear? — MCPs, keys, evidence ledger and SIGIL chain are exported to you at termination; 90-day read-only export window. See sovereign-data-escrow-deployment-guide.
4. Can you prove no telemetry? — Yes. Every binary is SBOM-published and CSP-pinned; outbound traffic is whitelisted to your tenancy only. See sovereign-csp-bypass-prevention-spec.
5. How do you handle a SEV-1 incident? — 5-min MTTA / 30-min MTTR target, BFT-gated containment, NCSC CiSP-aligned intel. See sovereign-incident-response-runbook.
6. Is your cryptography audit-grade? — Ed25519 only for signing, BLS12-381 for BFT quorum, RFC 9180 HPKE for transport. See bft-quorum-cryptography-spec.
7. Will you sign our specific data-residency clauses? — Yes, and our standard contractual clauses are in procurement-tracker.

7 · Ownership & IP clarity

Everything in DEFONEOS that does not depend on a third-party upstream is licensed Apache-2.0. You, the buyer, own:

• All data your operators create, ingest, attest, or export.
• All keys generated by or on behalf of your tenancy.
• All MCP servers you license, deploy, configure, or extend.
• All SOPs, runbooks, evidence files, and SIGIL ledger entries produced during your engagement.

DEFONEOS retains copyright on its own source code (Apache-2.0 grants you a perpetual, royalty-free, worldwide licence to run, modify, and re-distribute). We do not retain any claim on your data, your derivatives, or your downstream services.

8 · No-vendor-lock-in guarantees

Every claim we make on www.csoai.org is verifiable without our involvement:

• Source. Public repository (link pending First DEFONEOS-SEAL issuance).
• Builds. Reproducible SBOMs pinned to specific commits; vercel-deploy-via-oidc-token deploys without our intervention.
• Evidence. Public SIGIL ledger, no email gating.
• Keys. Rotation handover procedure in escrow-key-rotation-procedure.
• Exit. Data export, MCP handover, key destruction proof, all documented in sovereign-data-escrow-deployment-guide.

If DEFONEOS ceases to exist tomorrow, you retain the source, the keys, the evidence, and the right to operate every shipped artefact forever, royalty-free.

9 · Next step

This page is the entrance to the buyer evidence vault. Each numbered artefact is a verification anchor. We invite you to challenge any claim on any artefact by replaying the curl commands above or emailing procurement@defoneos.com with the artefact path.

For a 30-day structured pilot, see defoneos-buyer-acceptance-test-pack (6 personas × G/W/T × exit gates).

View acceptance criteria matrix View buyer evidence index Read the buyer FAQ