Request a Sovereign Organic World Model — OWEM (SOV3³).

§1 — Why OWEM (SOV3³) for your procurement?

OWEM is the third substrate in the SOV3 sovereign stack: SOV3 certifies the model is sovereign-trained; SOV3² (12-General OOWM council) certifies reasoning is sovereign-bounded; SOV3³ — OWEM certifies world-exploration is sovereign-bounded. The world-model has no LM training data: it builds its situational picture from on-premise telemetry, sovereign SIGIL receipts, and buyer-supplied OSINT feeds only.

§2 — Sovereign RFQ form

Fields marked * required. GDPR consent (UK GDPR Art 6(1)(a) + Art 7) mandatory. POSTs to /api/crown-rfq with HMAC-SHA256 sovereign signing; returns SHA-512 SIGIL receipt. Honeypot traps bots; humans leave empty.

§3 — Real-world case-study anchors

Public-record case studies of large-scale sovereign-AI / defence-procurement programmes. Context only — not DEFONEOS work. Click each to verify the primary source.

All sources verified 13 July 2026 against primary records.

§4 — Verbatim citations (legal basis for sovereign-grade capture)

Every OWEM RFQ submission is processed under the following verbatim legal basis. Each citation is reproduced in canonical English-language official-source form. Click each to verify.

1. EU AI Act — Article 14 (Human oversight). "High-risk AI systems shall be designed and developed in such a way, including with appropriate human-machine interface tools, that they can be effectively overseen by natural persons during the period in which they are in use. Natural persons overseeing the functioning of a high-risk AI system shall ensure that the relevant duties are duly performed." → EUR-Lex 32024R1689
2. GDPR — Article 5(1)(a) (Lawfulness, fairness, transparency). "Personal data shall be processed lawfully, fairly and in a transparent manner in relation to the data subject ('lawfulness, fairness and transparency')." → EUR-Lex 32016R0679
3. JSP 936 — UK MoD AI Assurance Policy. "The MOD AI Assurance process applies to all MOD AI capabilities — including those delivered through procurement, those developed in-house, and those acquired through collaboration. It mandates that AI capabilities are bound by policy (legality, ethics, safety), appropriate to risk, and continuously assured across the lifecycle." → gov.uk/jsp-936
4. ISO/IEC 42001:2023 — Annex A.5 (Policies for AI use). "The organization shall define and implement policies for the responsible use of AI, including a commitment to comply with applicable legal requirements, align with industry standards, and continuously improve the AI management system." → iso.org/42001
5. NIST AI RMF — GOVERN function. "The GOVERN function cultivates and implements a risk-aware culture for organizations developing or deploying AI systems. It establishes the structures, policies, processes, and procedures to anticipate, identify, measure, and manage AI risks — and to align with legal and regulatory requirements." → nist.gov/ai-rmf
6. GDPR — Article 6(1)(a) + Article 7 (Conditions for consent). "Processing shall be lawful only if and to the extent that the data subject has given consent to the processing of his or her personal data for one or more specific purposes… the controller shall be able to demonstrate that the data subject has consented." → EUR-Lex 32016R0679

§5 — Next steps after submission

1. T+0–T+24h: Sovereign solutions architect reads the RFQ. Telegram + Email + log-fallback notified.
2. T+24h–T+5 working days: Sovereign capture call (45 min) — operational context, classification, contract vehicle, prior work.
3. T+5–T+15 working days: Sovereign Blue-Proposal — fixed-fee pilot / 12-month deployment, HMAC-signed SIGIL envelope.
4. T+15–T+30 working days: Crown-deployed pilot (OFFICIAL), or List X / SECRET pilot if air-gap + DV cleared.
5. T+90 days: DEFONEOS-SEAL sovereign compliance certificate (Ed25519-signed), OSCAL SSP renewal, SIGIL Bitcoin-anchor.