Source: 09-CLAIM-PROOF-MATRIX.md

What this source is

An 8-row claim-to-proof matrix — the structural document that maps each pitch claim to a specific verification artifact on the demo site. At 1,168 characters, it is compact and load-bearing: reviewers in any of the three review paths hit this document as a structural anchor (“here’s the claim, here’s the exact URL that proves it, here’s what to look for, here’s whether it’s shipped”).

Every row in the matrix is marked “Shipped” — there are no “Planned” or “In Progress” entries. This is a strong confidence signal about the product’s current state, if the matrix is accurate.

Key claims

The matrix itself is the source. Each row is an atomic claim:

1. “AI mapping is production-usable” — proof at /squire-v2-media-demo/watch/videos/player.html?video=ai-field-mapping, verification is “validate confidence + accept flow in narrated video,” status Shipped. Maps to the AI Field Mapping narration in narration-scripts and the 95% mapping accuracy claim on production-proof. → claim-proof-matrix
2. “Context Sidecar delivers zero-click intelligence” — proof at /squire-v2-media-demo/watch/videos/player.html?video=context-sidecar, verification is “confirm context switching across record types in narrated flow,” status Shipped. Maps to the Context Sidecar narration in narration-scripts and the full NetSuite AP workflow detail on context-sidecar. → claim-proof-matrix
3. “Governance evidence is live” — proof at /compliance-dashboard.html, verification is “expand SOC2 sections and export evidence,” status Shipped. → claim-proof-matrix and cto (confirms the CTO brief’s “compliance evidence export and SOC 2 mapping” ask is answered by a specific dashboard URL).
4. “Oracle differentiation is explicit” — proof at /squire-v2-media-demo/oracle-comparison.html, verification is “review 8-row matrix,” status Shipped. Note: the Oracle comparison is ALSO an 8-row matrix, like this document itself. → claim-proof-matrix and demo-site (the oracle-comparison URL is now formally cited from a corpus source).
5. “Watch evidence is complete” — proof at /squire-v2-media-demo/watch/videos/index.html, verification is “confirm 19-card playlist structure,” status Shipped. The “19-card playlist” number is NEW — first concrete count of videos in the Watch playlist. → demo-site and three-review-paths
6. “Pilot economics are modeled” — proof at /Squire-Executive-Package-v2/04-ROI-CALCULATOR-STANDALONE.html, verification is “check scenarios and assumptions,” status Shipped. Confirms CFO brief’s “scenario inputs are adjustable and transparent” claim — the ROI calculator really is an interactive tool with scenarios and assumptions, not just a fixed projection. → claim-proof-matrix and cfo
7. “Platform quality is enterprise-grade” — proof at /Squire-Executive-Package-v2/05-TECHNICAL-PROOF-STANDALONE.html, verification is “review tests and controls,” status Shipped. Note: this URL numbers it 05-TECHNICAL-PROOF while the notebook has a source numbered 04-TECHNICAL-PROOF.md (per the notebook source list). Small numbering discrepancy worth flagging — possibly a renumbering between the markdown source and the standalone HTML. → production-proof and claim-proof-matrix
8. “Pilot execution is gated” — proof at /Squire-Executive-Package-v2/13-PILOT-30-60-90-STANDALONE.html, verification is “validate day-60/day-90 gates,” status Shipped. Points at the same 13-PILOT-30-60-90 content I just ingested in 13-pilot-30-60-90. The “day-60/day-90 gates” verification language slightly predates the terminology refinement in the 13-pilot source (which clarifies that Day 60 is a phase transition, not a formal gate). Not a contradiction — just older phrasing. → claim-proof-matrix and pilot-30-60-90

Pages updated by this ingest

Created (1 new page):

• claim-proof-matrix — a new structural concept page that captures the matrix itself and its role in Paths A/B/C. All three review paths reference the Claim-Proof Matrix as a step (Path A step 4, Path B step 4, Path C — implicit via claim-matrix traversal).

Updated (2 existing pages):

• demo-site — added /compliance-dashboard.html, confirmed /oracle-comparison.html and /04-ROI-CALCULATOR-STANDALONE.html from this source; noted the 19-card playlist count
• three-review-paths — the “Claim-Proof Matrix” step in Paths A and B now has a wiki-link to the new concept page

Notable quotes

The source is a table; the most notable “quote” is the structure of the claims themselves, especially the “Shipped” status on all 8 rows. The Oracle comparison being a “8-row matrix” is a nice structural echo.

Cross-references / contradictions found

• “19-card playlist” count is NEW: the Watch playlist has 19 videos. Given the 16 modules + 2 context-sidecar variants + 1 executive reel = 19. (Previously, I estimated 24 when I added 7 scene videos to the count. But scene videos are in a separate “storyboard” playlist, not the main 19-card playlist.)
• “05-TECHNICAL-PROOF” URL vs “04-TECHNICAL-PROOF.md” notebook source: small numbering discrepancy. The notebook source is 04-TECHNICAL-PROOF.md (source id cd1ca427-...) but this matrix references 05-TECHNICAL-PROOF-STANDALONE.html as the live URL. Possible explanations: (a) renumbering between markdown draft and final numbered HTML, (b) two different documents, (c) off-by-one in one of the sources. Not blocking, but worth noting for future verification.
• Oracle comparison page is explicitly “8-row matrix”: the Oracle comparison at /squire-v2-media-demo/oracle-comparison.html has an 8-row comparison matrix. Echoes the structure of this claim-proof matrix. Consistent.
• Gate terminology: this matrix uses “day-60/day-90 gates” as the verification language for the pilot execution claim. The newer 13-pilot-30-60-90 refines this — the only HARD gate is at end of phase 3 (day 90); day 60 is a phase transition. Not a contradiction; this matrix uses the older phrasing while still pointing at the same underlying artifact.
• “Shipped” status on all 8 claims: coherent with ai-governance-layer-video’s present-tense framing (“is production ready today”) and read-elevator-pitch’s “production-ready” framing. The only mild exception is NL Action Gate, which the hook video calls “future innovation” — but NL Action Gate is not in this 8-row matrix, so there’s no direct conflict here.

Notes

• This matrix is 8 rows, but it is NOT the same thing as the Oracle comparison (which is ALSO an 8-row matrix at a different URL). Don’t conflate them. The claim-proof matrix is broad (8 pitch claims → 8 proof artifacts); the Oracle comparison is deep (8 capability comparisons vs Oracle).
• The matrix is a short document that punches above its weight — it is referenced in all three review paths as a structural anchor and it maps the entire pitch to verifiable URLs. If a reviewer skims nothing else, they can walk this matrix and verify the whole pitch in ~10 minutes.
• The “Verification” column is written as imperative actions (“validate”, “confirm”, “expand”, “check”, “review”) — it tells the reviewer what to DO, not just what the artifact contains. This is a good design choice for async review: the reviewer doesn’t have to infer what they’re looking for.
• Cross-reference: this source and 22-module-library were ingested in the same turn because both are structural reference documents. They work together: the module library tells the reviewer what’s in the box; the claim-proof matrix tells the reviewer where to verify the pitch claims.