Skip to content

Community Module: Inventory & Gap Analysis

Date: 2026-01-29 Domain: Community (The Trinity)

1. Executive Summary

Status: Backend is Robust / Frontend is Fragmented. The Core Engine (packages/modules/community) is fully formed, covering Identity, Property, and Governance. The User Interface (apps/platform) is scattered across multiple root directories, lacking a unified "Community" experience.

2. The Inventory (As-Built)

A. The Engine (Backend)

  • Location: packages/modules/community/src
  • Maturity: High (Rich Service Layer).
  • Components:
  • contracts/: Deed & Lease Services.
  • assessments/: Assessment Service.
  • occupancy/: Occupancy Service.
  • registry/: Profile, Google Workspace, Watchlist services.
  • governance/: Voting logic.
  • property/: Asset Service.

B. The Interface (Frontend)

The "Trinity" (Identity, Property, Governance) is split across disparate routes:

Route Likely Role Purpose Status
(app)/community/gov-dash-view Resident View active votes, meeting dates. ⚠️ Isolated
(app)/gov-board-hub Board Member Manage proposals, view quorum. ⚠️ Root Level
(app)/prop-master-reg Manager Master Registry of all units. ⚠️ Root Level
(app)/id-dir-search All Directory Search. ⚠️ Root Level
(app)/id-me-manage Self Profile Management. ⚠️ Root Level

3. The Gap Analysis (Vision vs Reality)

GAP 1: The "Scattered Trinity"

The Architecture (BLP-DOM-000_DOMAIN_ATLAS.md) states that Community is the union of Directory, Property, and Governance. The Reality is that these are treated as independent, root-level apps (prop-master-reg, gov-board-hub).

  • Consequence: No sense of "Place". A resident doesn't feel like they are "in the Community module"; they are just visiting isolated utility pages.

GAP 2: Naming Convention Drift

We have a mix of:

  • Capability-Based: gov-dash-view (Good).
  • Role-Based: gov-board-hub (Ambiguous - is it a hub or a dashboard?).
  • Legacy?: prop-master-reg (Feels like a database admin tool name).

GAP 3: The Missing Hub

There is no page.tsx at (app)/community that aggregates these flows.

  • If I click "Community", where do I go? currently, likely 404 or empty.

4. Proposed Questions for Vision Alignment

  1. The Split: Is the separation of gov-dash-view (Resident) and gov-board-hub (Board) intentional? (i.e., discrete Apps vs Roles in one App?)
  2. The Consolidation: Should we move prop-master-reg and gov-board-hub inside /community to reflect the Domain Atlas?
    • Correction: /community/com-prop-master
    • Correction: /community/com-gov-board