Guides

Offline contracts, authority, conformance, and counsel-grade review walks — what holds when the network or the audit starts.

• Trust & edgeRun a security review of the platformFor counsel and security reviewers: work through isolation, sign-on, gates, and audit evidence in review order, and finish knowing exactly what to verify live in the product.
• Trust & edgeVerify the audit trail hands-onFor counsel: go from reading the evidence model to reconstructing a real action — actor, brand context, gate decision, and outcome — during a live review session.
• Trust & edgeRead the offline contract your locations run onFor counsel: the offline behavior contract your edge locations are designed to run under — what must continue, what may degrade, what is forbidden while disconnected, and how a location reconciles its history when the uplink returns.
• Trust & edgeVerify what an agent is allowed to doFor counsel: read the authority model the way an auditor would — capabilities as signed data, approval gates on high-impact actions, and an evidence record that answers "why did the agent do that?" months later.
• Trust & edgeCheck the level behind any conformance claimFor counsel: place any conformance claim against the four certification levels, see which domains and test suites sit behind each level, and know exactly what is public versus what is shared under NDA.

From first briefing to network organism: pilots, tenancy structure, agent policy, metering, and compounding.

• Institutional pathRun a pilot that earns expansionFor operators: take one bounded workflow from kickoff to a go/no-go review with proof criteria written down first — the only rollout shape we recommend.
• Institutional pathStructure a new brand on the shared platformFor integrators: map a new brand onto the tenant hierarchy — where isolation is enforced, how brand, region, and location nest, and what to decide before onboarding starts.
• Institutional pathSet agent policy before you automateFor operators: classify every action an agent may take by consequence, put irreversible work behind named approval gates, and end with a written policy your auditors can read.
• Institutional pathStand up royalty and fee metering across brandsFor operators and finance leads: get usage and fees metering onto the shared ledger with splits you can reconcile — per brand, per location, without a spreadsheet layer.
• Institutional pathSee the path from first briefing to network organismFor operators: the full deployment path in five named phases — each with a goal, explicit exit criteria, and the artifacts that carry the decision forward — so commercial commitment never runs ahead of proven value.
• Institutional pathWalk the path from first briefing to network organismFor operators: the eight stages a serious multi-location buyer actually travels — from first skeptical signal to a compounding network — with what you should expect from us at each one.
• Institutional pathSee how local excellence becomes network intelligenceFor operators: the compounding loop in full — how a method discovered in one location is captured as a versioned playbook, evaluated on evidence, propagated under governance, and rolled back if it fails — and why the network is designed to compound with scale instead of decay.
• Institutional pathTell Business OS from Franchise OS without a deckFor operators: the durable distinction between the location-level organism runtime and the network learning layer — what each owns, what neither pretends to own, and how they compose under one authority floor.
• Institutional pathWalk the six-system substrate chainFor operators: the organism runtime in signal order — Pulse senses, Mesh connects, Synapse fires, Cortex thinks, Aria acts, Forge transforms — with honest links to the public docks and the docs that govern judgment and evidence.
• Institutional pathName what the organism is made ofFor operators: the composition checklist for a living location and network — certified kit posture, edge offline contract, policy-bound agents, Business OS, Franchise OS, vertical intelligence, and the shared authority floor — with honest links to the public leaves that own each part.
• Institutional pathBrief Helix without mistaking it for a membership stackFor operators: how Helix specializes Business OS for multi-location fitness — member progression, floor intelligence, Helix Coach, and Axon as Mesh specialization — with honest links to the fit silo and the public substrate docks.
• Institutional pathBrief Ember without mistaking it for a POS stackFor operators: how Ember specializes Business OS for multi-location hospitality — kitchen flow, inventory honesty, Ember Service, and sacred offline ticket/payment loops — with honest links to the rest silo and the public substrate docks.
• Institutional pathBrief Scaffold without mistaking it for a job-site app stackFor operators: how Scaffold specializes Business OS for construction networks — field progress vs plan, safety observations, Scaffold Field, and harsh-environment offline loops — with honest links to the build silo and the public substrate docks.
• Institutional pathBrief Domain without mistaking it for a PMS stackFor operators: how Domain specializes Business OS for multi-property portfolios — tenant experience, predictive maintenance, Domain Steward, and access/safety offline loops — with honest links to the realty silo and the public substrate docks.
• Institutional pathBrief Catalyst Capital without mistaking it for a fund admin stackFor operators: how the capital lane stays agent-authority only — settlement integrity, treasury signals, risk flags, and capital allocation support on one governed record — with honest links to the capital silo and the public substrate docks, and no kit sales theater.
• Institutional pathBrief Codex Counsel without mistaking it for a practice-management storefrontFor counsel: how the law lane stays agent-authority only and in design — intake quality, matter progression, trust-aware workflows, and deadline and obligation tracking — with honest links to the law silo and the public substrate docks, and no kit sales theater.

Hardware playbooks for Helix, Ember, Domain, and Scaffold — kit composition without inventing inventory.

• Vertical hardwareSpec the hardware for a Helix clubFor operators: the full hardware posture for one Helix club — the edge node that runs the floor, the Vision Intelligence kit class for form and pose, access and check-in, lockers and displays, the five kit tiers, and the offline contract a 24/7 club is designed to keep.
• Vertical hardwareSpec the hardware for an Ember dining roomFor operators: the reference hardware configuration for one Ember location — commerce kit, vision, and back-of-house layers, the four kit tiers, the offline contract the stack is designed to keep, and where Ember Service activation sits in the deployment sequence.
• Vertical hardwareSpec the hardware for a Domain propertyFor operators: choose the hardware posture for one Domain property — the edge core, access and identity, environmental sensing, and privacy-zoned cameras — as a reference configuration finalized per site survey, staged to match the realty rollout.
• Vertical hardwareSpec the hardware for a Scaffold job siteFor operators: the reference hardware configuration for a construction site — rugged edge, presence and PPE sensing, the strictest offline contract in the lineup, and the kit tier that matches your site size and risk profile.

Evidence package shape, stakeholder briefing map, and integration pattern families — templates, not fake filled packs.

• Commercial enablementKnow what a Phase 1 Evidence Package must containFor operators and counsel: the category map of a Foundation Pilot exit package — what must appear before a go/no-go, what stays briefing-only, and what this page deliberately does not publish.
• Commercial enablementKnow who we brief before a multi-stakeholder dealFor operators: the role-shaped briefing map — which stakeholder jobs we prepare for, what each conversation is for, and what stays internal rather than published as a generic deck.
• Commercial enablementMap the integration patterns the platform already documentsFor integrators: actionable outlines for identity, Mesh–Synapse events, edge offline, agent authority, data fabric, and STORE kits — each linked to real docs and guides, not a fake coverage library.
• Commercial enablementBrief MCV.STORE as a Solution without inventing a cartFor operators: how MCV.STORE stays a Solution — physical organism kits and lines on one Mesh-native surface — with honest waitlist and labeled pre-sale paths, and no fake inventory counts or public unit prices.