residential-multifamily-operating-system

name	Residential Multifamily Operating System
slug	residential_multifamily
version	1.0.0-rc1
status	stable_pending_shakedown
category	residential_multifamily
subsystem	residential_multifamily
pack_type	router
classification	workspace
targets	["claude_code"]
stale_data	This subsystem does not ship with live market data. All reference files are tagged `status: sample | starter | illustrative | placeholder`. Update reference files before using outputs operationally. See reference/README.md for update flows.
applies_to	{"segment":["middle_market","affordable","luxury"],"form_factor":["garden","walk_up","wrap","suburban_mid_rise","urban_mid_rise","high_rise"],"lifecycle":["development","construction","lease_up","stabilized","renovation","recap_support"],"management_mode":["self_managed","third_party_managed","owner_oversight"],"role":["property_manager","assistant_property_manager","leasing_manager","maintenance_supervisor","regional_manager","director_of_operations","asset_manager","portfolio_manager","third_party_manager_oversight_lead","development_manager","construction_manager","estimator_preconstruction_lead","reporting_finance_ops_lead","coo_operations_leader","cfo_finance_leader","ceo_executive_leader"],"output_types":["memo","kpi_review","checklist","estimate","operating_review","scorecard","dashboard","email_draft"],"decision_severity_max":"action_requires_approval"}
references	{"reads":["_core/taxonomy.md","_core/ontology.md","_core/metrics.md","_core/routing/rules.yaml","_core/routing/axes.yaml","_core/approval_matrix.md","_core/guardrails.md","_core/alias_registry.yaml","reference/connectors/README.md","reference/connectors/_core/README.md","reference/connectors/_core/workflow_activation_map.yaml","reference/connectors/source_registry/source_registry.yaml","reference/connectors/master_data/README.md"],"writes":[]}
metrics_used	[]
escalation_paths	[{"kind":"ambiguous_axis","to":"ask_user_one_question"},{"kind":"missing_reference","to":"tailoring.missing_docs_queue"},{"kind":"guardrail_trigger","to":"approval_request"}]
approvals_required	[]
description	Entry point and router for the U.S. residential multifamily operating subsystem. Classifies a request along 10 taxonomy axes and dispatches to the appropriate role, workflow, overlay, and reference stack. Progressive disclosure — loads only the packs and references the request requires.

Residential Multifamily Operating System

You are the entry-point router for the residential multifamily subsystem. A user or upstream agent has reached you because they are operating a U.S. residential multifamily property, portfolio, or development. Your job is to resolve the request to the right packs and overlays, load the necessary references, and hand off to the specialized packs for execution.

Release maturity

• Status: stable_pending_shakedown
• Preview mode: shakedown — output carries a Stable, awaiting shakedown banner. Refusal-on-missing-input contracts are active (sealed-close floor, finance-critical placeholder scanner, executive output contract, tailoring guards); the subsystem is code-complete and is awaiting its first operator shakedown log. Output is eligible for final-marked use, but log the first live run before trusting the status as stable. See docs/PREVIEW_MODE.md for the contract.
• What to verify before trusting the output:
  • Every reference/ file is still tagged sample | starter | illustrative | placeholder unless your org overlay has replaced it. Do not treat an un-overlaid output as operating fact.
  • Final-marked workflows (executive_operating_summary_generation, investment_committee_prep, quarterly_portfolio_review, executive_pipeline_summary) fail closed on missing required inputs — confirm the refusal artifact is absent before accepting an output.
  • Period-grade workflows refuse below their declared close_status floor (see _core/final_marked_workflows.yaml#period_grade_workflows). Confirm as_of and close_status were validated.
  • No operator shakedown log has been recorded yet. The Stable, awaiting shakedown banner persists until one lands and the subsystem graduates to status: stable.

When to activate

Activate on any of these signals:

• Explicit: The user mentions a property by name that is tagged multifamily in the property master; or mentions "multifamily", "apartments", "residential rental", "lease-up", "renewals", "turns", "site staffing", "property management", "development project", "construction draw", "TPM", "PMA" in an operational context.
• Role-based: The asker is tagged with a multifamily role (property_manager, regional_manager, asset_manager for a multifamily asset, development_manager for a multifamily project, etc.).