PIN — Property Identification Number
How properties exist as first-class identities on Leja
What the PIN Is
Every physical property listed and verified on Leja receives a permanent Property Identification Number (PIN). It is the property’s identity — not the landlord’s identity, not the agent’s identity. The property itself has a record. The PIN is not a role. It is not a listing. It is the property. Format:PIN-NG-YYYY-XXXXXXXXXXX
Example: PIN-NG-2026-F2H6N4T8W3V
The PIN accumulates the full history of a property:
- Maintenance events (what was reported, who fixed it, how long it took)
- Tenancy history (how many tenancies, average duration — no tenant identities)
- Condition record (inspection outcomes over time)
- Dispute history (count and nature — no party identities)
- Availability status (real-time)
- Neighborhood trust score (aggregated from all Leja properties nearby)
Why the PIN Matters
Without a PIN, a buyer inspecting a property can only trust:- The agent’s description (potentially biased)
- The landlord’s claims (self-reported)
- Their own inspection (one-time, incomplete)
- How many maintenance issues have been reported (and resolved or not)
- How long previous tenancies lasted (stability signal)
- Whether the property condition consistently improved or declined
- Whether the neighborhood trust score is high or declining
- What the property’s current availability status is
The Three-Way Linkage Model
Every PIN is anchored to three identity nodes simultaneously:Node 1 — Property Owner (RIN)
The verified property owner’s personal RIN is the primary anchor. It is set at PIN issuance and updated if the property is sold. Every ownership transition creates a permanent ownership history node.Node 2 — Listing Agent (Personal RIN)
When an agent lists a property on Leja Professional, their personal RIN is attached to the PIN as the listing agent node. This is distinct from the owner node — the agent may not own the property.- Only one agent can hold the current listing node at a time
- When an agent withdraws a listing or the property is sold, their listing node becomes historical — the next listing agent creates a new current node
- The listing agent takes professional responsibility for the accuracy of what they enter on that listing
Node 3 — Listing Organisation (BRN, if applicable)
If the listing agent is employed by an organisation, the organisation’s BRN is also attached as a node alongside the agent’s personal RIN.Historical Listing Events — The Property’s Professional Record
Every time an agent lists, relists, sells, or withdraws a property, a permanentPropertyListingEvent is created on the PIN.
- Which agents have ever listed this property
- Which organisations have ever represented it
- Whether it has been listed and withdrawn repeatedly (red flag signal)
- Who sold it and when
- How many agents have handled it across its history
Real-Time Status
The PIN has a current availability status visible to all parties:What the PIN Accumulates
Public standard (visible to all Leja parties without login):- Verification tier (PROVISIONAL, COMMUNITY_VERIFIED, INSPECTED)
- Building age (banded: pre-2000, 2000–2010, 2010–2020, post-2020)
- Previous tenancy count (no tenant identities)
- Average tenancy duration
- Maintenance history (issue types and resolution times — no party names)
- Last inspection date and overall condition rating
- Utility connection status (electricity, water, waste — verified or claimed)
- Dispute history (count and category — no party identities)
- Rent band history (rising / stable / falling — not exact amounts)
- Known recurring issues log
- Neighborhood trust score
- Real-time availability status
- Number of distinct listing agents over the property’s history (banded)
- Exact previous rent amounts
- Detailed maintenance reports (job descriptions, outcomes)
- Exit inspection photos (anonymized — no tenant identities visible)
- Previous tenant identities
- Exact rent unless owner consents
- Landlord personal details beyond verification status
- Any service provider identity from maintenance jobs
- The agent’s commission or fee for the listing
PIN Issuance
Who can create a PIN: The verified property owner — directly, or via an agent acting on their behalf. If an agent initiates the PIN creation, the owner must explicitly confirm it. The PIN is issued linked to the owner’s personal RIN. Minimum owner requirement: The owner must have at least NIN_VERIFIED personal RIN before they can create a PIN. This is stricter than the old PHONE_VERIFIED minimum — property ownership claims require confirmed identity. NIN_VERIFIED is required for all property types (residential and commercial). At issuance, the system creates:- PIN at PROVISIONAL tier
- Ownership node linking PIN → owner’s personal RIN
- If agent initiated: listing agent node linking PIN → agent’s personal RIN (and BRN if org staff)
- TrendEvent on the owner’s RIN:
PROPERTY_LISTED - TrendEvent on the agent’s RIN:
PROPERTY_LISTING_CREATED(if agent initiated) - PropertyListingEvent record:
LISTED
Maintenance Leja Professional and the Bidirectional Connection
Every service job completed through Resident on a property automatically feeds that property’s maintenance history in Leja Professional. This means:- A landlord does not need to manually log maintenance events
- Every Resident-processed job creates a permanent record on the PIN
- The property’s witnessed maintenance history grows every time a plumber, electrician, or painter processes a job through Resident
PIN and Leja Stay
For a property to be listed on Leja Stay (short-let), it must have a PIN at minimum PROVISIONAL verification tier. The Leja Stay listing references the PIN. Every short-let booking creates a TrendEvent on the PIN. Every post-stay rating updates the PIN’s condition history. The property’s short-let reputation is part of its permanent record.PIN in the Trust Graph
The PIN is a first-class node in the Trust Graph. A tenancy transaction touches the PIN directly:- Tenant’s personal RIN (Track 1 event added)
- Owner’s personal RIN (owner behavior witnessed)
- Agent’s personal RIN (Professional Record updated, PropertyListingEvent updated)
- Org’s BRN (if applicable)
- PIN (tenancy count, duration, condition, maintenance all updated)
02_Trust_Architecture/02_trust_graph_lens_matrix.md.