Meeting Notes to SoW Converter

Converter purpose

After a meeting, the owner should be able to turn notes into a one-page statement of work without inventing scope. This page gives the slots, the guardrails, and the paste-ready output.

• Write the buyer problem before writing the solution.
• Keep scope capped to 90 days unless the buyer asks for a longer programme.
• Make data boundaries explicit. Public-source and synthetic first.
• Use a fixed-price pilot route before discussing enterprise expansion.
• If a buyer asks for certification, route to csoai-defoneos and the BFT council path.

Meeting notes intake

Fill these eight rows immediately after the call.

One-page SoW output template

Copy this into a document after filling the intake rows.

DEFONEOS 90-day sovereign pilot — draft SoW

Buyer problem
[Use the buyer words. One paragraph.]

Pilot objective
Prove whether DEFONEOS can deliver [outcome] using UK-sovereign, audit-grade, signed, neutral architecture without personal surveillance or kinetic-targeting patterns.

Work package 1 — Evidence and controls
- Map buyer use case to JSP 936, NIST AI RMF, ISO 42001, UK GDPR, and OSCAL evidence.
- Produce a signed evidence-room bundle and red-line register.

Work package 2 — Public-source integration demo
- Connect only approved public, synthetic, or buyer-provided non-sensitive data.
- Demonstrate Common Operating Picture, audit trail, and human oversight.

Work package 3 — Assurance and procurement route
- Produce go or no-go report, residual-risk register, pricing route, and next procurement vehicle.

Success metrics
1. [metric] baseline [x] target [y]
2. [metric] baseline [x] target [y]
3. [metric] baseline [x] target [y]

Commercial
Fixed pilot fee: [choose from pricing card]
Milestones: 30 percent start, 40 percent midpoint, 30 percent final acceptance
Owner gates: DSP, CE Plus, SC, procurement route, buyer data access

Honesty
Draft only until buyer validates scope and procurement route. No endorsement, no certification, no controlled technical data.

Pilot package selector

Use this table to choose the first commercial route.

Risk register starter

Every SoW needs these risks stated openly.

• Certification risk: Cyber Essentials Plus and SC are owner-gated until completed.
• Procurement risk: route may require framework listing or prime sponsorship.
• Data risk: no sensitive buyer data enters a public demo environment.
• Expectation risk: DEFONEOS is an open sovereign OS surface, not a secret MOD-accredited platform today.
• Scope risk: broad platform asks must be reduced to three work packages for a 90-day pilot.

Acceptance criteria library

Select three to five criteria only.

• All pilot pages and evidence artefacts return HTTP 200 from canonical URLs.
• Buyer receives an OSCAL-ready control map for the scoped use case.
• Human oversight log exists for every AI-assisted recommendation.
• No red-line pattern appears in demo, data, or documentation.
• Commercial next step is explicit: stop, extend, framework route, prime route, or grant route.
• A named buyer stakeholder can explain the value in one paragraph without Nick present.

Owner handover checklist

Before sending the SoW, run this checklist.

• Replace every bracketed field.
• Attach only public links or buyer-approved private artefacts.
• Check the pricing card matches the package selected.
• Check the evidence-room link is live.
• Send to one named owner, not a generic list.
• Log the SoW in the CRM and attach the tick-67 SIGIL record.

Milestone and payment schedule

Use this when a buyer asks how the 90-day pilot is governed commercially. Keep it capped and measurable.

Clause library

These clauses are safe starter language. They are not legal advice and should be reviewed before signature.

• Data boundary: The pilot uses public, synthetic, or buyer-approved non-sensitive data only unless a separate written data processing schedule is agreed.
• Human oversight: DEFONEOS outputs are advisory in the pilot. A named human owner remains accountable for every operational decision.
• Red lines: The pilot excludes kinetic targeting, find-fix-finish workflows, kill-order generation, personal surveillance, face recognition, and phone-location tracking.
• Assurance: Governance artefacts are prepared for review and do not represent third-party certification unless expressly issued by the relevant authority.
• Provenance: Pilot artefacts are versioned and hash-recorded. Ledger anchoring is used where the endpoint is available.
• Exit: Either party may close the pilot at a decision gate if the value hypothesis is not validated.

Worked example — public resilience pilot

This example shows how to fill the SoW without creating an overbroad platform promise.

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.

Honesty register

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

• This page is an executable owner pack, not legal advice and not a government endorsement.
• AUKUS-compatible means design compatibility only. No AUKUS partnership is claimed without a signed letter on file.
• DEFONEOS-SEAL is not issued here. Any credential requires the 33-agent BFT council quorum and owner gate.
• No kinetic-targeting, find-fix-finish, kill-order, face-recognition, phone-location, or individual-tracking pattern is included.
• Buyer names and public bodies are routing examples from public procurement context. Nick must verify the current named contact before sending.
• SIGIL anchor is local until the SOV3 ledger endpoint is reachable from this Mac session.
• Generated 2026-07-11T08:01:33Z. File slug: defoneos-mod-meeting-notes-to-sow.