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

Feature Package PK-09 — Resident Services & Access

Status: Package Specification
Domain: Resident Experience / Access / Concierge
Maps to: Playbook (resident services lifecycle)
External integration: Access control, Keycloak (identity), Synapse (resident comms)


1. What This Package Does

Gives the concierge and security team one system for resident and visitor management — issuing access rights, visitor passes, key cards, and managing resident communications — replacing paper visitor logs, uncoordinated key-card issuance, and fragmented resident messaging.

2. Features & Functionality

FeatureWhat it doesWho uses itWhat stands behind it
Resident access rightsAccess granted per unit (lobby, lifts, own floor, amenities) based on ownership/tenancyConcierge, securitytruth_edge:access (person→unit→access); PK-02/PK-05 edges
Key card / credentialPhysical or digital credential issued; linked to access edge; revocableConcierge, residentintegration_entity (system: "access-control"); card number
Visitor managementVisitor pre-approved by resident; visitor pass issued with time limit; entry loggedResident, security, conciergeVisitor claim linked to host unit; time-bounded access edge
Service-provider accessContractor, cleaner, delivery person issued scoped access for specific dates/areasSecurity, facilitiesScoped truth_edge:access with valid-from/to; contractor record
Resident directoryVerified resident directory (opt-in) for community contactResidents, conciergecns://truth/node/person; consent flag on claim
Announcements & alertsDevelopment-wide or per-block notices (maintenance, emergencies) sent via resident channelsProperty manager, HOASynapse discussion rooms; NATS stream
Emergency accessBreak-glass access for emergencies (fire, medical) with auto-auditSecurity, emergency servicesfn::security::elevate_trust; PoCE record of elevation

3. Workflow (Visitor Pass)

  1. Resident pre-approves visitor (name, ID, date/time, host unit) → visitor claim
  2. Security verifies resident is owner/tenant of host unit (PK-02/PK-05 edge check)
  3. Visitor pass issued → time-bounded access edge (lobby + host floor, specific window)
  4. Visitor checks in at security → pass activated; entry logged
  5. Pass expires automatically at end of window; access edge released
  6. PoCE receipt records approval, issue, entry, expiry

4. Guard Rails

  • No access right without verified ownership/tenancy edge
  • No visitor pass without host sponsorship
  • Access edges are time-bounded and auto-expire
  • No anonymous or unverified access grants
  • Emergency access elevated with PoCE audit trail
  • If access control is unavailable → fail closed; no fake credentials

5. Evidence & Audit

  • Access edges, visitor claims, credential records (access-control mirror), entry logs, emergency-access elevations, PoCE receipts