Properties modules
| Short-Term | Critical | No occupancy links | No work links | Needs review | > | |
| Long-Term | Healthy | No occupancy links | No work links | Needs review | > | |
| Mid-Term | Needs attention | No occupancy links | No work links | Draft-only | > | |
| Mid-Term | Healthy | No occupancy links | No work links | Draft-only | > | |
| Long-Term | Critical | 1 occupancy link | 1 work link | Draft-only | > | |
| Long-Term | Needs attention | No occupancy links | No work links | Draft-only | > | |
| Short-Term | Healthy | No occupancy links | No work links | Needs review | > | |
| Short-Term | Needs attention | 1 occupancy link | 1 work link | Held until manager approval | > | |
| Short-Term | Needs attention | No occupancy links | No work links | Routine review | > | |
| Short-Term | Critical | No occupancy links | No work links | Draft-only | > | |
| Mid-Term | Healthy | 1 occupancy link | No work links | Draft-only | > | |
| Short-Term and Long-Term capable | Healthy | 1 occupancy link | No work links | Needs review | > | |
| Long-Term | Healthy | No occupancy links | No work links | Routine review | > | |
| Long-Term | Needs attention | 2 occupancy links | No work links | Needs review | > | |
| Mid-Term | Needs attention | No occupancy links | No work links | Needs review | > | |
| Short-Term | Healthy | No occupancy links | No work links | Draft-only | > | |
| Long-Term | Healthy | No occupancy links | No work links | Needs review | > | |
| Flexible | Healthy | No occupancy links | No work links | Needs review | > | |
| Long-Term | Needs attention | No occupancy links | No work links | Needs review | > | |
| Long-Term | Needs attention | No occupancy links | No work links | Routine review | > |
Property health table is rendered by PropertiesPortfolioClient.Properties record table remains the tactical list surface.Property health table replaces second command-center priority queue.Selected detail is now a row handoff, not a second dashboard panel.Property rows are the tactical entry points.Guardrails remain source-static and hidden from tactical review.Open selected property receiving detailOwner-safe summary remains internal review only; no publication or delivery.Review onlyAdmin / Fixture properties: 20 / Fixture occupancy links: 6 / Fixture work links: 2 / Private data: RedactedSingle-account synthetic preview only; no live tenant activity or external execution.Property review stays inside the local Manager/Admin corridor and remains no-live.Properties now opens with one compact filter bar, dense property health table, and detail row handoff.3 visible areas: Compact filter bar, Property health table, Detail handoff.Read-only properties review only; no edit, send, sync, payment, provider, or owner delivery action.Source-static Manager/Admin Properties MVP readiness registerReview existing no-live Properties route surfaces in operational order; this register is readiness copy only and not a workflow engine.Property operating records / Listing and channel mapping / Property knowledge blocksManager/Admin continuation from Command CenterProperties receives the property-scoped handoff after Command Center triage.Step 2 of 3 keeps the corridor in bounded Manager/Admin review.In the current dev-preview corridor, Properties is the property-scoped receiving surface between /command-center and /properties/[propertyId].This route narrows the review into one selected property detail receiving surface.Review context stays aligned with the Command Center handoff.This receiving surface reviews property evidence, owner-safe summaries, and the selected detail handoff before the corridor closes in property detail.Selected property detail is the explicit receiving surface and corridor endpoint for this slice after supervisory triage.Occupancy and channel status stay metadata-only and no-live.Next bounded internal review step is the selected property detail receiving surface.Primary property detail handoffHarbor Loft 2ASource-static property detail handoff only; no edit, sync, provider, payment, auth, message, storage, or deployment action.Read-only property review only; no edit, send, sync, payment, or provider action.Additional bounded property detail receiving surfaces remain available from the same supervisory handoff.Each detail route remains a read-only receiving surface with the same no-live property boundary.The receiving surface stays source-static, review-only, and ready for later no-live local UI validation only.Synthetic property records only / No real addresses / No private owner, resident, guest, vendor, or cleaner contact data / No real access codes / No live channel connection / No source-system private records / Every record maps to account/workspace before property, unit, listing, lease, reservation, work, or money context / Owner and Field views receive only approved role-safe summariesProperty records, listing and channel mappings, knowledge blocks, rules, and role-safe summaries.