# Property Management controlled-pilot readiness

This readiness note summarizes the current app-pack analysis for the Housing Cooperative Operations / Property Management solution page.

## Required modules

The controlled pilot should be installed with these baseline modules because the pack routes and type definitions depend on existing platform capabilities rather than new custom controllers:

- **CRM** for residents, owners, tenants, suppliers, and board-member directories.
- **Store** for property, building, unit, parking, utility, common-area, marker, meter, and service-point registries.
- **Documents** for permits, certificates, meter photos, maintenance evidence, supplier invoices, board resolutions, insurance claims, and audit evidence.
- **Calendar** for inspections, renewals, board meetings, maintenance appointments, and reminder-driven follow-up.
- **BPM** for move lifecycle, maintenance, inspection, supplier invoice approval, meter reading, and governance workflows.
- **Ticket** and **Task** for resident requests, maintenance work orders, owner assignment, SLA follow-up, and escalation queues.
- **Communication** for resident, supplier, and board handoffs that remain human-reviewed.
- **Risk** for compliance, arrears, insurance, safety, and operational exception signals.
- **Organisation** for cooperative structure, board roles, committees, buildings, and responsibility assignment.
- **KPI** for dashboard, annual report, queue health, SLA, compliance, and arrears metrics.

## Optional modules

- **Finance** is optional and should be enabled only when the operator is ready to expose fee schedules, billing periods, invoices or charges, arrears queues, delinquency buckets, and payment monitoring. Finance routes must remain hidden or disabled when the Finance module is not installed.

## Core / installer requirements

The pack is suitable as a controlled pilot, but broader rollout needs core support for:

1. `optionalModules` and route-level `requiredModules` gates.
2. Disabled menu items with visible missing-capability reasons.
3. Generic pack route rendering for `/app/property-management/...` dashboard, queue, report, and debug views.
4. Idempotent type-definition installation keyed by `object_kind`, `definition_code`, and `source_pack_code`.
5. Dry-run validation for JSON parsing, route references, type route coverage, duplicate paths, custom renderer requirements, optional module gates, and non-destructive install behavior.

## Safe first workflows

Recommended first workflows for a guided pilot:

1. Resident or owner onboarding / move lifecycle.
2. Maintenance work order with supplier handoff and evidence capture.
3. Fee and arrears review with human approval when Finance is installed.
4. Inspection, permit, or certificate renewal queue.
5. Board resolution workflow with audit trail and annual-report output.

## Boundaries

The solution remains a controlled pilot. It does not perform autonomous payment capture, accounting posting, statutory reporting, resident cost allocation, supplier ordering, official communication sending, or regulated decisions without human review.