---
type: source-summary
title: 'Source: Tier 2 due-diligence batch (8 docs)'
modified: 2026-04-11
tags:
  - due-diligence
  - tier2
  - evaluation
  - source
  - preston-test
---

# Source: Tier 2 due-diligence batch (8 docs)

## What this source is

Eight documents that Squire would open during **deeper due diligence** — after Tier 1 answers "is this real?" and before committing to the pilot. These cover data architecture (what's mock vs fixture vs real), Squire-specific deployment, BC production setup, fixture-to-production migration path, MDM feature depth, the full endpoint registry, operational runbooks, and the FAQ.

Total: ~50,000 chars across 8 files (~5,100 lines).

## Key claims (new content, grouped by document)

### DATA-ARCHITECTURE-MOCK-VS-FIXTURE.md (523 lines)
1. **Three-tier data architecture**: (a) Real connectors = live API calls with real data; (b) Fixture connectors = pre-built realistic data for demos; (c) Mock data = minimal test stubs. The guide maps every connector and module to its tier so evaluators know which data paths are tested with real APIs vs simulated.

### SQUIRE-NETSUITE-MCP-SETUP-GUIDE.md (998 lines)
2. **Squire-specific MCP deployment guide**: step-by-step for deploying the MCP gateway tools in Squire's NetSuite environment. Covers tool registration, policy configuration via `/api/mcp/policies`, user-scoped MCP settings via `/api/settings/mcp`, and a production rollout checklist. This is the Week 2 technical-deep-dive artifact for MCP specifically.

### BUSINESS-CENTRAL-PRODUCTION-SETUP.md (577 lines)
3. **BC production connector guide**: OData v4 API setup, Azure AD app registration, metadata discovery, delta sync configuration, and auth token refresh flow. This is what Squire's BC practice team would follow to wire up SuiteCentral 2.0 to their Business Central environments.

### FIXTURE_MIGRATION_GUIDE.md (958 lines)
4. **Migration path from fixture to production**: step-by-step guide for converting any fixture-based connector to a production connector. Documents what code changes are needed, how to wire real credentials, and how to validate the migration. This answers the evaluator question: "OK the fixtures work — how do I make them real?"

### MDM-FEATURE-GUIDE.md (414 lines)
5. **MDM deep-dive**: Golden Record data model, deduplication algorithm, conflict resolution rules, entity resolution architecture. Extends [[pages/modules/mdm-central]] with implementation detail beyond the narration-level description.

### ENDPOINT-REGISTRY.md (388 lines)
6. **Canonical endpoint registry**: all ~1,035 routes with method, path, auth requirement, and categorization. This is the single source of truth for the API surface. Cross-references to the full API documentation.

### OPERATIONAL-RUNBOOKS.md (669 lines)
7. **Week 8 operational procedures**: deployment (zero-downtime rolling update), incident response (severity classification, escalation paths), backup/recovery (PostgreSQL point-in-time recovery, 15-minute RPO), and security operations (key rotation, certificate renewal). This is what Squire's ops team would use to run SuiteCentral 2.0 in production.

### FAQ.md (581 lines)
8. **FAQ v3.3.0**: Answers to the questions Squire's team will ask during evaluation — AI configuration, connector setup, demo vs production behavior, security model, performance characteristics. Organized as Q&A pairs.

## Pages updated by this ingest

**Updated** (4 existing pages):
- [[pages/concepts/production-vs-demo]] — cross-link to the data architecture mock-vs-fixture guide and the fixture migration guide
- [[pages/modules/mdm-central]] — cross-link to the MDM feature guide for implementation detail
- [[pages/entities/squire-readiness-checklist]] — cross-link to the BC production setup and MCP deployment guides as Week 2 artifacts
- [[pages/entities/demo-site]] — cross-link to the endpoint registry

## Cross-references

- **Fixture migration path exists**: the FIXTURE_MIGRATION_GUIDE answers a key evaluation concern — "if I like the demo, how do I make it real?" The guide documents the specific code changes, credential wiring, and validation steps for each connector. This significantly strengthens the "fixture-based is a feature, not a bug" narrative from Tier 1.
- **Operational runbooks signal maturity**: immature codebases don't have incident response procedures with severity classification, backup recovery with 15-minute RPO targets, or zero-downtime deployment guides. The existence of these runbooks is evidence of production engineering discipline.
- **The FAQ will surface new questions from Squire's team**: it covers ~50 Q&A pairs. Some may raise issues the wiki hasn't addressed yet. Worth reviewing during a future lint pass.

## Notes

- The **BC production setup guide** is especially important for the HintonBurdick context — if HintonBurdick's client base uses Business Central, this guide is what makes the dual-ERP story real for Squire's operations team.
- The **MCP setup guide** is Squire-specific and includes policy configuration examples that reference Squire's NetSuite environment. It's not generic documentation.
- These 8 documents collectively answer: "OK, I believe it's real (Tier 1). Now show me how to deploy it, how to migrate from demo to production, how to operate it, and how to troubleshoot it when things break."