Feature Package PK-01 — Sales & Off-Plan
Status: Package Specification
Domain: Sales / Marketing / Legal
Maps to: Playbook (unit sale lifecycle)
External integration: CRM, ERPNext (invoice), land registry mirror
1. What This Package Does
Gives a development's sales team one auditable system for off-plan and resale unit sales — from reservation through sale agreement, payment schedule tracking, and handover — replacing spreadsheets, paper reservation forms, and uncoordinated legal files.
2. Features & Functionality
| Feature | What it does | Who uses it | What stands behind it |
|---|---|---|---|
| Unit reservation | Prospective buyer reserves a unit for a holding period; time-bounded lease prevents double-reservation | Sales agent, buyer | cns://claim/type/real-estate/sale with reserved trait; truth_edge buyer→unit lease |
| Sale agreement | Reservation converts to a sale agreement with price, payment schedule, handover date; signatures recorded | Sales manager, legal, buyer | cns://claim/type/real-estate/sale with sale_confirmed trait; PoCE session |
| Payment schedule tracking | Milestone payments (booking, 10%, 20%, handover) tracked against the agreement; each payment linked to invoice | Finance, sales | Claim traits per payment milestone; ERPNext invoice mirror |
| Handover readiness | Unit must pass snagging (PK-08) and service-charge setup (PK-07) before handover is released | Project manager, legal | Cross-package gate; fn::poce::finalize_session |
| Buyer identity | Buyer identity anchored to Keycloak; optional BBS+ selective disclosure for age/nationality | Sales, legal | cns://truth/node/person; Keycloak DID |
| Land registry mirror | Title reference recorded in integration_entity; title transfer tracked post-handover | Legal, registrar | integration_entity (system: "land-registry") |
3. Workflow (Step by Step)
- Buyer selects unit → reservation claim created; unit lease bound for holding period
- Sale agreement drafted (price, payment schedule, handover date) → legal review
- Buyer signs →
fn::poce::record_step(signature evidence) - First payment → ERPNext invoice mirror; payment reference recorded
- Milestone payments tracked as they arrive; each linked to agreement claim
- Handover: unit passes snagging (PK-08) and service charge account opened (PK-07)
- Title transferred; land registry mirror updated; PoCE receipt issued for the sale
4. Guard Rails
- No double-reservation of a unit (lease conflict check)
- No sale agreement without buyer identity verification
- No handover without snag clearance and service-charge account
- Land registry owns title law; Sovereign owns operational sale state and audit
- If ERPNext is unavailable →
502fail-closed; no dummy invoice numbers
5. Evidence & Audit
- Reservation claim, sale agreement, signatures, payment records, ERPNext invoice refs, land registry mirror, PoCE receipt