Squire Production Readiness Checklist
A 4-phase, 2-3 day pre-flight checklist written specifically for Squire to validate the Preston-Test Integration Hub with real customer data. Grade: A+ (100/100). The document Reuben Cook should run through during the Phase 1 evaluation.
What it is
A comprehensive production readiness checklist at docs/squire/PRODUCTION_READINESS_CHECKLIST.md in the Preston-Test repo. Explicitly written for Squire’s evaluation — “This checklist ensures Preston-Test Integration Hub is production-ready for Squire’s SaaS integration advisory services.”
The 4 phases
| Phase | Focus | Duration | What it validates |
|---|---|---|---|
| 1: Connection | Connector auth + data retrieval | ~1 hour | NetSuite OAuth, BC OData, AI provider wiring |
| 2: AI Validation | AI accuracy + governance | ~1 hour | Field mapping accuracy, reasoning traces, hallucination detection |
| 3: Real Data | Squire’s actual customer data | ~4 hours | Real-world data flowing through the platform end-to-end |
| 4: Scale | Load testing + performance | ~4 hours | Throughput under realistic concurrent workloads |
Total: 2-3 days for complete validation, assuming credentials are prepared in advance.
Pre-flight requirements (30 minutes)
Before starting Phase 1, Squire needs:
NetSuite credentials: Account ID, Consumer Key + Secret (OAuth 1.0a), Token ID + Secret, API endpoint URL
Business Central credentials: Azure AD Tenant GUID, Client ID + Secret, Environment (production or sandbox), Company GUID
AI providers (optional but recommended): OpenAI API key (GPT-4o-mini at ~$0.001/request), Anthropic API key (Claude), or just run LMStudio locally (free)
Infrastructure: Node 18+, PostgreSQL/MongoDB, npm install + npm run build passing
Why this matters for the adoption case
This checklist is the operational answer to the 30-day evaluation phase Week 2 (“technical deep-dive”). When the pilot calendar says “Week 2: technical deep-dive,” the checklist IS the deep-dive — it tells Reuben exactly what to verify, in what order, with what commands, and what the expected results look like.
The CTO role brief says the CTO should validate “production behavior.” This checklist is how.
Sources
- tier1-repo-evaluation-batch — PRODUCTION_READINESS_CHECKLIST.md (1,256 lines, April 9, 2026)