How it is wired — and what is live.
Two pictures. First, how the read-only intelligence flows from your systems of record up to executive synthesis. Second, how the deployed surfaces connect. Every element is tagged so a prospect or an engineer can see, at a glance, what is built today and what goes live when the backend is deployed.
The substrate data-flow
From source systems to executive synthesis. The flow is built; today it runs on synthetic data because the backend is not yet deployed and no real tenant is connected.
Your ERP, MES, WMS, TMS, procurement, CRM, and HRIS — the systems of record. They stay authoritative; AssetShop reads them and never writes back.
Read-only adapters, one per system. A reference adapter passes 12/12 conformance in the harness; vendor adapter scaffolds return not-ready from their health check until validated on a live tenant, so they can never be mistaken for production.
Ingestion, canonicalization, SHA-256 lineage anchoring, and the calibration ledger. The backend passes its full verification suite locally — it is built and tested, but not yet deployed to production.
SCO plus the module previews (Financial, Revenue, Workforce, Risk, Knowledge & Compliance, and the rest) read the substrate read-only. The front ends are built; today they render synthetic data (Meridian Industrials).
Reads across every module to surface the threads that only appear between domains, framed for eight executive roles (CEO, COO, CFO, CMO, CTO, CHRO, CIO, CPO). Built as a synthetic preview.
Calibration
What each tag means — so “built” is never confused with “running in production.”
The host topology
Eight ENS hosts. The public funnel links top to bottom; the trust center is cross-linked from every public host; the gated pages sit deliberately outside it. All surfaces are static, single-file, and pass the validation gates.
What “built” means here, precisely: every surface passes the validation gates (structure, theme integrity, accessibility contrast, ASCII-safe scripts), and the backend passes its verification suite. What is not yet done is founder-owned and deliberately not claimed: pinning to IPFS and setting the ENS contenthashes, deploying the backend, and connecting one ERP on a live tenant. Until those happen, this is a complete, honest preview of a system — not a system in production.