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

Real Estate Development Targeting — Sovereign OS for Large Residential Complexes

Status: Document Set Index
Target Vertical: Real Estate Development — large complexes, master-planned communities, apartment buildings, villa estates, retirement/lifestyle estates
Substrate: Sovereign OS / Community Weave Platform
Version: 1.0.0 | Date: 2026-11-09

Purpose

This document set describes how the Sovereign OS / Community Weave Platform infrastructure can target real estate developments — particularly large residential complexes with homes, apartments, villas, shared amenities, and homeowners associations. It is compiled entirely from existing work in the repository — playbooks, processes, integrations, architecture mandates, and canonical primitives — with zero bespoke tables, zero schema changes, and zero synthetic fallbacks.

Real estate developments are Jijibora's native target market (master-planned developments, retirement estates, golf/lifestyle communities, bedroom/commuter estates). The hotel document set (docs/hospitality/) is complementary: hotels manage guests and short stays; real estate developments manage owners, residents, tenants, units, common areas, and long-term community governance.

Document Set

#DocumentAudienceWhat it covers
00EXECUTIVE-SUMMARYLeadership, salesWhy real estate developments are a prime target; value proposition; positioning
01ARCHITECTURE-MAPPINGArchitects, CTOsReal estate operations → canonical primitives; unit/lease/owner model; honesty limits
02FEATURE-PACKAGESProduct, ops leadsPackage overview, matrix, cross-cutting capabilities
03PROCESSES-AND-WORKFLOWSOperations managersProcess families mapped to real estate functions
10–19[PACKAGE-*](10-PACKAGE-SALES-OFF-PLAN.md …)Package ownersDetailed specs per domain: sales, units, HOA, maintenance, leasing, amenities, finance, construction, resident services, security
STAKEHOLDER-*[STAKEHOLDER-*](STAKEHOLDER-01-DEVELOPER-OWNER.md …)Non-technical rolesPlain-language guides for developer, HOA board, property manager, resident, tenant, vendor
JIJIBORA-TIE-INJIJIBORA-TIE-INProduct, platformHow real estate reuses Jijibora building/reflex/community infrastructure
A–CAppendicesImplementersCNS types, NATS KV lookups, roadmap

Real Estate vs. Hotels — Complementary Positioning

DimensionHotels (companion set)Real Estate Developments (this set)
Primary relationshipGuest — short stayOwner / resident / tenant — long-term
Core assetRoom / function spaceUnit (apartment, villa, home) + common area
Revenue modelRoom rate, F&B, eventsSale price, service charge, rent, fees
GovernanceHotel operator decidesHOA board + developer + residents
LifecycleDays to weeksYears to decades
Key documentFolio / reservationSale agreement / lease / title link
Jijibora fitSecondary (managed building)Primary (master-planned community)

Core Architectural Mandates (Applied Throughout)

  1. Zero bespoke tables — all real estate entities map to claim, truth_node, truth_edge, resource, resource_edge, integration_entity. No unit_sale, hoa_vote, service_charge, snagging_defect tables.
  2. Declarative-first — business logic is config/lookup in NATS JetStream KV (SOVEREIGN_SCENARIOS, SOVEREIGN_LOOKUPS, SOVEREIGN_TEMPLATES), never filesystem reads at runtime.
  3. Fail closed — if an external peer (ERPNext, payments, access control) is unavailable, the platform returns 502/503 with a typed error. No synthetic OPTIMAL, no dummy IDs.
  4. Zero synthetic adapter payloads — no dummy coordinates, dummy owners, hardcoded org IDs, or fake routes.
  5. Machines propose, rules dispose — sourcing/solving suggest; a named approver confirms via PoCE.
  6. No hardcoded metrics — dashboards render live data or honest skeleton/empty states; no fake occupancy or service-charge collection rates.
  7. PoCE audit — every critical state transition produces a cryptographically verifiable receipt.