---
type: source-summary
title: 'Source: 05-TECHNICAL-PROOF.md (condensed bullet version)'
modified: 2026-04-07
tags:
  - technical-proof
  - condensed
  - source
  - preston-test
---

# Source: 05-TECHNICAL-PROOF.md (condensed bullet version)

## What this source is

A **condensed bullet-point version** of the technical proof document — NOT a renumbering of [[sources/04-technical-proof]]. Both `04-TECHNICAL-PROOF.md` (full 4-tier feature inventory) and `05-TECHNICAL-PROOF.md` (compact 6-section summary) exist as separate files in the Preston-Test repo.

Referenced by [[sources/09-claim-proof-matrix]] claim #7 ("Platform quality is enterprise-grade") at URL `/Squire-Executive-Package-v2/05-TECHNICAL-PROOF-STANDALONE.html` — so **this is the version used in the live review flow**, not 04. 04 is the deeper internal document.

## Key claims

1. **Test Infrastructure** — 9,510 total (9,476 passed, 34 skipped), 100% executed pass rate, 419 suites, 64.59% code coverage. Consistent with [[sources/04-technical-proof]] and [[sources/26-canonical-metrics-and-wording]].
2. **4 verified AI providers**: OpenAI GPT-4o, Claude Sonnet, OpenRouter, LMStudio (local). **Field mapping accuracy: 95%+.** Matches 04-TECHNICAL-PROOF and is consistent with canonical wording.
3. **5 connectors listed**: NetSuite (OAuth 1.0), Salesforce (OAuth 2.0), **Shopify (OAuth 2.0)**, Oracle (REST/JDBC), Business Central (OData v4). → **CONTRADICTS [[sources/26-canonical-metrics-and-wording]]** which names 6 connectors: NetSuite, Business Central, Salesforce, HubSpot, ShipStation, Oracle. This source has **Shopify** (not in canonical) and is missing **HubSpot** and **ShipStation**.
4. **12 core modules** listed exactly matching [[sources/22-module-library]] (SupplierCentral through ContractCentral). Consistent.
5. **Infrastructure stack**: Terraform + Helm + Kubernetes + GitHub Actions + AES-256-GCM + PostgreSQL + SQLite. Consistent with [[sources/04-technical-proof]].
6. **Production Readiness**: "100% Complete" across Core Platform, AI Orchestration. Documentation at 85%. "Remaining Work: 36-60 hours" — this is a notable tension: if the platform is 100% complete, the 36-60 hours of remaining work is documentation polish, not missing features.

## Pages updated by this ingest

**Updated** (2 existing pages):
- [[pages/concepts/claim-proof-matrix]] — clarified that "05-TECHNICAL-PROOF" is a real separate document (not a renumbering) and 09-claim-proof-matrix correctly references it
- [[pages/concepts/canonical-metrics]] — added Shopify connector drift as a documented known-stale claim in 05-TECHNICAL-PROOF.md

## Cross-references / contradictions found

- **Shopify drift (NEW, flagged)**: this source lists **Shopify** as a 3rd connector. [[sources/26-canonical-metrics-and-wording]] is authoritative and names a different 6-connector set (NetSuite, Business Central, Salesforce, HubSpot, ShipStation, Oracle) — **no Shopify**. Possible explanations: (a) Shopify was an earlier connector that was replaced or merged; (b) 05-TECHNICAL-PROOF is stale and should be refreshed to match canonical; (c) Shopify is an informal or in-development connector that doesn't yet qualify as "production-demonstrated" per the canonical wording. Most likely (b) — this file is older than 26-CANONICAL-METRICS and drifted. Since 05 is what the claim-proof matrix points at, **a reviewer walking Path C will see the stale Shopify claim**, which contradicts the canonical pitch.
- **"100% Complete" + "Remaining Work: 36-60 hours"** is internally tensioned. Resolution: 100% complete refers to Core Platform + AI Orchestration features; 36-60 hours refers to Documentation at 85%. Not a contradiction if read carefully, but the juxtaposition is awkward.
- **Resolves the "05-vs-04" numbering question**: NOT a renumbering. Both files exist side by side. 04 is the comprehensive internal technical proof (~4,400 chars, 4 tiers of features, architecture, LOC, CRUD, NetSuite sandbox); 05 is the compact public-facing bullet summary (~1,300 chars, 6 sections, listed numbers only). The claim-proof matrix correctly references 05-TECHNICAL-PROOF-STANDALONE.html as the Path C verification artifact.

## Notes

- This source is significantly shorter than [[sources/04-technical-proof]] (1,300 vs 4,400 chars). The trade-off: 05 is easier to skim in the Path C 10-minute slot; 04 has the actual source-file paths, version numbers (v2.5, v3.2, v3.3, v3.4), and NetSuite sandbox ID that make verification feasible.
- The **Shopify drift** should be either (a) reconciled by updating 05-TECHNICAL-PROOF.md in the repo to match 26-CANONICAL-METRICS, or (b) flagged to the product owner for a manual reconciliation. It's a wording-governance issue per the canonical wording style guide's governance requirement: *"Any document added to NotebookLM should conform to this file before packaging."* — 05 doesn't currently conform.
- The "36-60 hours remaining work" figure is the closest thing to a completion timeline in the corpus — but it's explicitly about documentation polish, not feature work.