Manco Meeting Agent

Renewal commercial offer · escalation under-application audit · arrears recovery — all converging on the same tenant. Treating these as 3 unrelated workstreams is fragmenting the relationship. A single AfriSky-level intervention thread would consolidate the conversation.

• ·Draft AfriSky proposal · Block C 4A
• ·Sign off CoJ tariff back-correction (AfriSky-adjacent)
• ·AfriSky 60-day arrears thread

Tariff band misalignment on MM-01 + surcharge over-application on MM-04 both lodge against the same supplier. A consolidated CoJ engagement (single liaison · monthly portfolio-level review) would surface these earlier than per-meter audit cycles.

• ·Sign off CoJ tariff back-correction lodgement
• ·Push CoJ lodgement to municipality once signed
• ·MM-04 VAT/surcharge liability finding (this cycle)

Half the renewal pipeline has a flagged lease audit. Renewal conversations should start from the audit posture — yet today's manco discussed proposals + audits as separate items. A unified at-renewal audit summary on the renewal inspector would close this loop.

• ·Tenant-by-tenant renewal strategy memo · 5 at-risk tenants
• ·AfriSky · 4 audit findings
• ·Volta Studios · OpEx pro-rata finding

AfriSky's escalation under-application has been flagged 3 cycles running. The variance feed renders each instance as an isolated row, which masks the systemic-vs-one-off distinction. Recurrence count is a real signal — it's the difference between 'fix invoice' and 'fix lease clause interpretation'.

The renewal book on /report/pulse shows count + at-risk per bucket, but doesn't reflect the commercial conversations the manco kicked off. An asset manager looking at the pulse can't see that AfriSky's renewal is mid-negotiation.

Absent shareholders see AT_RISK_TENANTS + KPI snapshots, but not the manco actions that affect those numbers. The trust loop the manco is supposed to close (manager doesn't write minutes, owner doesn't chase status) only closes if the owner actually sees the actions.

Renewal proposals get drafted in /operate/renewals but they're not subject to the same audit rigor as lease pillars. A 'commercial offer terms' pillar would track market-comp deviation, escalation cap reasonableness, incentive cost vs renewal-probability uplift — and feed audit_rows just like Financial & rent does.

• Inferred from
• ·Draft AfriSky proposal · Block C 4A · R150/sqm with server-room move
• ·Tenant-by-tenant renewal strategy memo · 5 at-risk tenants

When a manco discusses AfriSky for 5 minutes, Recall captures the audio but the transcript doesn't link those 5 minutes to the AfriSky tenant entity. Auto-tagging by named-entity extraction would let the renewal inspector show 'discussed in last 3 mancos · 12 minutes total' as context.

• Inferred from
• ·All 5 actions tied to specific tenant or meter entities via linked_artefact

CoJ comes up in 2 of 5 actions. There's no surface for 'all open lodgements with CoJ', 'CoJ ack-time SLA', 'CoJ escalation contacts'. Today the action board pushes per-meter; consolidating at the supplier level would let the manco track relationship health (not just per-meter progress).

• Inferred from
• ·Sign off CoJ tariff back-correction lodgement
• ·Push CoJ lodgement to municipality once signed

The current Manco page shows the latest meeting only. To detect patterns across mancos (e.g. 'this is the 3rd cycle AfriSky has been at-risk'), an action-history surface keyed by tenant or pillar would be needed. Today's recurrence detection only works because the bot synthesises across cycles in-memory.

• Inferred from
• ·Tenant-by-tenant renewal strategy memo · 5 at-risk tenants