--- type: source-summary title: 'Source: 22-MODULE-LIBRARY.md' modified: 2026-04-07 tags: - module-library - modules - source --- # Source: 22-MODULE-LIBRARY.md ## What this source is The **definitive text reference for the 16-module footprint**. It is the markdown companion to the interactive `/Squire-Executive-Package-v2/22-MODULE-LIBRARY-STANDALONE.html` page in the live demo. Per its own preamble, it exists "when NotebookLM needs a text-only reference for module footprint and routing" — it is specifically designed to be read by AI assistants (like this wiki). At 1,644 characters, it is compact but authoritative. It resolves the **long-running 12-core-vs-4-extension open question** and corrects a drift in the Brain1 wiki's module accounting. ## Key claims 1. **The 12 core modules are explicitly named**: SupplierCentral, PaymentCentral, CustomerCentral, MDMCentral, SyncCentral, QualityCentral, PayoutCentral, InstallerCentral, ServiceCentral, InventoryCentral, FinanceCentral, ContractCentral. → [[pages/concepts/module-library]] (corrected) 2. **The 4 extension/platform modules are explicitly named**: WorkflowCentral, PortalCentral, Vendor Portal, Context Sidecar (labeled "platform demo"). → [[pages/concepts/module-library]] (corrected) 3. **Installer Central IS a core module (#8)**. The narration-scripts.js absence flagged in [[sources/narration-scripts]] is now resolved — Installer Central is real and in the core 12; its missing narration entry is a data gap in that file, not an indicator that the module doesn't exist. → [[pages/concepts/module-library]] 4. **Customer Payment Portal is NOT a module**. My earlier [[pages/concepts/module-library]] page (based on narration-scripts.js) counted Customer Payment Portal as module #5. This source's authoritative 16-module list does not include it. Conclusion: Customer Payment Portal is a **demo video** that showcases a sub-feature of CustomerCentral or PaymentCentral, not a standalone module. → [[pages/concepts/module-library]] (needs correction) 5. **Context Sidecar is the 16th module, classified as an extension/platform demo**. It's listed as #4 in the extension bucket with the explicit label "(platform demo)" — distinguishing it from the other extension modules (WorkflowCentral, PortalCentral, Vendor Portal) which are full modules. The "(platform demo)" qualifier suggests Context Sidecar may be more of a demonstration of platform capabilities than a standalone product module. → [[pages/modules/context-sidecar]] and [[pages/concepts/module-library]] 6. **Evidence routing pattern (NEW)**: `` videos live at `/squire-v2-media-demo/watch/videos/player.html?video=`. This is the canonical URL template for module demo videos. → [[pages/entities/demo-site]] 7. **AI Field Mapping live tool URL (NEW)**: `/ai-field-mapping-editor.html` on the demo host. This is a live interactive tool, not just a demo video. Worth adding to the demo-site URL catalog. → [[pages/entities/demo-site]] 8. **Context Sidecar reviewer proof URL (NEW)**: `/squire-v2-media-demo/read/context-sidecar-proof.html`. A new Read-track URL not previously referenced. → [[pages/entities/demo-site]] 9. **Context Sidecar JSON is technical-only**: *"Raw Context Sidecar JSON should be treated as technical proof only, not the primary reviewer path."* Means there's a raw JSON artifact for technical reviewers, distinct from the narrated demo video. → [[pages/modules/context-sidecar]] 10. **Dashboard evidence lives under `/public/`**: module-specific dashboards are at `/public/.html`. General routing fact. → [[pages/entities/demo-site]] 11. **Cross-reference to `23-ENGINEERING-SCALE-QUALITY.md` and `26-CANONICAL-METRICS-AND-WORDING.md`**: the source explicitly asks readers to "keep this file aligned with" both. Both are in the notebook; both will be needed to reconcile metric and module claims in the future. ## Pages updated by this ingest **Created** (0 new pages): all claims land on existing pages. **Updated** (3 existing pages): - [[pages/concepts/module-library]] — **corrected**: replaced the narration-scripts.js-derived list (which counted Customer Payment Portal as a module and was confused about Installer Central) with the authoritative 12-core + 4-extension list from this source. Added the evidence routing patterns. - [[pages/concepts/suitecentral-2-overview]] — resolved the 12-vs-4 split open question - [[pages/entities/demo-site]] — added the new URLs (ai-field-mapping-editor, context-sidecar-proof, dashboard routing pattern) ## Notable quotes > "Total library footprint represented in executive/demo flow: 16 modules (12 core + 4 extension/platform)." > — Notes section > "Context Sidecar (platform demo)" > — the 4th extension/platform module entry, explicitly qualified ## Cross-references / contradictions found - **Corrects a wiki drift from the narration-scripts.js ingest**: my earlier module-library page counted 15 narration-backed modules plus Installer Central (no narration) for 16 — BUT I also listed Customer Payment Portal as a module because it had its own narration entry. The authoritative list here shows Customer Payment Portal is NOT a module. So the 16 modules are: the 11 narration-backed "-central" modules I listed (contract, customer, finance, inventory, mdm, payment, payout, portal, quality, service, supplier, sync, vendor-portal, workflow, plus mdm-central = 15) minus Customer Payment Portal (1) plus Installer Central (1) plus Context Sidecar (1) = 16. The corrected list aligns with this source. - **Installer Central open question partially resolved**: the module exists and is in the core 12. Its absence from `public/js/narration-scripts.js` is a narration-data gap, not a module-existence gap. The `installer-central-proximity.webm` video file in the asset manifest is its demo; the narration text may live elsewhere or may be embedded in the video audio (like the AI Governance Layer hook video). - **Context Sidecar terminology**: 22-MODULE-LIBRARY.md calls Context Sidecar a "platform demo" and classifies it as an extension/platform module. Earlier sources ([[sources/01-executive-summary]] slide 2, [[sources/ai-governance-layer-video]]) called it "the killer app." Both are accurate — it IS the killer app AND it IS classified as an extension/platform demo in the module library. The two framings are not contradictory; they're different perspectives (pitch framing vs product architecture). - **Vendor Portal naming**: this source uses "Vendor Portal" (two words) while the other 15 modules are camelCase single words ("VendorPortal" form does not appear here). Minor naming inconsistency but not contradictory. ## Notes - This source is **written specifically for AI assistants** — the preamble says "when NotebookLM needs a text-only reference." That's Brain1's exact use case. Expect more notebook sources to be structured similarly (as text companions to live pages). - The evidence routing patterns (especially `/squire-v2-media-demo/watch/videos/player.html?video=`) are useful structural metadata that should inform how we catalog future video-related content on [[pages/entities/demo-site]]. - The cross-reference to `26-CANONICAL-METRICS-AND-WORDING.md` is interesting — it suggests there's a single "source of truth" metrics document that should reconcile all the test-count vintages captured on [[pages/concepts/production-proof]]. Worth ingesting next if the user wants to close the test-count vintage story definitively.