Real Estate OS
The portfolio is recorded in six places and understood in none.
- Property management
- Assets, units, occupancy
- Lease systems
- Tenants, terms, escalations, expiries
- Accounting
- Income, expense, NOI
- Market data
- Comps, rents, cap rates
- Building systems
- Sensors, tickets, maintenance
- Underwriting models
- Assumptions, IRR, exit scenarios
Plate data
- Industry
- Real estate
- Status
- Reference architecture
- Agents
- 05
- Layers
- 07
The architecture applied, published in full, ready to be built on.
Four questions those systems cannot answer.
- Why is NOI declining in this asset?
- Which leases will not renew next year?
- Which assets should we acquire this quarter?
- Which system carries the action, and who signs the commitment?
The industry, in miniature.
Asset, unit, lease, tenant, market, comp, cap rate, capital plan, work order, covenant.
Ontology fragment · real estate
ENTITY asset
RELATIONSHIP lease -> held_by -> tenant
EVENT lease_expiry
METRIC noi
RULE investment_committee_threshold (enforcement: approval)
DECISION acquisition_shortlist
ACTION underwriting_model_updateEach one introduced by the question it answers.
Acquisition
Which assets should we acquire this quarter, against our mandate?
Asset management
Why is NOI declining in Tower B, and what recovers it?
Leasing
Which tenants should we target for these three floors?
Facility
Which equipment failures are likely in the next 30 days?
Investment committee
What happens to IRR if occupancy falls 7 percent and the exit cap expands 50 basis points?
Five agents, one Industry OS. The investment committee agent exists to argue with the other four.
What the Industry Pack contains.
- Ontology
- Assets, leases and market structure.
- Reference workflows
- Underwriting, renewal, capital planning and preventive maintenance.
- Agent templates
- Five agents with committee thresholds pre declared.
- Connectors
- Property management, lease, accounting, market data and building systems.
- Evaluations
- Built from historical underwriting decisions.
Financial boundaries rather than regulatory ones.
The pattern is the same: declared per agent, enforced by the runtime.
requires_human_approval: capital_commitments lease_terms_offered valuation_assumptions tenant_communicationsRead next.
- Pharma OS
- The one with a product behind it. Same band order, plus deployment.
- Healthcare OS
- The same seven bands, applied to a different industry.
- Manufacturing OS
- The same seven bands, applied to a different industry.
- Financial Services OS
- The same seven bands, applied to a different industry.
- The Super Brain spec
- The twelve required services and the three conformance levels.
- Industry Ontology Schema
- How the ontology fragment on this page is declared.
One architecture. Twenty pages. Same document.
This is the architecture applied, not a product yet.
Published in full and ready to be built on. If you run a portfolio and want to see this against it, start with a conversation.
A conversation, not a demo script. We ask what your systems of record are, what they cannot answer, and which decisions actually matter. If an Industry OS is not the right answer for you, we will say so.