The outcome you are walking toward
A walkable map of the six named systems that make Business OS feel like one runtime instead of a product grid: Pulse senses · Mesh connects · Synapse fires · Cortex thinks · Aria acts · Forge transforms. You leave able to brief a colleague on what each layer does, what is a public product dock, and what still belongs to policy and evidence docs — without inventing coverage you have not seen.
One runtime, six layers — not six glued products
Most software stacks are a collection of tools. Business OS is narrated as an organism. The substrate chain is the spine of that narration:
- Pulse senses people, places, equipment, and lifestyle signals.
- Mesh connects devices, cameras, and assets as a living interconnect fabric.
- Synapse fires real-time loops — priority signals between nodes.
- Cortex thinks under the policy you control.
- Aria (with the agent team) acts inside hard boundaries.
- Forge transforms experience into better playbooks and skills under governance.
These are layers of one runtime. If a briefing treats them as unrelated SKUs, ask how a single critical loop crosses them without a second integration project per hop.
Pulse — perception
Pulse is the sensing plane: what is happening at the location that the organism must notice. Diligence posture: sensing without an operating record becomes noise. Pair Pulse conversations with data fabric orientation so signals land on shared facts with brand context, not shadow spreadsheets.
Mesh — physical interconnect
Mesh is the physical device and asset interconnect fabric — discovery, registration, health, multi-tenant routing, edge. One diligence distinction that must stay sharp: Mesh connects physical endpoints; the Data Fabric is the data plane that governs the record. Interconnect fabric is not data fabric. Kits and edge nodes are meant to speak Mesh natively; the STORE / hardware story is composition, not a random device catalog — see STORE Solution and the vertical hardware playbooks.
Synapse — the event bus
Synapse is the real-time neural event and feedback bus: low-latency, context-aware routing, closed loops between nodes. Public orientation for event shape and integration boundaries lives in webhooks & the event substrate and the family map in integration patterns. Diligence ask: can a priority signal move without inventing a one-off queue per vendor?
Cortex — judgment under policy
Cortex is agentic judgment operating under policy you control — not unbounded autonomy. The control loop you should be able to reconstruct is owned by governed agent boundaries, approval gates, and the audit trail. The counsel-facing walkthrough of authority as signed data is Verify what an agent is allowed to do.
Aria — coordinated action
Aria coordinates the agent workforce: goals and signals in, specialist work routed, escalation when confidence or authority is insufficient. Agents are the governed will of the organism; they do not sit beside Business OS as a separate "AI product." The roster and scenarios live on Agents. Diligence ask: which actions are proposals, which are gated, and which are forbidden offline?
Forge — continuous transformation
Forge is the outcomes engine that turns experience into better playbooks and skills — under pressure, under governance. Local forge activity feeds the compounding story; network propagation of winning methods is Franchise OS territory, deepened in how the organism compounds. Diligence ask: what is extracted automatically versus nominated by humans, and what evidence package a change must produce before it spreads?
Offline and edge — the chain must not go blind
Critical loops are designed to survive imperfect connectivity. The careful public contract is Read the offline contract your locations run on. If Mesh and Synapse only work while the uplink is perfect, the organism is a dashboard with cameras — not a location runtime.
How to use this chain in a briefing
- Walk the six verbs in order once. Do not skip to Forge demos before Pulse and Mesh are concrete for the site.
- Name the public docks you can open today: Mesh, Synapse, Forge, plus Business OS.
- Push every autonomy claim back to gates and evidence docs — never to a slide metric.
- Separate local runtime (this chain) from network learning (Business OS vs Franchise OS).
Non-goals for this leaf
- No named-vendor battle cards, certification badges, or invented availability guarantees.
- No claim that every vertical already exposes a full public recipe for every hop.
- No pricing, packaging, or "AI transformation" theater.
When the chain is clear, compose the rest of the organism — kits, agents, verticals, Franchise OS — in Name what the organism is made of, and continue counsel review via diligence resources.