★ MasterPilot Execution v3Steps & Deliverables

Pilot Execution v3 — Steps & Deliverables, explained

🔄 Patent-filing date realignment · 18 Jun 2026
Patent FD target shifted from 15 Jun 2026 to 26 Jun 2026. All FD+N statutory and decision dates shift accordingly: §39 clock starts 26 Jun · complete specifications due 26 Jun 2027 (§9(1)) · PCT decision 26 Dec 2026 · US/EU national-phase entry 26 Dec 2028 · Request for Examination 26 Jan 2029. Marketing public-disclosure window also shifts: founder 1-to-1 outbound to known DP targets continues pre-FD under NDA; public marketing (newsletter · pillar pages · founder LinkedIn cadence · PR note · webinar invites) unlocks Mon 29 Jun 2026 (W5) post-FD. Engineering W1-W14 pilot timeline holds: demo lock Fri 26 Jun · Verified Go-Live Decision Tue 01 Sep.
Plain-English description of every step in the v3 plan, with the status of each deliverable and a link where it already exists. Source of truth = Execution Plan v3 (.md). Advisory — final go/no-go & risk acceptance are human QA + Founder decisions; Verixa never claims "validated."
Status key:  DRAFTED framework / template / spec exists (linked)   PLANNED execution pending — evidence required   LOCKED committed date   GATE go/no-go control

The model — three phases

1 · Demo-ready 26 Jun (LOCKED) — a segregated evaluation environment running all six workflows + MIRA on synthetic data. It is a fixed commercial commitment with no validation dependency; it drives onboarding and the design-partner LOI.
2 · Verified version Target 1 Sep → buffer 15 Sep — a controlled-SDLC build that Verixa verifies (Verixa does not run customer IQ/OQ/PQ). Closes with the supplier assurance pack (G-7) and a signed quality agreement (G-8).
3 · Partner validation Sep+ — the design partner runs IQ/OQ/PQ and intended-use validation, leveraging the G-7 pack. Language rule throughout: "verified under our SDLC; customer validates intended use" — never "validated."

Schedule — what happens each week, and why

WeekWhat happens & whyGate
W1
Jun 01
Kick-off & long-lead starts: approve plan versions; start MIRA V7 (AI-copilot provider assurance) and O3 (qualify the AI providers Anthropic/Azure as suppliers); draft G-7 (supplier assurance pack) and G-8 (quality agreement); decide the PDF library (shared by the inspection-export and AI-governance packs); stand up the CI verification-gate so evidence is auto-captured; secure the design-partner LOI; confirm both hires. Front-loading here is what keeps August from becoming a crunch.
W2
Jun 08
Build the two highest-risk integrity items: WP-4 (e-signature substrate verification) and WP-13b (fail-closed AI audit). Onboard the CSV/CSA + RA contractor.
W3
Jun 15
WP-2 subset and WP-1 single-tenant lock — lock the demo down to one tenant.
W4
Jun 22–26
Demo hardening into the G-DEMO gate.DEMO-READY 26 Jun
W5
Jun 30
G-JUN Go/No-Go review; confirm the full-stack build hand (hire #1).G-JUN
W6
Jul 06
Kill-check: if two or more critical items are red, scope narrows or the baseline moves — automatically, no debate. This is the control that prevents an unrealistic all-six-by-Sept plan from drifting.KILL-CHECK
W7
Jul 13
Front-loaded start of WP-12 (inspection export + scorecard + test authoring) and WP-13 (AI governance pack); WP-10 (Findings→CAPA gate, pulled forward because WP-12 depends on it); WP-8, WP-9. Weekly evidence burndown begins.
W8
Jul 20
WP-12 / WP-13 complete; MIRA guardrail verification starts as each guardrail lands; G-7 populated continuously from W7 (so August is closure, not first authoring).
W9
Jul 31
Release-candidate freeze + G-8 quality agreement SIGNED — a hard gate.G-8 SIGNED
W10–W13
Aug
Verification closure (not first authoring); G-7 closure; MIRA provider pack; O3; security + tenant isolation (P6) + DR; enablement kit; defect closure.
W14
Sep 01
Target go-live — each workflow classified at the per-workflow gate (production-verified / not-verified / demo-only / deferred).GO-LIVE TARGET
W15–16
Sep 1–15
Buffer — contingency only, not a baseline. Teams plan to Sep 1.
15 SepHard backstop — any workflow still unverified defers to a change-controlled wave.BACKSTOP

Deliverables & gates — what each is, status, and link

Deliverable / gateWhat it isStatusLink
Design-partner LOISigned letter of intent from a design partner; gates the pilot and unblocks G-8.DRAFTED template · PLANNED signature (end Jun)LOI template
Demo-ready (G-DEMO)26 Jun segregated eval env — all 6 workflows + MIRA on synthetic data.DRAFTED test pack & scenarios · 26 JunDemo scenarios · Test RTM
WP-4 — e-sig substrate verificationVerifies the electronic-signature substrate (part of the integrity core; owned by senior devs).PLANNED build W2
WP-13b — fail-closed AI auditThe AI-gateway fail-closed audit path (integrity core).PLANNED build W2
WP-12 — inspection export + scorecardHash-reproducible inspection-export pack + scorecard + test authoring (the build hand's ring-fenced scope).PLANNED front-loaded W7
WP-13 — AI governance packThe AI governance evidence pack (intended use, human oversight, monitoring).DRAFTED build instr. + SOP · PLANNED packBuild instruction · VRX-SOP-501
WP-10 — Findings→CAPA gateThe observation→finding→CAPA chain WP-12's export depends on (pulled to W7).PLANNED W7
MIRA V7 — provider assurance packProvider-assurance pack for the MIRA AI copilot (a top-2 risk; guardrail verification front-loaded W8–W12).PLANNED from W1
O3 — supplier qualificationQualify the AI providers (Anthropic / Azure) as suppliers.DRAFTED SOP · PLANNED qualificationVRX-SOP-701
G-7 — supplier assurance packThe supplier / SaaS-vendor assurance evidence pack the partner leverages for validation. Populated continuously W7→Aug.DRAFTED SOPs · PLANNED populate/closeVRX-SOP-701 · VRX-SOP-912 · 📖 detailed guide
G-8 — signed quality agreementThe quality agreement with the design partner — a hard gate to be signed by W9.DRAFTED SOP frameworks · PLANNED signature (W9)VRX-SOP-913 · VRX-SOP-702
Security (P6) + tenant isolation + DRSecurity, tenant-isolation, and disaster-recovery verification.PLANNED Aug
Enablement kitCustomer validation enablement & go-live kit.DRAFTED SOP · PLANNED kitVRX-SOP-907
Commercial Pilot Verification PlanThe risk-based verification approach (HIGH→direct evidence; MED→scripted; LOW→review/supplier).DRAFTEDVerification Plan v1.0

Capacity — the two required hires (non-negotiable)

AddScopeConfirm byStatus
+1 Full-stack build handWP-12 inspection export + scorecard + test authoring only — NOT the integrity core. (Senior devs keep WP-4 / WP-13b.)W5 (productive by W7)PLANNED — confirm
+1 Fractional CSV/CSA + RA contractorVerification evidence, G-7 pack, G-8 agreement, enablement kit, Part-11 framing.W2PLANNED — confirm

The two binding controls the team must respect

W6 kill-check — recognition of the top risks is not control; the W6 gate is the control. ≥2 red ⇒ narrow scope or re-baseline, automatically.
Per-workflow go-live rule — at W14 each workflow is "production-verified" only if: build complete · risk-based verification complete · evidence in G-7 · covered by signed G-8 · no open critical blocker. QA will not label a workflow "verified" without its evidence — the buffer does not change that.