How it is wired, and what is live.
You do not have to take our word for anything: every claim on this estate is independently verifiable, and the harness that proves it ships with the product.
Two pictures: how read-only intelligence flows from your systems of record up to executive synthesis, and what stands at each stage today. Every element is tagged so a prospect or an engineer can see at a glance what is built now and what goes live when the backend deploys. Read-only is the architecture, not a setting: every arrow is a one-directional read, and no write path exists in the product.
The substrate data flow
From source systems to executive synthesis
The flow is built; today it runs on the SYNTHETIC tenant because no real tenant is connected, and it says so at every stage.
Source systems, EXTERNAL
Your ERP, MES, WMS, TMS, procurement, CRM, and HRIS: the systems of record. They stay authoritative; the platform reads them and never writes back.
Connectors, PER-CONNECTOR GATES
Read-only adapters, one per system. Counts derive from the canonical ladder at page build: 8 certified and conformance-tested, 9 in active development, 56 on the portfolio. Scaffolds return not-ready from their health check until validated on a live tenant, so they can never be mistaken for production.
Shared substrate, BUILT, NOT DEPLOYED
Ingestion through the hardened validation door, canonicalization, SHA-256 lineage, and the calibration record. The backend passes its verification battery in this tree on every sealed run; it is built and tested, and production deployment is the founder-owned step, stated rather than implied done.
Domain modules, BUILT ON SYNTHETIC
The flagship and the domain modules read the substrate read-only. The fronts are built and render the SYNTHETIC Tenant-One profile today; live data arrives at deploy plus credentials, and every gated call fails closed with its gate named until then.
Executive synthesis, BUILT
Reads across every module to surface the threads that only appear between domains, framed per executive role, on the same entitlement gates the suites prove.
The write path, NONE
There is no optional write-back and no approval entry into any source system; the v3.95-era opt-in write path is superseded by decision D-R62. Approvals and decisions live in the platform own append-only ledger, and the source transaction is never touched.
Calibration vocabulary
So built is never confused with running in production
BUILT means it works today in its stated context and its checks can fail red. BUILT, NOT DEPLOYED means it exists and passes its battery but is not running in production. SCAFFOLD means the structure is in place and reports not-ready until validated on a real tenant. AT DEPLOY means it requires the founder-owned steps, deploying the backend and connecting one system on a live tenant, and none is live yet. EXTERNAL means the customer systems of record, read and never written.
The host topology
One estate, one app, one twin
The public estate you are reading is one generated set: the landing, the Trust Center, the department pages, the policies, and the evidence assets, published together and guarded by the same claims suites. The product itself is the Guided Walkthrough (Platform Demo), a single-file build of the working platform on the synthetic tenant. A decentralized twin of the app packages for name-resolved hosting as a separate deploy target. Until the founder-owned deploy steps run, this is a complete, honest preview of a system, not a system in production, and the status page says exactly that.