The outcome you are walking toward
A diligence briefing you can give without collapsing Domain into "another PMS." You leave able to name what Domain owns as the realty vertical orchestrator, how it sits on Business OS, which public docks carry the substrate hops, and what remains designed-for / staged — without inventing NOI lifts, occupancy rates, or shipped coverage you have not seen.
Domain is an orchestration, not a leasing stack
Domain is the adaptive Property Intelligence orchestrator for buildings and multi-property portfolios. The public silo is MCV.REALTY — Domain. Category-level posture only: property-management systems manage leases and tickets; Domain is designed so every building becomes a living domain that senses access, environment, and equipment, connects building systems, and fires real-time signals — forging better tenant experience, predictive maintenance, and building health across the portfolio.
MCV.REALTY is in staged rollout — scope is set, availability follows proof. Every capability on the public silo is described as designed to operate, not as shipped production behavior.
If a briefing treats Domain as a standalone PMS SKU beside Business OS, ask how access, habitability, maintenance, and tenant recovery cross sensing, interconnect, events, judgment, action, and forging without a second integration project per hop. The signal-order walkthrough is Walk the six-system substrate chain.
What Domain specializes (honest domains)
Public depth on the realty silo organizes around operating domains — diligence vocabulary, not a weighted scorecard:
- Tenant experience — one tenant record per unit spanning applications, lease, renewals, communications, and maintenance. The operating posture is realty tenant record rollout.
- Predictive maintenance — plant and HVAC signals designed to open planned interventions before reactive emergencies — without inventing uptime guarantees.
- Occupancy and amenity optimization — common-area and amenity utilization as live signals for experience and staffing, not vanity occupancy theater.
- Building health — environmental sensing (temperature, humidity, air quality, leak detection) joined to access and equipment presence.
- Access and identity — every door a governed signal: grants, denials, and anomalies designed to land in the audit trail at the moment they happen.
- Portfolio coherence — multi-building topology without snowflake buildings; privacy and tenancy boundaries stay non-negotiable. Network learning itself is Franchise OS territory — Tell Business OS from Franchise OS.
Named-vendor battle cards stay internal. Public differentiation stays category-level.
Domain Steward — primary agent for the asset
Domain Steward is the named primary agent of the realty vertical. Mandate: tenant experience, predictive maintenance, occupancy and amenity optimization, and building health. Style: quietly vigilant, long-horizon, protective of both the asset and the resident and tenant experience. Signature question: what is the building telling us that humans have not yet noticed.
It is designed to live inside building loops (access anomaly, leak threshold, plant degradation, amenity crowding) alongside the property team — not as a monthly board pack. Shared teammates (Sentinel, Atlas, Nexus, Ledger, ForgeMaster) enrich risk, cost, skill, and learning; Domain Steward owns the realty-lane mandate.
Authority still sits on the shared floor: irreversible classes stay gated; brand scope fails closed; reconstructability lives in the audit trail. Counsel walks that story through Verify what an agent is allowed to do and governed agent boundaries.
Substrate docks Domain depends on
Domain is a specialized orchestration on the MCV substrate. Public docks you can open in a briefing:
- Mesh — the building as a Mesh node; access, sensors, and plant gateways on one interconnect fabric. Interconnect fabric is not data fabric.
- Synapse — real-time access, safety, and maintenance loops.
- Forge — outcomes that turn building experience into better playbooks and skills under governance.
- Pulse / Cortex / Aria complete the chain narratively; product docks for Mesh, Synapse, and Forge are the ones to name aloud first.
Composition of kits, agents, verticals, and Franchise OS is Name what the organism is made of.
Hardware and offline — access and safety first
The physical posture for one Domain property is Spec the hardware for a Domain property: edge core, access and identity, environmental sensing, privacy-zoned cameras, standardized kits — all reference configurations finalized per site survey. Access control and safety signaling are the highest-priority offline loops: local credentials and cached policy continue; critical safety and leak detection alert locally; events buffer with integrity; audited break-glass remains possible; ordered reconciliation on reconnect — no silent loss of access authority or critical environmental events. The careful public contract is Read the offline contract your locations run on.
How to use this leaf in a briefing
- Open the silo first: MCV.REALTY — Domain.
- Name Domain as vertical orchestrator on Business OS, not as a leasing-stack replacement alone.
- Hedge availability explicitly: staged rollout, designed to operate — not generally shipped.
- Walk Mesh → Synapse → Forge docks before any "smart building AI" demo.
- Push autonomy claims back to gates and evidence — never to NOI, occupancy, or other invented portfolio metrics.
- Separate location runtime from network learning (Business OS vs Franchise OS).
- Pair with the construction sibling when the portfolio spans sites: Brief Scaffold without mistaking it for a job-site app stack.
Non-goals for this leaf
- No NOI, occupancy, or margin percentages; no uptime guarantees or invented customer logos.
- No named-vendor battle cards or certification badge theater.
- No present-tense claim that every Domain kit path or sensing zone ships at equal maturity on day one.
When Domain is clear, continue composition via organism composition and counsel review via diligence resources.