Leja Presence — Professional PR Surface
What Leja Presence Is
Leja Presence is the market-facing identity layer within Leja Ops. It is not a separate product, not a social network, and not a content marketing tool. It is the professional’s witnessed record expressed outward — shaped by AI, steered by the professional, and delivered to three distinct audience tiers. The one-sentence position: A fully fledged PR company running inside Leja Professional — not typical PR, but market exposure built entirely from witnessed records.What It Is Not
- Not a standalone app or separate product
- Not self-reported marketing (everything traces to a witnessed record)
- Not what residents see in the marketplace — it goes significantly beyond the transactional marketplace layer
- Not a generic social media or content publishing tool
Architecture Decision (Locked)
Approach: AI-curated story moments + professional publishing amplifier Two layers:- Passive floor — Leja’s AI reads the professional’s Trust Graph continuously and surfaces “story moments” — milestone achievements, portfolio highlights, performance trends, record-backed credibility signals. These are always authentic because they originate from witnessed events, never from self-reported content.
- Active amplifier — The professional has a publishing layer inside Leja Ops to approve, annotate, expand, and amplify these story moments to each audience tier. They can also publish active content (deal announcements, service showcases, campaign targeting) on top of the AI-generated floor.
The Three Audience Tiers
Tier 1 — Public
- Canonical URL:
leja.ng/pro/[handle] - Indexable by search engines, shareable as a digital business card
- No Leja account required to view
- Shows: verified badge, aggregate witnessed stats, active listings/services, contact CTA, brief professional narrative
- This is the “anyone with the link” tier
Tier 2 — Leja Network
- Logged-in Leja users (residents, seekers, other professionals)
- Shows: full professional record highlights, detailed portfolio, Trust Graph summary, ability to enquire or follow the professional
- Residents looking for agents or housing see this layer
Tier 3 — Institutional
- Verified B2B contacts: landlords, developers, embassies, corporates
- Shows: full mandate history, portfolio depth, AI-generated professional performance narrative, exportable professional dossier
- The kind of material a real PR firm would prepare for a pitch meeting
- Direct engagement pathway for B2B trust decisions
Relationship to the Rest of Leja
Trust Graph is the source. Every element in Presence traces to a witnessed event in the Trust Graph. Presence is the publication layer on top of Trust Graph, not an independent data store. One product rule. Presence lives in Leja Ops. But a professional’s public Tier 1 page is visible and linkable from the Resident surface — a resident who finds their current agent can tap their name and reach the agent’s public Presence. One ecosystem. One identity layer. Marketplace vs Presence distinction:- The marketplace is transactional: find a property, book a service
- Presence is relational + narrative + external: build a brand over time, so inbound clients arrive pre-sold, with verified proof that preceded them
- Story — who the professional is, their track record, verified wins, growth narrative
- Relationship — brand built over time; inbound clients come pre-sold
- External reach — indexed publicly, shareable, the professional’s digital business identity outside Leja
Story Moment Engine (Section 2 — Locked 12 June 2026)
A story moment is a unit of professional content automatically generated by the AI from a trigger in the Trust Graph. It is not marketing copy — it is a witnessed fact expressed in human-readable form, with the source record linked. A viewer can always see what backed the claim.Six Story Moment Types
| Type | Trigger | Example output |
|---|---|---|
| Milestone | Quantitative thresholds in the ledger | ”50 rent payments witnessed. Every one verified.” |
| Performance pattern | AI detects trend across multiple records over time | ”95% on-time payment rate across 40 tenancies. 18 months. Zero disputes escalated.” |
| Trust tier | Verification upgrade, new badge earned, BRN confirmed | ”Professional record now BRN-verified. Independently confirmed.” |
| Portfolio | New mandate, new location, new property type | ”New mandate signed. Location-aware context, not exact address.” |
| Growth | Org adds verified agent, tier upgrade, first enterprise engagement | ”Team now verified at 4 agents. All operating under the same BRN.” |
| Record depth | AI detects unusually long or deep unbroken witnessed record | ”Three years of unbroken witnessed activity. No gaps. No self-reported history.” |
Story Moment Anatomy
Each moment contains:- Headline — short, punchy (AI-written, professional can edit)
- Body — 2–3 sentences of context (AI-written, professional can edit)
- Source records — the specific witnessed events that created this moment (always linked, non-removable by the professional)
- Suggested tier — AI recommends which audience tier(s) this belongs to
- Visibility rule — what detail level each tier sees (Tier 1 gets summary; Tier 3 gets full record link)
The Curation Workflow
The “Not Self-Reported” Guarantee (Invariant)
Every published story moment carries a tamper-evident link to its source witnessed record(s). The professional can edit the narrative — they cannot edit or remove the source record link. Human-in-the-loop is mandatory: no story moment ever publishes without explicit professional approval. This is consistent with Leja’s AI governance rule (aiConfidence + human gate).Active Publishing Layer (Section 3 — Locked 12 June 2026)
The professional’s deliberate voice on top of the AI story floor. Where story moments are reactive (AI surfaces what the record earned), active publishing is intentional — the professional reaches the market for a specific reason.Four Active Content Types
| Type | What it is |
|---|---|
| Deal showcase | A specific property or service actively marketed — a full pitch backed by witnessed records (rent history, occupancy rate, tenancy duration) |
| Announcement | A milestone declared on the professional’s own terms — narrative on top of their record |
| Service capability | What the professional offers and who it’s for — a structured card that persists on their Presence page |
| Team update | Organisation-specific — new agent verified, team expansion, new location coverage |
Campaign Tools — Targeted Exposure
A campaign is not a paid ad. It is the professional directing their Presence at a specific audience segment for a specific purpose. Mandate seeking — targets landlords/property owners who have interacted with Leja but have no active professional managing their property. The professional’s record and current portfolio are shown as the pitch. Professional sets location context and property type. Tenant network growth — targets residents and space seekers actively searching for accommodation in overlapping locations. Verified track record surfaced alongside active listings. Corporate / institutional reach — targets verified B2B contacts (companies, embassies, developers). Shows the institutional dossier. Requires Tier 3 verified contact to receive it. Professional does not see who received it — only aggregate engagement signals.What the Professional Controls vs. What Leja Controls
| Professional controls | Leja controls |
|---|---|
| What to publish and when | Source record links (always present, non-removable) |
| Narrative text and tone | Verification badges (only from witnessed activity) |
| Which audience tier sees what | Audience targeting eligibility (based on record depth) |
| Campaign timing and location context | What “verified” means on each claim |
| Whether to run a campaign at all | Privacy of individual residents and landlords in the record |
Campaign Eligibility — Record Depth Gates
Reach is earned, not bought. The professional’s own witnessed record determines campaign access. A professional with 6 months and 10 receipts does not get the same reach as one with 3 years and 400 receipts. This keeps campaigns defensible — they are not a paid advertising surface.Design Sections Status
- Section 1: What it is, where it lives, architecture decision, three tiers
- Section 2: AI story moment engine — 6 types, anatomy, curation workflow, not-self-reported invariant
- Section 3: Publishing + amplification layer — 4 content types, 3 campaign types, eligibility gates
- Section 4: Data model implications — 4 new entities (ProfessionalPresence, StoryMoment, PresenceContent, PresenceCampaign), schema law compliance, privacy rules
- Section 5: Monetisation — segment gates, campaign credits by tier, record depth thresholds, what Presence never does to revenue model
Data Model (Section 4 — Locked 12 June 2026)
Four new entities. No changes to existing schema. All connect to existing records via foreign keys and comply with all 10 schema laws.ProfessionalPresence
One per professional or organisation. Configuration record that activates
Presence, assigns the handle, and holds public bio and active state.
Inactive by default — professional deliberately activates it.
Key fields: handle (unique, public URL slug), isActive, publicBio,
tier, organisationId (nullable — solo agents reference userId),
phaseTag.
StoryMoment
One per AI-generated content unit. Created automatically when AI detects
a trigger in the Trust Graph. Holds both the original AI text and the
professional’s edited version (originals always preserved).
Key fields: type (enum: MILESTONE / PERFORMANCE_PATTERN / TRUST_TIER /
PORTFOLIO / GROWTH / RECORD_DEPTH), headline, body, aiHeadline,
aiBody, status (PENDING / PUBLISHED / DISMISSED / SCHEDULED),
audienceTier, sourceRecordIds (non-nullable array — always populated),
aiConfidence (Law 5), humanApprovedAt (null until approved — Law 6),
scheduledAt, publishedAt, deletedAt (soft delete — Law 9), phaseTag.
PresenceContent
One per piece of professional-authored active content. No AI generation —
no aiConfidence field. Location context is city/region/LGA only (Law 4).
Key fields: type (enum: DEAL_SHOWCASE / ANNOUNCEMENT /
SERVICE_CAPABILITY / TEAM_UPDATE), headline, body, status
(DRAFT / PUBLISHED / ARCHIVED), audienceTier, linkedPresenceId,
publishedAt, deletedAt, phaseTag.
PresenceCampaign
One per campaign run. recordDepthSnapshot is written once at creation
and never updated (Law 2 — immutability). Stores only aggregate engagement
signals — never individual viewer identities.
Key fields: type (enum: MANDATE_SEEKING / TENANT_NETWORK /
CORPORATE_REACH), status (DRAFT / ACTIVE / COMPLETED / PAUSED),
locationContext (city/region/LGA only), targetPropertyType (nullable),
recordDepthSnapshot (immutable eligibility proof), aggregateReach,
aggregateEngagements, startedAt, endedAt, phaseTag.
What Does NOT Need a New Entity
- Engagement analytics (views, follows, enquiries) — aggregate counters on
ProfessionalPresence, not a separate table. Individual viewer tracking is explicitly prohibited. - Verified badges — computed at read time from the Trust Graph. Not stored on Presence entities.
Monetisation (Section 5 — Locked 12 June 2026)
Governing principle: Presence earns reach through the ledger, not through spend. Campaigns are not ads. Monetisation reinforces the compounding record — the longer a professional operates on Leja, the more powerful their Presence.Segment Access Gates
| Feature | Segment A (transaction) | Segment B (subscription) |
|---|---|---|
| Tier 1 public profile | ✓ Basic — verified stats, handle, CTA | ✓ Full — narrative, AI bio |
| Story moments | ✗ | ✓ Included |
| Active publishing | ✗ | ✓ Included |
| Tier 2 Leja Network visibility | ✗ | ✓ Included |
| Tier 3 Institutional visibility | ✗ | ✓ BRN verified + record depth required |
| Campaign tools | ✗ | ✓ Credit-based |
Campaign Credits — Segment B Only
One credit = one campaign run (any type). Unused credits do not roll over.| Tier | Credits/month | Top-up rate |
|---|---|---|
| Growth (₦15,000/mo) | 2 | ₦3,500/credit |
| Scale (₦35,000/mo) | 5 | ₦2,500/credit |
| Enterprise (₦65,000/mo) | 12 | ₦1,500/credit |
Record Depth Thresholds — Campaign Eligibility
| Campaign type | Minimum required |
|---|---|
| Mandate seeking | 3+ months active + 20+ witnessed receipts |
| Tenant network growth | 6+ months active + 50+ witnessed receipts |
| Corporate / institutional reach | 12+ months + BRN verified + 100+ receipts |
recordDepthSnapshot (immutable). Cannot be gamed retroactively.
Tier 3 Passive Eligibility
Segment B + BRN verified + 6+ months witnessed activity. An institution landing on a professional’s public URL is automatically shown the tier appropriate to their verification status — verified corporate sees Tier 3; unverified visitor sees Tier 1.What Presence Monetisation Never Does
- Does not replace transaction revenue (₦250/receipt, ₦500/agreement) — additive
- Does not create pay-to-rank (more spend ≠ better record position)
- Does not charge for Tier 1 public profile — network growth mechanism
- Does not expose individual resident/landlord data as campaign targeting input
Open Questions (deferred — post-implementation)
- What is the exact format of the Tier 3 exportable professional dossier?
- Who manages Presence for organisations with multiple agents — designated manager role?
- How does Presence interact with the resident-facing Space surface at the surface level?