Source: 31-SUITECENTRAL-EVALUATION-SUMMARY.md

What this source is

An independent evaluation summary for a Squire leadership decision (snapshot 19603d6, 2026-06-03). It states a grade, a recommendation, and — the point of the doc — what both are based on, so the conclusion can be trusted rather than taken on faith. Its central signal is that two independent reviews (one longitudinal, one cold) have converged on the same snapshot.

Key claims

1. Grade: A (longitudinal) ≈ A− pilot / B+ platform / B− replacement (cold review, this snapshot) — the two now agree within ~half a grade tier. The conservative composite to present is A− pilot / B+ platform / B− replacement. → three-review-paths
2. Recommendation: proceed with a 30-day SyncCentral pilot — Sync Error AI Assist + AI Field Mapping + DLP/audit overlay on ONE existing production SyncCentral deployment. Enhance, do not replace. Do NOT fund a rebuild or sell it to clients as a finished platform yet. → pilot-30-60-90, revenue-model
3. What the grade rests on (evidence-first, repeatable): a clean reviewer-runnable suite (11,581 tests passing, 0 failures, 0 load errors on 19603d6); structural honesty gates that pass (connector status 5/1/11/1 enforced by an audit gate, proof cards, a zero-any type-safety gate on the 87-file governance core, strict-null budget, per-file coverage budget); source-level verification of every major capability; and a live AI accuracy benchmark (95.1% top-1, 0 hallucinations; 96.7% with Claude Haiku 4.5, 100% on a second Business Central pair) disclosed as a Phase-B fixture figure. → production-proof, claim-proof-matrix, 26-canonical-metrics-and-wording
4. The gap-closure trajectory is the evidence: every closeable gap a reviewer named was closed with code+tests+docs together — snapshot-hygiene debt, ~510 anys on the safety surface (→ 0, CI-enforced), coverage transparency, the reconciliation stub (→ real registry + NetSuite↔BC handler, 164 tests), SyncCentral routes not behind the kill switch (→ gated at parity + a suspended→403 regression test), stale product-card verdicts. One remains OPEN: the production-tier NetSuite credential test (V3). → 32-v3-netsuite-production-test-runbook, squire-readiness-checklist
5. The two reviews converged: the cold reviewer’s grades rose across nearly every dimension (Reality B+→A−, internal-pilot B+→A−, evidence-discipline B+→A, etc.). What moved them was the reviewer-facing evidence system (README/EVALUATION indexing, machine-readable metrics.json, COVERAGE.md/TYPE-SAFETY.md) — “no longer just code plus claims.” This review can confirm what the cold review couldn’t: running the suite on the identical commit confirms the metrics live, not just asserted. → canonical-metrics, preston-test-repo
6. Portfolio view (per product): SyncCentral = Enhance (the pilot), High confidence; PaymentCentral = Integrate (DLP/audit overlay first), High; CustomerCentral / VendorCentral = Defer; Payout Rec = Defer (needs Celigo connector); Elastic Suite = Defer (no Elasticsearch connector). → squire
7. What the pilot does NOT resolve (Squire-side, later): SOC 2 attestation (needs an independent CPA firm — Squire & Company cannot attest Squire Technology; shared leadership breaks auditor independence; readiness-advisor only) and a production reference customer (a BD outcome, not a code milestone).

Cross-references

• Same recommendation, independently: 30-suitecentral-for-squire reaches “Enhance, pilot #1+#2 on one deployment” from the features/speed-to-revenue angle; this doc reaches it from the evaluation/grade angle. The two June-2026 leadership docs are mutually reinforcing.
• 11,581 vs the canonical badge count: this is the env-sensitive live full-suite count on 19603d6; the README/badge figures and 26-canonical-metrics-and-wording use the unit-profile count — the gap is the documented env-sensitivity, not a contradiction. → canonical-metrics
• The one open item (V3) is the subject of its own runbook, 32-v3-netsuite-production-test-runbook, and is the gate before a paid pilot — not before an internal one.

Pages updated

• three-review-paths — the cold/longitudinal convergence to within ~half a tier; A− pilot / B+ platform / B− replacement composite
• pilot-30-60-90 — the 30-day pilot scope table (tenant, ERP, features, success metrics) and what it does/doesn’t resolve
• squire-readiness-checklist — gap-closure status table with V3 as the single remaining OPEN build-side item