Validation Plan & Summary Report

Document reference: GFTCL-VP-001 · Framework: GAMP 5 Category 5 · EU Annex 11

FortressAI Research Institute · Norwich, Connecticut

Patents: USPTO 19/460,960 · USPTO 19/096,071 — © 2026 Richard Gillespie

This document defines how the GaiaFTCL vQbit Quantum VM is validated (the plan) and

records the outcome (the summary report). It is the controlling document for the

qualification effort.

---

Part A — Validation Plan

Scope

The complete bespoke (Category 5) system: vQbit VM, C⁴ algorithm rail, Franklin

orchestrator, substrate store, CLI, and the federation surface. The host macOS is

Category 1 infrastructure and out of scope except for stated system requirements.

Approach

Risk-based validation per GAMP 5 Category & Supplier Assessment

and Risk Assessment. The V-model is verified on two independent

gates:

1. Build-time gate — 156 swift test GAMP 5 tests under Tests/GAMP5/ (IQ/OQ/PQ/MQ).

2. Runtime gate — 18–19 in-app checks (SovereignQualificationRunner) against the

live shipping stack inside Franklin.app.

Deliverables

URS, FS, SDS, Configuration Spec, RTM, Risk Assessment, IQ/OQ/PQ protocols + reports,

Qualification Catalog, and this plan/summary. All are controlled documents in this

section.

Acceptance criteria

A release is qualified when: all 156 build-time tests pass; all in-app checks return

CALORIE; the RTM shows full bidirectional coverage; and every run seals a re-verifiable

MQ receipt.

Roles

Developer-operator (FortressAI Research Institute) authors and executes; the independent

build-time and runtime gates provide testing independence; a third-party assessor can

re-verify any receipt without developer access.

---

Part B — Validation Summary Report

Result

CALORIE — qualified. The qualification gates pass on the current baseline.

Evidence

Each qualification run writes a federation-cosigned receipt to

cells/xcode/qualification_receipts/ (MQ-*.json). Each receipt re-computes its witness

hash from its sealed canonical witness, so the result is independently reproducible.

Deviations

Tracked through Operational Procedures → change control.

Any failed check blocks the release until resolved and re-qualified.

Research validation (QC VM + ECDLP + PoW learning)

Independent of the in-app qualification runner, the research publication bundle is regenerated from code and sealed JSON:

Frozen findings (2026-06-05): allMathLayerOK=true, allLearningClaimsOK=true, qaLayerClosed=true, allRewardClaimsOK=false (L7 not chain_accepted — honest), qc020ImprovementTrend.trendStatus=insufficient_hits until timed hits accumulate.

→ Research-Publication · paper cells/xcode/docs/SHOR_ECDLP_RESEARCH_PAPER.md

cells/xcode/scripts/peer_review_research_dataset.sh

Release statement

On a passing baseline the system is released for operational use. Re-qualification is

required after any change to a High/Critical configuration item, a substrate schema

addition, or a toolchain/OS upgrade.

---

*Cross-references: RTM ·

Qualification Catalog · IQ ·

OQ · PQ.*

*Federation cosignature: pending — gaiaftcl wiki sign --section GAMP5.*