Skip to main content

​
Communication Surface — Overview

​
What the Communication Surface Is

Communication in Leja is never general chat. Every message, review, and feedback event in Leja is:
  • Contextual (linked to a specific professional event, charge, property, or job)
  • Timestamped and attributed (permanent record)
  • Where appropriate: a TrendEvent (feeds Trust Graphs)
The key distinction from informal chat: A formal notice served through Leja has institutional standing. An off-platform message about the same topic does not. Leja does not replace everyday chat. Leja is the institutional layer that makes certain communications provable, timestamped, and permanent. Agents will continue to use private channels for casual coordination. Leja captures the events that matter legally and reputationally. The AI drafts. The agent sends. Leja witnesses. Leja never sends messages on behalf of agents.

​
Feature 1: P2P Contextual Messaging Threads

​
Agent ↔ Resident Thread

Milestone Wave: 2 Surfaces linked: Professional + Resident A contextual messaging thread exists per active occupancy. Messages in this thread are linked to specific professional events (a charge, a TrendEvent, a maintenance request). Witnessed communication types:
  • Payment reminder (AI-drafted by Dimension D, agent sends)
  • Formal notice (eviction, rent review, deposit return notice)
  • Maintenance acknowledgment
  • Exit coordination
A formal notice served through Leja:
  • Creates a timestamped, attributed record
  • Cannot be denied by either party
  • Is legally stronger than off-platform proof
  • Feeds the occupancy chapter in both parties’ Trust Graphs

​
Agent ↔ Space Seeker Thread

Milestone Wave: 3 Surfaces linked: Professional + Resident Pre-occupancy thread opened at viewing request submission. Application status updates sent through thread. Agent response time witnessed → feeds agent’s professional Trust Graph (visible to Principals comparing agents). Communication gap between inquiry and response = Track 3 signal for both parties’ Trust Graphs.

​
Guest ↔ Hotel / Short-let Host Thread

Milestone Wave: 3 Surfaces linked: Space + Resident Hotel/host response time and communication quality witnessed → feeds Hotel BRN or personal host Trust Graph. Pre-arrival queries, check-in instructions, post-stay resolution — all timestamped. Hotel communication gap before arrival = negative TrendEvent for the hotel.

​
Service Provider ↔ Requester Thread

Milestone Wave: 3 Surfaces linked: Resident (Track 2) Thread opened at job acceptance (not before — address is private until mutual acceptance). Key function: scope of work agreed in-thread before work begins. Having the agreed scope on record is Leja’s primary mechanism for scope dispute prevention. Provider cannot ghost after scope is formally agreed in-thread.

​
Feature 2: Intelligence Chat Interfaces

​
Professional Operator Intelligence Chat (Leja Professional)

Milestone Wave: 2 — Business + Scale tier only AI Dimension: D Roles: Managing Director, Org Agent, Principal Natural language portfolio queries and actions:
  • “Which residents are 3+ months overdue?”
  • “Draft a notice for Unit 4B regarding their outstanding balance”
  • “What is the occupancy rate across my Lekki properties?”
  • “Flag any tenancies ending in the next 60 days”
This is portfolio-specific intelligence — not general chat. Every query is interpreted against the agent’s actual verified verified record data. AI Dimension D. Business + Scale tier.

​
Resident Advocate Chat (Resident)

Milestone Wave: 3 — Resident Pro tier AI Dimension: C Roles: Resident, Space Seeker, Service Provider, Guest Full natural language in Nigerian English:
  • “Find me a 2-bedroom in Yaba under ₦800k with good maintenance history”
  • “What is my Trust Fingerprint doing and how do I improve it?”
  • “Help me draft my application to this property”
  • “Find a trusted electrician in Ikeja with 3+ years on Leja”
  • “Is this asking price fair for Lekki Milestone Wave 1?”
AI Dimension C (Resident Advocate). Reads Dimension A trajectory signals in real time. Resident Pro tier.

​
Feature 3: Witnessed Reviews and Feedback

​
Post-Occupancy Review (Both-Sided)

Milestone Wave: 2 Status: Active Leja feature area. Extend this section as the canonical spec. Surfaces linked: Professional + Resident After every tenancy exit, both parties review each other. Principal reviews Resident:
  • Exit condition (property returned in good state?)
  • Behavior (respectful of rules, communicated well?)
  • Notice compliance (gave required notice period?)
Resident reviews Principal:
  • Deposit return (returned in full? on time?)
  • Maintenance responsiveness (issues addressed during occupancy?)
  • Communication quality (professional? available?)
Rules:
  • Both reviews are immutable after 48 hours — no gaming
  • Extreme negative review without any prior logged dispute during the tenancy is automatically flagged as suspicious (possible retaliatory review)
  • Both reviews feed respective Trust Graphs permanently
  • One-sided review (one party refuses) still creates a partial TrendEvent for the non-reviewing party — their silence is noted

​
Hotel / Leja Stay Guest Review

Milestone Wave: 3 Surfaces linked: Space + Resident Guest submits witnessed review post-checkout:
  • Photo evidence optionally attached (damage record, positive record)
  • Review feeds Hotel BRN Trust Graph + Room PIN simultaneously
  • Hotel/host response to review is visible to future guests
  • AI summarizes review themes across stays (aggregate insight)
  • Immutable after 48 hours

​
Service Provider Review (Both-Sided)

Milestone Wave: 3 Status: Active Leja feature area. Extend this section as the canonical spec. Surfaces linked: Resident (Track 2) Both provider and requester review each other post-job.
  • Immutable after 48 hours
  • Provider reviews requester: payment timeliness, communication, clear scope description, showed up for scheduled work
  • Requester reviews provider: quality, professionalism, timeliness, completion rate
  • Both feed respective Trust Graphs
  • Repeat booking of the same provider = strongest trust signal on platform

​
TrendEvent Types Created by Communication Surface

The following TrendEvent types are created by the Communication surface and need to be added to the TrendEvent enum: 
FORMAL_NOTICE_SERVED        // Agent serves formal notice through Leja thread
NOTICE_ACKNOWLEDGED         // Recipient acknowledges notice in-thread
RESPONSE_TIME_FAST          // Agent/hotel responded within 2 hours (positive)
RESPONSE_TIME_SLOW          // Agent/hotel responded after 48+ hours (negative)
RESPONSE_NO_SHOW            // No response to formal inquiry (negative)
REVIEW_SUBMITTED_POSITIVE   // Post-occupancy/job/stay positive review
REVIEW_SUBMITTED_NEUTRAL    // Post-occupancy/job/stay neutral review
REVIEW_SUBMITTED_NEGATIVE   // Post-occupancy/job/stay negative review
REVIEW_FLAGGED_SUSPICIOUS   // Extreme negative without prior dispute history
SCOPE_AGREED_IN_THREAD      // Provider/requester agree job scope in-thread

​
Spec Requirements Before Build

  1. Thread data model — how messages link to TrendEvents and professional events
  2. What constitutes a “formal notice” (creates TrendEvent) vs casual communication (does not create TrendEvent) — clear criteria
  3. Read receipts and acknowledgment model
  4. 48-hour review lock implementation
  5. Suspicious review detection algorithm (what triggers the flag)
  6. AI draft generation pipeline for agent-side reminders
  7. Intelligence chat query → verified-record query translation (Professional operator intelligence chat)
  8. Response time measurement and TrendEvent creation threshold rules