JJijibora
Docs & Product Guide
On this page (7 sections)

Appendix C — Real Estate Implementation Roadmap

Status: Planning
Sources: A-01 — Jijibora Deployment (Administrator Operations), A-04 — Starter Packs for Administrators, D-07 — Starter Bundles for Developers, Appendix C — Hotel Implementation Roadmap


1. Phase 0 — Foundations (Weeks 0–2)

  • Deploy Sovereign OS core strata (SurrealDB :8000, NATS :4222, Camel :8181, Kestra :8180, Agent BFF :3030, Truth BFF :3031)
  • Deploy canonical primitives: claim, truth_node, truth_edge, resource, resource_edge, integration_entity (s356)
  • Deploy APF (s230), PoCE (s131-s150), federation (s184), community governance (s165-s166), compliance gates (s350)
  • Deploy integration dependencies (ERPNext, OpenMAINT :8080, Synapse :8008, Keycloak :8081, MinIO :9000, Gotenberg :3094, Solver Gateway :3070, access control)
  • Seed base NATS KV lookups (SOVEREIGN_LOOKUPS)

Exit: Health checks green; no schema changes beyond canonical strata.


2. Phase 1 — Pilot Development (Weeks 3–8)

Starter packs: Sales Office (PK-01, PK-02) + Finance Desk (PK-07), Soft mode.

  • Register real-estate CNS types (cns://claim/type/real-estate/*)
  • Declare real-estate NATS KV lookups (rates, thresholds, SoD, checklists, SLAs)
  • Wire CRM → sale agreements; ERPNext → invoices; land registry → title mirrors
  • Service charges issued per unit; collections tracked; three-way match
  • Live gate ritual: move Sales Office + Finance Desk packs to LIVE

Exit: Pilot development running live on unit sales, title records, service-charge issuance and collection; auditors can verify PoCE receipts.


3. Phase 2 — Full Development (Weeks 9–16)

Add: Maintenance Desk (PK-04, PK-08) + Leasing Desk (PK-05), LIVE.

  • Common-area defects → OpenMAINT work orders → contractor dispatch → expert sign-off
  • Snagging inspections → handover gate → unit READY_FOR_HANDOVER
  • Leases → rent collection → deposits → renewals → move-out
  • Solver-gateway: vendor selection across developments (procurement.basket_split@1)

Exit: Full development operations on Sovereign OS; ERPNext three-way match live; OpenMAINT WOs synced; solver proposals reviewed by humans.


4. Phase 3 — Community & Resident Services (Weeks 17–24)

Add: HOA Governance (PK-03) + Amenities (PK-06) + Resident Services (PK-09), LIVE.

  • HOA rules, resolutions, BBS+ voting, AGMs, elections
  • Amenity time-slot booking; resident-verified
  • Access rights, visitor passes, key cards
  • Scope governance & delegation (s142): developer → HOA board → committees

Exit: Development operating cross-function sales, finance, maintenance, leasing, governance, amenities, access; delegation chains auditable.


5. Phase 4 — Scale & Multi-Development (Month 7+)

  • Resale & secondary market (PK-10) live
  • Multi-development federation: bulk procurement across developments; shared vendors
  • Additional phases/towers onboarded as new scopes
  • Compliance gates live: building safety, fire, accessibility
  • Dashboards from live data only (no hardcoded metrics)

6. Success Metrics (Live Data Only)

All metrics computed from live backend API responses / SurrealDB queries — never hardcoded:

  • Units sold via PoCE (count, from claim table)
  • Service charges collected vs. issued (from compliance_gate_eval / charge claims)
  • Defects closed with expert sign-off (count, from PoCE steps)
  • Leases active and renewals processed (from claim table)
  • Amenity bookings confirmed (from amenity-booking claims)
  • HOA resolutions adopted and votes cast (from resolution/vote claims)

Honesty rule: If a metric is not yet computed, the dashboard renders an honest empty state or skeleton — never a synthetic number.


7. What to Confirm with the Developer / HOA (Pilot Kickoff)

  • Which 3–5 functions to solve first (sales? service charge? defects? HOA governance?)
  • Which sales, finance, and facilities leads will be named approvers
  • Which resident/owner languages and contact channels receive notices and updates
  • Which personal details stay out of receipts and dashboards; emergency access TTL
  • Service promises: max defect resolution time, max maintenance response time, service-charge collection cadence (which phases may choose faster)