How to Explore This Project
SuiteCentral 2.0’s knowledge surfaces are organized around four audiences — pick the path built for how you evaluate.
Choose your surface
Business leader or executive evaluator
- Start here in the wiki: the front door role paths — CFO, CTO, COO — or the business reading path.
- Ask questions with citations: the SuiteCentral 2.0 NotebookLM notebook answers from the canonical source pack and cites its sources.
Outside engineer or AI reviewer
- Read the source: the public reviewer snapshot — a curated mirror of the production tree with audit scripts you can run yourself. Its README is the evaluation entry point.
- Fast orientation: DeepWiki’s auto-generated wiki over that snapshot — architecture pages plus a “chat with this codebase” box (third-party analysis; the proof cards remain the evidence of record).
- Evidence of record: the proof cards — per-component Status / Tests / Known Gaps / 60-second verification.
Developer or AI coding agent
- Machine-readable wiki: llms.txt (index) and llms-full.txt (full content) — feed either to your agent.
- The layer map: SuiteCentral Code Architecture and its seven per-layer pages, starting at Layer 1.
- In-repo guidance:
AGENTS.mdat the repo root is the CLI-agent operating manual (mirrored in the reviewer snapshot).
Product user
- In-app help: the Help chat answers product questions grounded in the live documentation set.
- Interactive architecture: the Code Architecture Dashboard — click any layer of the infographic for its summary, docs, and suggested questions wired to the help assistant.
The seven architecture layers
1 · User & Operator Surfaces → 2 · HTTP-API Edge → 3 · Core Application Services → 4 · AI & Intelligence → 5 · Governance & Safety (vertical rail) → 6 · Connector & Integration Layer → 7 · Data, Evidence, and Publishing
Last refreshed: 2026-07-06