# Patent-Truth QC Report — P01 / P02 / P02b

**Audit date:** 2026-06-06
**Auditor:** Patent-Truth QC harness (Cowork port of Patent/IP Pack v1.5.1) — invoked via `anthropic-skills:patent-truth-qc`
**Audit scope:** P01 (Platform Validated Model Lockstep), P02 (Cryptographic Per-Inference Audit · Model Version Governance · Agent Qualification), P02b (AI Output Segregation Engine) — provisional filing bundles, drawings, build manifests
**Jurisdiction:** India (IP India, ordinary provisional). FTO scope extends to US / EP / GB / AU / KR / CN per `05_FTO_Opinion/FTO_Raw_Research/INTERNATIONAL_JURISDICTION_ASSESSMENT.txt`.
**Classification:** CONFIDENTIAL — Attorney-Client Privileged Work Product.

---

## 1. Executive Status

**STATUS: BLOCKED.**

**Primary blocker:** No approved patent source-of-truth register (`ip/spec/patent-source-of-truth.yaml`) exists in this workspace. The only `patent-source-of-truth.yaml` file located is the skill template at `~/.claude/skills/patent-truth-qc/templates/patent-source-of-truth.yaml`, which is a generic template, not a counsel-approved project baseline. Per Patent-Truth QC doctrine, artifact-alignment QC cannot be promoted to PASS without a counsel-approved source-of-truth baseline that locks: (i) the approved invention concept text per patent; (ii) the approved claim seeds (deferred at provisional, but baseline still required for spec consistency); (iii) the approved reference-numeral registry; (iv) the approved drawing-to-spec crosswalk; (v) approved figure list and titles.

This is a CRITICAL baseline-governance gap. Final status MUST remain BLOCKED until that register exists and is counsel-approved, regardless of how clean other findings are. All other findings below are advisory pending baseline approval; they cannot be acted upon as authoritative until the baseline is locked.

**Secondary blocker:** No patentability and no regulatory adequacy can be QC-asserted here:
- Patentability conclusions: `Counsel determination required.`
- Pharma/Biotech regulatory conclusions: `Regulatory SME determination required.`
- Jurisdiction-bound conclusions: `Conclusion fact-dependent — jurisdiction required.` (Primary jurisdiction is India for provisional filing; multi-jurisdiction exposure noted but out of QC scope.)

---

## 2. Severity Counts

| Severity | Count |
|---|---|
| CRITICAL | 1 |
| HIGH | 4 |
| MEDIUM | 10 |
| LOW | 6 |
| **Total findings** | **21** |

---

## 3. Findings Table

Schema (24 columns per Patent-Truth QC doctrine):

| # | Finding ID | Severity | Status | Patent truth ref | Jurisdiction | Evidence strength | Confidence | Artifact area | Artifact path | Section/line/element | Issue | Fix in URS | Fix in Code | Fix in Patent Spec | Fix in Diagrams | Diagram QC issue | Header/Footer issue | Patentability risk | Pharma/Biotech reg risk | Reg evidence basis | Evidence required | Owner | Blocked until | Reviewer required |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | PTQC-BASELINE-BASELINE-01 | CRITICAL | OPEN | n/a (baseline absent) | IN (provisional) | Direct file-system evidence (no register file) | High | BASELINE | `ip/spec/patent-source-of-truth.yaml` (expected; not present) | Workspace-wide | No counsel-approved source-of-truth register exists for P01/P02/P02b. Only the generic skill template at `~/.claude/skills/patent-truth-qc/templates/patent-source-of-truth.yaml` is present. Per QC doctrine, artifact-alignment QC cannot be promoted to PASS without this register being created, populated with locked truth fields per patent, and counsel-approved. | Create register: invention concept, claim seeds, approved figure list, approved reference-numeral registry, approved drawing-to-spec crosswalk, approval signature block (counsel name, date, scope). | n/a | n/a | n/a | n/a | n/a | Counsel determination required. | Regulatory SME determination required. | n/a | Counsel-approved baseline document. | Patent counsel + Vimal | Counsel approval of register | Patent counsel |
| 2 | PTQC-BASELINE-BASELINE-02 | HIGH | OPEN | n/a | IN | Direct file-system evidence (no in-folder claim chart for P01/P02/P02b; provisional, claims deferred) | Medium | BASELINE | `Patent 0X/Counsel Bundle/04_Claim_to_Prior_Art_Map.md` exists ONLY for P01 and P03 | P02 + P02b counsel bundles | No claim chart present for P02 or P02b. P02 spec §11 explicitly disclaims certain mechanisms (prompt-version pinning, GENESIS sentinel, append-only triggers, verifyChain first-break) as reserved for separate filing — these scope disclaimers materially affect later claim drafting and should be locked in a claim-position register, not only in spec body. P02b §7 has "claim seeds for counsel review" but no formal claim-to-spec crosswalk. NOTE: claims are not legally required at provisional under Patents Act §9(1); this finding is HIGH (not CRITICAL) because it is acceptable at provisional but becomes mandatory at complete-spec stage. | n/a | n/a | At complete-spec stage, formalize claims (§7 P02b seeds, P01 claim chart for P01) into proper independent + dependent claim set with §10(5)/§10(6) sufficiency map. | n/a | n/a | n/a | Counsel determination required. | n/a | n/a | Claim chart + §10(6) sufficiency map per patent at complete spec. | Patent counsel | Complete-spec stage | Patent counsel |
| 3 | PTQC-BASELINE-BASELINE-03 | LOW | OPEN | n/a | IN | Direct file inspection of `05_FTO_Opinion/FTO_Raw_Research/INTERNATIONAL_JURISDICTION_ASSESSMENT.txt` (2026-05-27) | Medium | BASELINE | `05_FTO_Opinion/FTO_Raw_Research/INTERNATIONAL_JURISDICTION_ASSESSMENT.txt` | Whole file | Jurisdiction profile EXISTS and is multi-jurisdiction (US / EP / GB / AU / KR / CN). For the present provisional filings (IP India ordinary, India-first), India is the primary jurisdiction; multi-jurisdiction exposure is acknowledged but out of provisional QC scope. Adequate. Recommendation: link this file from the patent-source-of-truth.yaml when created so jurisdiction binding is explicit. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Reference in source-of-truth register. | Patent counsel | n/a | Patent counsel (for confirmation only) |
| 4 | PTQC-BASELINE-BASELINE-04 | LOW | OPEN | n/a | IN | Direct file inspection of `00_Prior_Art_Search/00_README_Prior_Art_Search.md` | Medium | BASELINE | `00_Prior_Art_Search/`, `05_FTO_Opinion/FTO_Raw_Research/` | Folder-level | Prior-art register EXISTS at workspace level (7-candidate dossier + 11 FTO research files); per-patent prior-art tables exist in `Patent 01/Counsel Bundle/03_Prior_Art_Comparison_Matrix.md` and `Patent 03/Counsel Bundle/03_Prior_Art_Comparison_Matrix.md`. NOT present for P02 or P02b. Patentability-attack vectors against P02 (`US11658831B2 Ascent` hash-chain prior art global, `US12423067B1 Ketryx` US-only) and P02b would benefit from explicit per-patent prior-art comparison matrices. | n/a | n/a | n/a | n/a | n/a | n/a | Counsel determination required. | n/a | n/a | Per-patent prior-art comparison matrix for P02 and P02b at complete-spec stage. | Patent counsel | Complete-spec stage | Patent counsel |
| 5 | PTQC-SPEC-P01-SPEC-01 | LOW | OPEN | n/a (no register) | IN | Direct file inspection of `Verixa_Form2_Provisional_Specification.md` §5, §6, §11 | High (file-grounded) | SPEC | `Patent 01 - Platform Validated Model Lockstep/Filing/Verixa_Form2_Provisional_Specification.md` | §5 lines 112–127; §11 lines 513–515 | §5 "Brief Description of the Drawings" lists all 8 figures correctly with matching titles vs Drawings directory; §11 Abstract present and within ≤150 words allowance (one paragraph). Conformance verified. ADVISORY: §5 disclaimer paragraph (line 116) anticipates code-vs-spec drift — present and effective for P01. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None. | n/a | n/a | n/a |
| 6 | PTQC-SPEC-P02-SPEC-02 | LOW | OPEN | n/a (no register) | IN | Direct file inspection of P02 spec §6, §10, §11 (abstract) | High (file-grounded) | SPEC | `Patent 02 - Cryptographic Per-Inference Audit Model Version Governance and Agent Qualification/Filing/VeriXA_P02_Form2_Provisional_Specification.md` | §6 lines 100–110; §11 lines 351–369; Abstract lines 373–375 | §6 "Brief Description of the Drawings" lists all 5 figures with reference-numeral callouts inline (good practice). Abstract present (one paragraph). §11 Scope present. Conformance verified. NOTE: P02 spec body §7+ never inlines `Fig. N` callouts (see TRACE-P02-01 below). | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None at SPEC level. | n/a | n/a | n/a |
| 7 | PTQC-SPEC-P02b-SPEC-03 | LOW | OPEN | n/a (no register) | IN | Direct file inspection of P02b spec §5, §8 (abstract), §10 | High (file-grounded) | SPEC | `Patent 02b - AI Output Segregation Engine/Filing/VeriXA_P02b_Form2_Provisional_Specification.md` | §5 lines 94–106; §8 lines 323–325; §10 lines 335–339 | §5 lists 5 figures correctly; §5 disclaimer paragraph (line 96) is scope-widened to cover "service file names, database table names, database column names, database migration identifiers, function names, configuration constants, mnemonic section identifiers" — verified comprehensive and present. §8 Abstract present (one paragraph). §10 Scope present. Conformance verified. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None at SPEC level. | n/a | n/a | n/a |
| 8 | PTQC-TRACE-P01-TRACE-01 | MEDIUM | OPEN | n/a (no register) | IN | grep evidence — only one `Figs. 1 and 2` callout in §6.1 body; no inline figure references for Figs 3–8 | High | TRACE | `Patent 01 - Platform Validated Model Lockstep/Filing/Verixa_Form2_Provisional_Specification.md` | §6 body (lines 131–415); only line 137 cites "Figs. 1 and 2"; Figs 3, 4, 5, 6, 7, 8 not inline-cited | Indian provisional practice under §10 prefers (but does not strictly mandate) that §6 detailed description inline cite each figure ("Fig. N illustrates X"). P01 §6 cites only Figs 1 and 2; Figs 3–8 are described only in the §5 Brief Description and via reference numerals in §6 paragraphs. Not a §10(6) sufficiency failure in itself, but mildly weakens the §10 disclosure-completeness narrative. | n/a | n/a | Add inline "Fig. N" callouts in §6 detailed description sections that correspond to each figure: §6.2 → Fig 3 (TDAL schema), §6.4 → Fig 4 (Hash-Chain), §6.6 → Fig 5 (AI Gateway), §6.7 → Fig 6 (HITL ceremony), §6.8 → Fig 7 (Agentic Panel), §8.1 / §8.4 → Fig 8 (Worked Example). | None — figures are correct. | n/a | n/a | Counsel determination required. | n/a | n/a | Surgical §6 inline figure callouts at REV-9. | Patent drafter (lead-patent-drafter) | n/a | Patent counsel |
| 9 | PTQC-TRACE-P02-TRACE-02 | MEDIUM | OPEN | n/a (no register) | IN | grep evidence — no `Fig` or `Figure` references in §7+ body | High | TRACE | `Patent 02 - Cryptographic Per-Inference Audit Model Version Governance and Agent Qualification/Filing/VeriXA_P02_Form2_Provisional_Specification.md` | §7 (lines 114–270), §8 (272–290), §9 (294–337) — no inline figure citations | P02 §7 detailed description and §8 method describe the system layer by layer (§7.1 architecture, §7.2 audit chain, §7.3 governance, §7.4 qualification, §7.5 gateway pipeline) but never inline-cite "Fig. N". Same severity rationale as TRACE-P01. | n/a | n/a | Add inline "Fig. N" callouts in §7.1 → Fig 1, §7.2 → Fig 2, §7.3 → Fig 3, §7.4 → Fig 4, §7.5 → Fig 5. | None. | n/a | n/a | Counsel determination required. | n/a | n/a | Surgical §7 inline figure callouts at v1.3. | Patent drafter | n/a | Patent counsel |
| 10 | PTQC-TRACE-P02b-TRACE-03 | MEDIUM | OPEN | n/a (no register) | IN | grep evidence — no `Fig` or `Figure` references in §6+ body | High | TRACE | `Patent 02b - AI Output Segregation Engine/Filing/VeriXA_P02b_Form2_Provisional_Specification.md` | §6 (110–301), §7 (303–319) — no inline figure citations | Same pattern as P01/P02 above. P02b §6 has 10 subsections (§6.1–§6.10) corresponding closely to the 5 figures but no inline "Fig. N" callouts. | n/a | n/a | Add inline "Fig. N" callouts in §6.1 → Fig 1, §6.2 → Fig 2, §6.3 → Fig 3, §6.5 → Fig 4, §6.8 → Fig 5. | None. | n/a | n/a | Counsel determination required. | n/a | n/a | Surgical §6 inline figure callouts at v1.2. | Patent drafter | n/a | Patent counsel |
| 11 | PTQC-TRACE-P02-TRACE-04 | MEDIUM | OPEN | n/a (no register) | IN | grep evidence: numerals (200), (201), (202), (203), (204) appear in Fig 2 SVG legend text but never appear in spec §6 BDD or §7 body | High (cross-file) | TRACE | `Patent 02/Filing/Drawings/Fig2_Per_Inference_LLM_Audit_Chain.svg` vs spec §6.104 + §7.2 | Fig 2 SVG `<text>` elements declare "Inference Call Input (200)", "System Prompt Text (201) | System Prompt Version (202)", "User Prompt Text (203) | Model ID + Provider (204)"; these numerals are NOT declared in spec §6 line 104 or referenced anywhere in spec §7.2 | Five reference numerals (200, 201, 202, 203, 204) used in the drawing are not introduced in the specification. Under Patent Rules 2003 Rule 13(7) and standard Indian patent drafting practice, every reference numeral in a drawing must be introduced in the specification at its first use. CURRENT spec §6 line 104 starts numbering at (210) for hash computation. | n/a | n/a | Add to §6 BDD line 104: "showing inference call input (200) including system prompt text (201), system prompt version (202), user prompt text (203), and model ID + provider (204); hash computation (210) for system prompt (211), …". Mirror introduction in §7.2.1 or §7.2.5. | None — Fig 2 SVG content is accurate, only the cross-reference needs alignment. | n/a | n/a | Counsel determination required (rule-13(7) sufficiency framing). | n/a | n/a | Surgical §6 + §7.2 patch at v1.3. | Patent drafter | n/a | Patent counsel |
| 12 | PTQC-TRACE-P02-TRACE-05 | MEDIUM | OPEN | n/a (no register) | IN | grep evidence: numerals (300), (331), (441) appear in Fig 3 and Fig 4 SVGs but not in spec §6 or body | High (cross-file) | TRACE | P02 Drawings: Fig 3 SVG declares "model_registry Table (300)" and "REFUSED (331)"; Fig 4 SVG declares "Qualification Refused (441)" | Fig 3 + Fig 4 SVGs | Spec §6.106 (Fig 3 BDD) introduces (310), (311), (312), (313), (314), (320), (321), (322), (323), (330), (340) — but NOT (300) (the model_registry table itself) and NOT (331) (REFUSED state). Spec §6.108 (Fig 4 BDD) introduces (410), (411), (420), (421), (422), (423), (430), (431), (432), (440), (450) — but NOT (441) (Qualification Refused outcome). Same Rule 13(7) cross-reference gap as TRACE-04. | n/a | n/a | Add to §6.106: "the model_registry table (300) with state machine (310) … and a refused state (331) reached when qualification is not approved". Add to §6.108: "… qualification gate (440) routing to either inclusion in regulated paths (450) or qualification refused (441)". | None — SVG content accurate. | n/a | n/a | Counsel determination required. | n/a | n/a | §6 patch at v1.3. | Patent drafter | n/a | Patent counsel |
| 13 | PTQC-TRACE-P02b-TRACE-06 | MEDIUM | OPEN | §5 disclaimer (mitigating) | IN | grep evidence: mnemonic codes E2, E2-A, E2-B, E2-C, E2-D, E2-E used in Fig 1 SVG but not in spec body | High (cross-file) | TRACE | `Patent 02b/Filing/VeriXA_P02b_Fig1_System_Architecture.svg` vs spec §6 | Fig 1 SVG declares "AI OUTPUT SEGREGATION ENGINE — E2", "E2-A: AI GATEWAY SERVICE", "E2-B: PROHIBITED-FIELD BOUNDARY", "E2-C: HUMAN-DECISION RECORDING", "E2-D" (proposal staging), "E2-E" (evidence pack); spec §6 never uses these mnemonic codes | Mnemonic labels in Fig 1 are not referenced as such in spec body. MITIGATED by §5 disclaimer (line 96) which explicitly covers "mnemonic section identifiers". Net: legally defensible per the disclaimer but stylistically inconsistent; would be cleaner if §6 either uses E2-A/B/C/D/E labels OR Fig 1 SVG removes them. | n/a | n/a | Either (a) introduce E2-A/E2-B/E2-C/E2-D/E2-E labels in §6 subsection headings to match Fig 1, OR (b) replace mnemonic codes in Fig 1 with sub-system names matching §6 subsection titles. Preferred: (a) — cleaner cross-walk. | If (b): edit Fig 1 SVG `<text>` elements at lines that declare E2-A/B/C/D/E to use sub-system names. | n/a | n/a | Counsel determination required. | n/a | n/a | Editor pass at v1.2. | Patent drafter | n/a | Patent counsel |
| 14 | PTQC-DIAG-P01-DIAG-01 | MEDIUM | PARTIAL — visual review required for 5 of 8 figures | n/a (no register) | IN | Parent agent visually verified Fig 3 P01 (post-fix render); manifest documents Fig 1, 2, 3, 5 fixes applied 2026-06-06; vector-pipeline rebuild documented | Mixed | DIAG | `Patent 01/Filing/Drawings/Fig1..8_*.svg` + `P01_Drawings.pdf` (`ca090fd179…`) | All 8 figs | Per manifest §1.3, surgical fix applied to Fig 3 L149 FK arrow tip (now lands on box 330 bottom-left); per manifest §1.2, vertical text-overflow fixes applied to Fig 1 (199 Storage box text font 11→10) and Fig 3 (360 hitl_decisions decision-line font 10→9). Vector pipeline (cairosvg svg2pdf → reportlab footer overlay → pypdf concat) preserves geometry at infinite zoom. Visual verification status: Fig 3 visually verified by parent (post-fix render) — PASS for Fig 3. Figs 1, 2, 4, 5, 6, 7, 8: `Unknown — human visual review required.` | n/a | n/a | n/a | None for Fig 3 (visually verified). For Figs 1, 2, 4, 5, 6, 7, 8: render PNG and visually inspect for orphan arrows, overlap, legibility at 100% A4. | Rule 15(2) B&W compliance: P01 SVGs already B&W per manifest §1.0e — adequate. Rule 15(7) sheet N/8 + Rule 15(8) applicant footer: applied via reportlab overlay at PDF build time per manifest §1.1. Visual confirmation on rendered PDF: `Unknown — human visual review required.` for Figs 1, 2, 4, 5, 6, 7, 8. | Footer overlay applied per manifest §1.1 — Vimal Veereshwarayya (lower-left) + N/8 (lower-right). Manifest claim adequate; final PDF visual confirmation outstanding for 7 of 8 figs. | Counsel determination required. | n/a | n/a | PNG render + visual inspection of Figs 1, 2, 4, 5, 6, 7, 8. | Vimal + Patent drafter | Visual review of remaining 7 figures | Patent counsel |
| 15 | PTQC-DIAG-P02-DIAG-02 | MEDIUM | PARTIAL — visual review required for 3 of 5 figures | n/a (no register) | IN | Parent agent visually verified Fig 2 P02 and Fig 4 P02 (post-fix renders); manifest §1.3 documents Fig 4 orphan-arrow fix and Fig 2 chain-link numeral fix | Mixed | DIAG | `Patent 02/Filing/Drawings/Fig1..5_*.svg` + `P02_Drawings.pdf` (`6bdc0f295d…`) | All 5 figs | Per manifest §1.3, Fig 4 "updates" arrow at L42 fixed (was going `(565,265)→(565,318)`, landing 18px past edge of "Qualification Status (430)" rect → now `x2=520 y2=320`, tip lands on top edge of 430 rect). Per manifest §1.3, Fig 2 chain-link formula updated to inline (221), (222), (223) for prev/rawHash/ts operands so legend numerals tie to diagram. Per manifest §1.2, Fig 1 + Fig 3 + Fig 5 vertical-overflow rect-extension fixes applied. Visual verification status: Fig 2 + Fig 4 visually verified by parent — PASS. Figs 1, 3, 5: `Unknown — human visual review required.` | n/a | n/a | n/a | None for Figs 2 and 4. For Figs 1, 3, 5: render PNG and visually inspect for box-overflow, arrow connection, legend-to-diagram tie-in. | Rule 15(2) B&W compliance: P02 SVGs already B&W per manifest §1.0e — adequate. Footer per manifest §1.1 applied via overlay. Visual confirmation outstanding for Figs 1, 3, 5. | Footer overlay applied per manifest §1.1. | Counsel determination required. | n/a | n/a | PNG render + visual inspection of Figs 1, 3, 5. | Vimal + Patent drafter | Visual review of Figs 1, 3, 5 | Patent counsel |
| 16 | PTQC-DIAG-P02b-DIAG-03 | MEDIUM | PARTIAL — visual review required for 4 of 5 figures | n/a (no register) | IN | Parent agent visually verified Fig 2 P02b (post-fix render); manifest §1.0e documents B&W compliance fix (23 color violations → 0) | Mixed | DIAG | `Patent 02b/Filing/VeriXA_P02b_Fig1..5_*.svg` + `P02b_Drawings.pdf` (`ff6a16d68d…`) | All 5 figs | Per manifest §1.0e, all 5 P02b SVGs had non-B&W color elements (backgrounds + 23 colored arrowhead markers across the 5 figs); all converted to B&W (background `#f8f9fa`→`#ffffff`; colored markers `#444`/`#c0392b`/`#1e8449`/`#d68910`/etc.→`#000000`). Per manifest §1.0b Fix 1, Fig 1 service-name corrected from `capa-ai.service.ts` (copy-paste error) → `investigation-autopilot.service.ts` for the Deviation AI box. Per manifest §1.0c, Fig 3 + Fig 4 vertical-overflow rect-extensions applied. Visual verification status: Fig 2 P02b visually verified by parent — PASS. Figs 1, 3, 4, 5: `Unknown — human visual review required.` | n/a | n/a | n/a | None for Fig 2. For Figs 1, 3, 4, 5: render PNG and visually inspect for B&W compliance, text-in-rect containment, arrow connection. | Rule 15(2) B&W compliance critical: 23 color violations were present and reportedly fixed — visual confirmation required on rendered PDF. | Footer overlay applied per manifest §1.0a Fix 4. | Counsel determination required. | n/a | n/a | PNG render + visual inspection of Figs 1, 3, 4, 5. | Vimal + Patent drafter | Visual review of Figs 1, 3, 4, 5 | Patent counsel |
| 17 | PTQC-CONF-P02b-CONF-01 | HIGH | OPEN — disclaimer mitigates patent risk but not confidentiality risk | §5 disclaimer (partial mitigation) | IN | grep evidence: 8 distinct `.service.ts` filenames exposed in P02b SVG + spec text (`investigation-autopilot.service.ts`, `capa-ai.service.ts`, `oos-ai.service.ts`, `mira.service.ts`, `ai-gateway.service.ts`, `rca-ai.service.ts`, `risk-ai.service.ts`, `document-review-ai.service.ts`, `mira-config.service.ts`, `evidence-pack.service.ts`, `evidence-pack-canonical.ts`) + migration identifiers (`016_create_ai_tables.sql`, `288_urs_ai_governance_evidence_packs.sql`) | High (file-grounded) | CONF | P02b Form 2 spec lines 136, 140, 170, 191, 227, 263, 299; Fig 1 SVG lines 19+; Fig 3 SVG; Fig 4 SVG | Internal source-code file names and migration numbers are exposed in the patent filing — published once filing is open to public inspection (12 months after India provisional + 6 months early-publication window, or earlier on request). PARTIALLY MITIGATED by §5 disclaimer which states "service file names…need not correspond one-to-one with any particular source-code implementation". The disclaimer protects against §10(6) sufficiency narrowing but does NOT undo public disclosure of the actual file paths. This is a CONFIDENTIALITY decision, not a patentability decision. | n/a | n/a | Consider whether `.service.ts` paths should be replaced by generic role names ("the deviation-investigation AI service" instead of `investigation-autopilot.service.ts`) before public disclosure. If retained, log decision in source-of-truth register so counsel review is on-record. | If retained: no change. If replaced: edit Fig 1 line 19, Fig 3, Fig 4 SVG `<text>` elements + Form 2 §6 inline citations. | If SVG edits: re-run box-by-box audit + Rule 15(2) B&W check. | n/a | Counsel determination required (whether disclosure narrows trade-secret protection of internal code architecture). | Regulatory SME determination required (whether disclosure of internal validation evidence references (e.g., migration identifiers, `qs21-guard.test.ts` references) affects GxP audit-trail integrity of the controlled codebase). | n/a | Counsel + Vimal decision on retention vs replacement before filing. | Counsel + Vimal | Counsel decision | Patent counsel |
| 18 | PTQC-CONF-P02-CONF-02 | LOW | OPEN | n/a | IN | grep evidence: no `.service.ts` or migration identifiers in P02 SVGs; spec body uses generic component names | High | CONF | P02 spec + Fig 1..5 SVGs | Spec body | P02 spec body uses generic regulated-system terminology ("AI Gateway Service (100)", "model_registry Table (300)", "qualification gate (440)") with no internal source-code file paths. Clean. NOTE: spec §10 line 345 ("An embodiment of the invention has been reduced to practice as a multi-tenant GxP AI governance platform operating in pharmaceutical and biotechnology quality management environments") is neutral and no longer brand-attributes per manifest §1.0 — verified clean. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None. | n/a | n/a | n/a |
| 19 | PTQC-CONF-P01-CONF-03 | LOW | OPEN | n/a | IN | grep evidence: no `.service.ts` or migration identifiers in P01 SVGs or spec | High | CONF | P01 spec + Fig 1..8 SVGs | Spec body | P01 spec body uses generic component names; §5 disclaimer (line 116) in place. Clean. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None. | n/a | n/a | n/a |
| 20 | PTQC-REG-P02-REG-01 | HIGH | OPEN | n/a | IN | Direct evidence: P02 spec §10 line 341 ("These requirements mandate…The per-inference audit architecture described herein satisfies these requirements for AI inference calls as a class of record mutation.") | High (file-grounded) | REG | `Patent 02 - Cryptographic Per-Inference Audit Model Version Governance and Agent Qualification/Filing/VeriXA_P02_Form2_Provisional_Specification.md` | §10 line 341, line 343 | §10 Industrial Applicability includes an AFFIRMATIVE compliance claim: "The per-inference audit architecture described herein satisfies these requirements for AI inference calls as a class of record mutation." This is a regulatory-conformance assertion against 21 CFR Part 11, EU GMP Annex 11, EU Annex 22 (Draft 2025), MHRA AI/ML Guidance (2024), FDA AI/ML SaMD Action Plan, GAMP 5 Category 5, and ALCOA+. The QC harness cannot validate regulatory adequacy. | n/a | n/a | Consider hedging "satisfies" to "is designed to address" or "supports the …requirements" to avoid affirmative compliance representation that has not been independently certified. Alternatively, retain language IF a regulatory SME has on-record validated it. | n/a | n/a | n/a | Counsel determination required (representation risk under §10(6)). | Regulatory SME determination required. | EU Annex 22 Draft 2025 is not yet enforceable; "satisfies" against a draft is a fact-dependent claim. EU AI Act enforcement phase-in: high-risk classifications August 2027. FDA CSA Final Guidance is enforceable. | Regulatory SME sign-off (e.g., `verixa-gxp-quality:full-gxp-ai-eqms-urs-expert`, `verixa-ai-governance:ai-validation-governance-expert`) on the compliance assertion. | Patent counsel + Regulatory SME | SME sign-off OR language hedge | Patent counsel + GxP SME |
| 21 | PTQC-REG-P02b-REG-02 | HIGH | OPEN | n/a | IN | Direct evidence: P02b spec §6.10 lines 276–299 ("The prohibition on direct AI writes to GxP-critical record fields is grounded in the following regulatory requirements: 21 CFR Part 11 §11.10(d)…Annex 11 §12…Annex 22 §7 (Draft 2025)…EU AI Act Article 14…MHRA ALCOA+ — Attributable") + §10 Scope lines 337 ("to enforce the ALCOA+ Attributable principle and EU Annex 22 §7 human oversight requirement") | High (file-grounded) | REG | `Patent 02b - AI Output Segregation Engine/Filing/VeriXA_P02b_Form2_Provisional_Specification.md` | §6.10 lines 276–299; §10 line 337 | P02b §6.10 catalogues regulatory citations and asserts the engine is "grounded in" them and "enforces" ALCOA+ Attributable + Annex 22 §7. Affirmative regulatory-effect claim. The QC harness cannot validate. EU Annex 22 §7 (Draft 2025) is pre-enforcement; EU AI Act Article 14 enforcement August 2027. | n/a | n/a | Consider hedging "enforces" → "is designed to support". Same recommendation as REG-01. | n/a | n/a | n/a | Counsel determination required. | Regulatory SME determination required. | EU Annex 22 §7 (Draft) and EU AI Act Art. 14 (effective Aug 2027) are not currently in force. ALCOA+ MHRA 2018 Data Integrity guidance is in force. 21 CFR Part 11 §11.10(d) is in force. Annex 11 §12 is in force. | Regulatory SME sign-off on the regulatory-effect claims in §6.10 and §10. | Patent counsel + Regulatory SME | SME sign-off OR language hedge | Patent counsel + GxP SME |

---

## 4. Bundled-Deliverable Consistency Check

| Bundle | Manifest SHA-256 (claimed) | Actual SHA-256 | Match | Manifest pages (claimed) | Actual pages | Match |
|---|---|---|---|---|---|---|
| P01 Form1 OFFICIAL | `cb95fd1eac7bb39f2ee106b092409946098d09f5501eba09657920cbfbbd3f46` | `cb95fd1eac…3f46` | YES | 9 | 9 | YES |
| P01 Form2 REV-8 OFFICIAL | `874b5d9564ddd0a82374505d4499259f38d8356328d86fd0884877f450b81c69` | `874b5d9564…1c69` | YES | 54 | 54 | YES |
| P01 Form3 OFFICIAL | `da4ca38ad32eddc9d2d66032b15a3f3718cc716a9e295ee149fa5afbdaace442` | `da4ca38ad3…ce442` | YES | 3 | 3 | YES |
| P01 Drawings | `ca090fd17990bab5a589bd09c204b5ab9d5ee4d8d4314ec8b77b3ff49634a389` | `ca090fd179…4a389` | YES | 8 | 8 | YES |
| P02 Form1 OFFICIAL | `6f2f7fa1053658552d0d51e2f4784a2055f6e3991a80b5f2b666af4d22faa055` | `6f2f7fa105…aa055` | YES | 8 | 8 | YES |
| P02 Form2 v1.2 OFFICIAL (CURRENT) | `b37d56fcc4bb4db260c1b465d7c88bc2f2f081d673c2bdf5933b39e2e2fd28e7` | `b37d56fcc4…28e7` | YES | 31 | 31 | YES |
| P02 Form3 OFFICIAL | `09b833771621632c95de12d3f5a3e047e0285573e95c252d571ee4e17567e71b` | `09b8337716…7e71b` | YES | 3 | 3 | YES |
| P02 Drawings | `6bdc0f295d4f23995c4e741a84ac38bcc8b9f67c47be57cbbdda64d7b7403904` | `6bdc0f295d…03904` | YES | 5 | 5 | YES |
| P02b Form1 OFFICIAL | `cb0e73adbc78c527d2a81e59849a3ce93d999dd3a45ae69a8ce1c569e868e639` | `cb0e73adbc…e639` | YES | 8 | 8 | YES |
| P02b Form2 v1.1 OFFICIAL (CURRENT) | `6294ab59520b568d3399b616259b7445be64e3536318ef8217a46bd1dcbe43fe` | `6294ab5952…43fe` | YES | 28 | 28 | YES |
| P02b Form3 OFFICIAL | `a2bba37275bfe8453e769657c2dd39d3aed976ae5cd15c23d4ce6556cb29b219` | `a2bba37275…6b219` | YES | 3 | 3 | YES |
| P02b Drawings | `ff6a16d68d77b7a2ad4ddf998e078115728c948190c57f1f92870eb8192e859c` | `ff6a16d68d…e859c` | YES | 5 | 5 | YES |

**Result:** All 12 filing-bundle PDFs match their manifest SHA-256 and page counts. No drift between manifests and actual bundles. Superseded files (P02 v1.1, P02b _OFFICIAL non-v1.1, P01 Form1 non-OFFICIAL) retained in folders per manifest §1.1 audit-trail policy — must NOT be uploaded; this is documented but Vimal must confirm at upload time.

---

## 5. What Is NOT in Scope of This QC

The Patent-Truth QC harness does NOT attempt and cannot conclude on:

- **Code-level verification.** No grep against the Verixa repository (`/Users/vimalv/03_Repositories/Github/Verixa`) was performed in this audit. Spec claims of the form "Verified against: `ai-gateway.service.ts:processRequest()` (steps 1–9)" are RECORDED IN THE SPEC but not independently re-verified here. Code-level verification belongs to a separate engineering-audit workflow (`anthropic-skills:super-senior-fullstack-engineer` + `verixa-platform-engineering:product-engineering-architect`).
- **Patentability legal opinion.** No §3(k) (India) / §101 (US) / Art. 52(2)(c) (EPO) / GAMP novelty-non-obviousness conclusions are made. `Counsel determination required.` Owner: `anthropic-skills:verixa-section-3k-patent-expert`, `anthropic-skills:verixa-patent-attorney`.
- **Regulatory adequacy.** No 21 CFR Part 11 / Annex 11 / Annex 22 / EU AI Act / ALCOA+ adequacy determination is made. `Regulatory SME determination required.` Owner: `anthropic-skills:verixa-ai-validation-governance-expert`, `verixa-gxp-quality:full-gxp-ai-eqms-urs-expert`.
- **FTO clearance.** No comparison with prior art beyond noting that an FTO research dossier exists at `05_FTO_Opinion/FTO_Raw_Research/`. Owner: `anthropic-skills:verixa-patent-fto-expert`.
- **Visual confirmation of figures not rendered in this session.** Parent agent visually verified Fig 2 (P02), Fig 3 (P01), Fig 4 (P02), Fig 2 (P02b). The other 14 figures (P01 Figs 1, 2, 4, 5, 6, 7, 8; P02 Figs 1, 3, 5; P02b Figs 1, 3, 4, 5) are marked `Unknown — human visual review required.`
- **PDF-level Rule 15(7)/15(8) footer confirmation.** Footers are added via reportlab overlay at PDF build time per manifests; confirmation that the overlay actually applied correctly on each page requires opening each PDF page. Marked `Unknown — human visual review required.` until rendered.
- **Diagram-to-URS-to-code three-layer reconciliation.** Without a counsel-approved source-of-truth register (BASELINE-01), a three-layer reconciliation is structurally impossible. Once the register exists, this becomes the primary task for the next QC pass.

---

## 6. Mandatory Next Actions (in order)

1. **Counsel-approved source-of-truth register.** Create `ip/spec/patent-source-of-truth.yaml` containing, for each of P01, P02, P02b: approved invention concept text, approved claim seeds (or "deferred to complete spec"), approved figure list with titles, approved reference-numeral registry (with the additions noted in TRACE-04 and TRACE-05), approved §10/§11 scope, sign-off block (counsel name, date, version). Until this exists, ALL findings remain advisory.
2. **Counsel resolution on CONF-P02b-CONF-01.** Decide whether `.service.ts` paths in P02b filing should be replaced by generic role names. If retained, log the decision and rationale in the source-of-truth register.
3. **Regulatory SME sign-off on REG-P02-REG-01 and REG-P02b-REG-02.** Either obtain on-record SME validation of the compliance assertions, or hedge language ("satisfies" → "is designed to address"; "enforces" → "is designed to support") at the next spec revision.
4. **Visual review of 14 remaining figures.** Render PNG of P01 Figs 1, 2, 4, 5, 6, 7, 8 + P02 Figs 1, 3, 5 + P02b Figs 1, 3, 4, 5 and visually verify post-fix state matches manifest claims.
5. **§6/§7 inline figure callouts** for P01, P02, P02b (TRACE-01/02/03). Surgical patch in next REV.
6. **§6 reference-numeral introductions** for P02 numerals (200), (201), (202), (203), (204), (300), (331), (441) (TRACE-04, TRACE-05). Surgical patch in next REV.
7. **Claim charts at complete-spec stage** for P02 and P02b (BASELINE-02).
8. **Per-patent prior-art comparison matrices** for P02 and P02b at complete-spec stage (BASELINE-04).

---

## 7. Source Ledger

| Source type | Source name/path | Date/version | Claim supported | Limitations |
|---|---|---|---|---|
| Skill doctrine | `~/.claude/skills/patent-truth-qc/SKILL.md` (skill mounted from `anthropic-skills:patent-truth-qc`) | v1.5.1 (Cowork port) | QC schema, 24-column finding table, fail-closed status semantics, fail-safe phrasing | Cowork-port advisory mode; deterministic-guard scripts not run in this audit |
| Spec file | `Patent 01 - Platform Validated Model Lockstep/Filing/Verixa_Form2_Provisional_Specification.md` | REV-8 (2026-06-06; 532 lines) | P01 §5, §6, §11, abstract scope; Fig 1–8 BDD; inline-citation gap (TRACE-01) | Provisional; no claims |
| Spec file | `Patent 02 - Cryptographic Per-Inference Audit Model Version Governance and Agent Qualification/Filing/VeriXA_P02_Form2_Provisional_Specification.md` | v1.2 OFFICIAL (2026-06-06; 392 lines) | P02 §6 BDD, §7 detailed description, §10 industrial applicability, §11 scope, abstract; reference-numeral gap (TRACE-04, TRACE-05); compliance-assertion language (REG-01) | Provisional; no claims |
| Spec file | `Patent 02b - AI Output Segregation Engine/Filing/VeriXA_P02b_Form2_Provisional_Specification.md` | v1.1 (2026-06-05; 347 lines) | P02b §5 disclaimer scope, §6 detailed description, §6.10 regulatory grounding, §7 claim seeds, §8 abstract, §10 scope; CONF disclosure (CONF-01); REG assertion (REG-02) | Provisional; claim seeds only (not formal claims) |
| Drawings — P01 | `Patent 01 - Platform Validated Model Lockstep/Filing/Drawings/Fig1..8_*.svg` + `Reference_Numerals.md` | 2026-06-06 (vector-rebuild) | Fig list, reference-numeral registry, post-fix state | Vector SVG inspection by grep; visual confirmation for Figs 1, 2, 4, 5, 6, 7, 8 outstanding |
| Drawings — P02 | `Patent 02 - …/Filing/Drawings/Fig1..5_*.svg` | 2026-06-06 (vector-rebuild + Fig 4 orphan-arrow fix + Fig 2 numeral fix + 3 overflow rect-extension fixes) | Fig list, numerals (200, 201, 202, 203, 204, 300, 331, 441 found in SVG only) | Visual confirmation for Figs 1, 3, 5 outstanding |
| Drawings — P02b | `Patent 02b - …/Filing/VeriXA_P02b_Fig1..5_*.svg` | 2026-06-06 (B&W conversion 23 violations → 0 + Fig 1 service-name fix + 3 overflow rect-extensions) | Fig list, mnemonic E2-A/B/C/D/E codes in Fig 1 SVG only | Visual confirmation for Figs 1, 3, 4, 5 outstanding |
| Build manifests | `Patent 0X/Filing/Filing_Bundle_P0X/00_Build_Manifest.md` | 2026-06-06 (latest) | SHA-256 + page-count claims for filing PDFs | Manifest self-attestation; cross-checked against actual sha256sum + pdfinfo — all match |
| Jurisdiction profile | `05_FTO_Opinion/FTO_Raw_Research/INTERNATIONAL_JURISDICTION_ASSESSMENT.txt` | 2026-05-27 (v5) | Multi-jurisdiction coverage US/EP/GB/AU/KR/CN; India primary for provisional filing | FTO scope, not source-of-truth governance |
| Prior-art dossier | `00_Prior_Art_Search/` + `05_FTO_Opinion/FTO_Raw_Research/` (11 competitor/USPTO files) | 2026-05-24 dossier + 2026-05-27 multi-jurisdiction | Prior-art landscape | Per-patent comparison matrices exist for P01 + P03 only |
| Source-of-truth register | `ip/spec/patent-source-of-truth.yaml` | **ABSENT** | Would lock invention concept, claim seeds, figure list, reference-numeral registry, drawing-to-spec crosswalk per patent | **Primary blocker. Status remains BLOCKED until this register is created and counsel-approved.** |
| Verixa CLAUDE.md | `/Users/vimalv/03_Repositories/Github/Verixa/CLAUDE.md` | Current (regulatory boundaries section) | Regulatory classification rationale (GAMP 5 Cat 5, 21 CFR Part 11, Annex 11, Annex 22, AI Act, CSA, GMLP, ALCOA+, etc.) | Engineering-side; informs reg-risk framing but not regulatory adequacy conclusion |

---

## 8. Permitted Fail-Safe Phrases Used in This Report (per QC doctrine)

- `Counsel determination required.` — used for patentability and §10(6) sufficiency framing.
- `Regulatory SME determination required.` — used for ALCOA+, 21 CFR Part 11, Annex 11, Annex 22, EU AI Act, FDA CSA, GMLP adequacy.
- `Conclusion fact-dependent — jurisdiction required.` — applicable to all conclusions where multi-jurisdiction exposure matters; India is the primary jurisdiction for the provisional filings.
- `Unknown — human visual review required.` — used for 14 of 18 figures (PNG render + visual confirmation outstanding).
- `Unknown — evidence required.` — held in reserve; not used in present findings.
- `Unverified — evidence required.` — held in reserve; not used in present findings.

---

**End of Patent-Truth QC Report.** Status: **BLOCKED** pending counsel-approved source-of-truth register (BASELINE-01). All other findings remain advisory until baseline is locked. No claim in this report is binding pre-counsel.