Source: 01_VISION_DOCUMENT.md
What this source is
The strategic vision document for SuiteCentral 2.0. Version 1.0, dated April 9, 2026 (same vintage as business-case.md and value-proposition.md — all refreshed 2 days before this session). Audience: Squire Executive Leadership & Technical Teams. At ~28,000 chars it is the second-largest source in the corpus after value-proposition.md.
This is the document that frames the “why” behind every architectural decision in SuiteCentral 2.0. It establishes 7 design principles, names the Two-Platform Problem explicitly, and provides a competitor timeline.
Key claims (new content beyond prior sources)
The Two-Platform Problem — EXPLICITLY NAMED
- “The Two-Platform Problem” is the section heading for Squire’s specific pain. Previously this term was inferred from multiple sources but never explicitly named in an ingested document. Now formally confirmed. → squire — resolve the “Two-Platform Problem is still not explicitly named” open question.
- 180K error detection + 180 billion. → NEW number for the market framing.
Competitor timeline (NEW, with Squire’s window)
- Celigo: AI status “Announced”, timeline 6-12 months, Squire’s window is NOW
- Boomi: AI status “Beta (300M+ integrations trained)”, timeline 2026, window 12 months
- MuleSoft: AI status “Roadmap”, timeline 2026, window 12 months
- Workato: GenAI Platform “Live”, window Closing
The 7 design principles (NEW framework, originally labeled “Six Rules” but lists 7)
- P1: ERP-Native, Not ERP-Adjacent — “We live inside the ERP, not next to it.” Platform embeds via iframe, understands NetSuite governance limits and OData quirks.
- P2: AI-Assisted, Human-Approved — “AI suggests. Humans decide. Audit trails prove.” Approve-to-Apply with cryptographic hash verification.
- P3: Cost Transparency, Not Cost Surprise — “You should know what AI costs before you click the button.” Per-provider cost comparison, budget alerts, hard stops per tenant.
- P4: Dual-ERP, Single Platform — “NetSuite and Business Central are equal citizens.” Single codebase, connectors share base architecture.
- P5: Built for Ourselves First — “If it doesn’t work for Squire, it doesn’t ship.” SC 1.0 proves the need across 40+ environments; SC 2.0 enters through controlled pilot.
- P6: Explainable AI, Not Black Box AI — “Every AI decision comes with a receipt.” Confidence breakdown, reasoning traces, hallucination detection.
- P7: Demo What Operators Actually See — “Proof artifacts must look like real ERP work, not generic middleware.” Scene 5 is NetSuite-first, MCP mentions tied to policy proof, not protocol trivia.
Test count — canonical baseline
- 9,476 / 9,510 tests (9,476 passed, 34 skipped) in 419 suites. Matches the April 19, 2026 canonical in 26-canonical-metrics-and-wording.
Architecture — the “Three-Layer Integration Stack”
- Three layers: Client (embedded sidecars in NS + BC + standalone dashboard), Intelligence (AI providers, MCP gateway, governance), Data (connectors, sync, MDM).
Pages updated by this ingest
Updated (3 existing pages):
- squire — “Two-Platform Problem” now explicitly named and fully described
- suitecentral-2-overview — added the 7 design principles as a section
- competitive-landscape — added the competitor timeline table with Squire’s window assessment
Cross-references
- 7 principles labeled “Six Rules”: minor inconsistency — the heading says “six” but 7 are listed. P7 (“Demo What Operators Actually See”) was likely added after the heading was written.
- 9,476 tests matches canonical: vision document cites the same April 18, 2026 canonical baseline as 26-canonical-metrics-and-wording and 24-strategic-acquisition.
- “$180 billion industry”: first market-size number in the corpus. Useful for investor/board context.
- Workato’s window is “Closing” per this doc — but Workato wasn’t in 25-competitive-evidence-register. The vision doc and business-case both surface Workato as a competitor the register hasn’t tracked yet.