Preston-Test repo

The codebase that IS SuiteCentral 2.0 — production-ready, 9k+ tests, 16 dashboards, full sales surface area for the Squire adoption case.

What it is

A Node.js + TypeScript enterprise integration platform with AI-powered field mapping, located at /mnt/c/Users/kstra/Repos/Preston-Test. The repo is not just code — it’s also the sales artifact for the Squire adoption case, containing the Squire-Executive-Package-v2/ directory and the squire-v2-media-demo/ demo tracks.

Why it matters (to the adoption case)

The repo is the proof. Every claim about SuiteCentral 2.0 — production status, test counts, the 16 modules, NetSuite connectivity — is backed by code in this repo. When Squire’s CTO does technical due diligence, this repo is what they look at.

Key facts (from 01-executive-summary)

• Production-grade, with measurable test evidence
• Multi-provider AI stack
• NetSuite sandbox connectivity proven
• 16-module footprint (12 core operational + 4 extension/platform)

Status

• Production-ready as asserted in 01-executive-summary
• See production-proof for the specific test/quality numbers

What this source DOESN’T say

This source treats the repo as a black-box “production-grade package” — it doesn’t go into:

• Technology stack (Node.js + TypeScript, Alpine.js + Tailwind)
• Build/deploy story (Docker, Terraform/Helm, AWS)
• Specific module dashboards
• The ?demo=true and ?mode=embedded query-parameter modes
• The Squire-Executive-Package-v2/ and squire-v2-media-demo/ directories

These details live in the repo’s own README/CLAUDE.md (not yet formally ingested as source-summaries) and in other notebook sources like 23-ENGINEERING-SCALE-QUALITY.md. This page intentionally stays high-level until those are ingested.

Sources

• 01-executive-summary