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

Feature Package PK-03 — HOA & Community Governance

Status: Package Specification
Domain: Governance / HOA / Residents
Maps to: Playbook (community governance), Process 4 (Meeting Notes & Decision Records)
External integration: Synapse (resident discussions), Keycloak (voter identity)


1. What This Package Does

Gives the HOA board and residents one auditable system for community governance — proposing rules, voting on resolutions, holding AGMs, enforcing violations, and electing board members — replacing proxy forms, paper ballots, and unrecorded decisions.

2. Features & Functionality

FeatureWhat it doesWho uses itWhat stands behind it
Community rulesHOA rules registered as governance claims with scope and enforcement stageHOA board, residentscns://claim/type/governance/resolution; s165 scope governance
Resolution proposalAny eligible owner proposes a resolution; discussion period before voteHOA board, ownerscns://claim/type/governance/resolution; Synapse discussion room
Voting (BBS+)Owners vote on resolutions using BBS+ selective disclosure — proves eligibility without revealing how they votedOwners, HOA secretarycns://claim/type/governance/vote; BBS+ credential (s121-s123)
AGM / meetingsMeeting notices, minutes, action items recorded; decisions promoted to resolutionsHOA secretary, boardcns://knowledge/meeting_note; fn::poce::record_step
ElectionsBoard member elections with candidate nominations, ballots, tallyResidents, election committees166 election functions (fn::election::create, nominate, cast_ballot, tally)
Rule enforcementViolations logged (e.g., noise, parking, pet rules); fines proposed (not auto-issued)HOA board, property managercns://claim/type/governance/rule-violation; human approval gate

3. Workflow (Resolution Lifecycle)

  1. Owner submits resolution proposal → claim created; discussion opens in Synapse room
  2. Discussion period elapses; proposal moves to vote stage
  3. Eligible owners verified via ownership edges (PK-02); voting opens
  4. Owners cast BBS+ votes; results tallied; threshold checked (e.g., 50% + 1)
  5. If passed → resolution claim marked ADOPTED; enforcement stage scheduled
  6. PoCE receipt records proposal, voters, choices, threshold, outcome

4. Guard Rails

  • No vote without verified ownership (voting rights tied to unit share)
  • No auto-enforcement of rules; violations require human review and approval
  • BBS+ selective disclosure: eligibility proven without revealing vote choice
  • No auto-issued fines; human approval required at each stage
  • s142 scope governance: delegation chains (board → committees) bounded and auditable

5. Evidence & Audit

  • Resolution claims, vote claims with BBS+ proofs, meeting minutes, election results, violation records, PoCE receipts