Playbook blueprints

When a space entity state changes (building, drain, road segment), the reflex evaluates registered rules and actuates the next step — paging the right desk, opening a case, or dispatching a crew. The platform's spinal-cord reflex for physical assets.

Turns a staffing requirement (crew, inspector, technician) into offers from qualified providers, shortlists them, and binds one — so the city never assigns work by guesswork. It is the sourcing bus other playbooks wire into.

Reacts to proximity events — a vehicle, crew, or sensor crossing a registered boundary of a road/drain/asset — by evaluating the crossing against rules and notifying or opening a case.

The emergency (SOS) signal for multi-agency response — water, power, road, hospital, flood. Converts a distress signal into a governed dispatch with proof of correct execution, so a response is never claimed without evidence.

Household accumulation signals become replanned collection routes; completion is a record, not a device ping; a missed collection is rescheduled, never silently dropped.

The rain/flood preparation ladder — rain-gauge triggers a pre-alert, sandbags and crews pre-position, then a post-event report closes the loop. Reversible prep happens automatically; consequential dispatch needs a human.

Community ticket intake (free text, WhatsApp, USSD) is classified and assigned to the right desk category (maintenance, security, pest, cleanliness, other), graded within SLA by a human, and closed only with evidence.

Every complaint has an explicit escalation path — acknowledge by class, then urge, then escalate, then ward office — driven by SLA clocks, not by who knows whom.

Three or more similar unresolved complaints in the same block within a declared window open a pattern case — the systemic signal that a street, drain, or fixture is failing repeatedly. It routes like any other case; it never fines anyone automatically.

Recurring preventive ticks for streetlights, manholes, and public furniture — each due occurrence emits an expected-visit plus a record step via the sourcing bus to a solver route verdict. A missed round re-schedules by the same guard.

Public dues/fees follow a polite ladder — reminder, notice, grace, escalate — with lifeline-degrade rules as values. Arrears degrade politely and never hard-block life-safety services.

Time-windowed movement governance around schools: calendar windows restrict through-traffic to safer flow near school gates, crossing guards are rostered, and parent/caretaker advisories subscribe to the safety state.

Road-incident / accident pattern detection: three or more reports on the same corridor open a pattern case; jam-measure triggers and traffic-light flow playbooks respond to quantified signals.

Aggregates closed civic work (faults fixed, rounds completed, dues collected) into monthly board digests per ward. The AI drafts; a human approves; only then does it publish. There is no auto-publish anywhere.

Stall, board, and occupancy tracking on existing storefront entities; a security incident ladder from ward security to the emergency desk; booking / deck reservations for weekly community use; revenue hooks into metering.

Public furniture, park, and playground maintenance rounds wired to the same rounds tick as patch rounds: each due occurrence emits an expected-visit and a record step via the sourcing bus to a solver route verdict; a missed round re-schedules.

Optional services for residents (blocks/units registered with no personal data): the playbook surfaces relevant add-ons and the resident chooses. No forced enrolment, no auto-charge.

Evacuation placements and short-term subsistence evidence after a disaster or eviction. Relief is a child of SOS: it inherits the parent ceiling and may only tighten it — never widen scope.

Housing allocation queues: application → needs scoring by declared bands → ranked queue → offers. Eligibility resolves by key from governed lookups with values only; individual enumeration is forbidden.

Lease registration / renewal events maintain the occupancy register; use-change events append use-change history per parcel (the entity's recorded life).

Market valuation comparison: similar parcels' evidence becomes transparency findings. Evidence-based only; no automated gouge projection; every finding carries its provenance. Comp prices are UNKNOWN until sourced.

Recurring civic checklist rounds in standing-order style: fault reported → fair sourcing of a crew → scheduling / routing → photo-or-arrival-point proof → verified disbursement. The everyday engine of ward maintenance.

Public facility inspection as a staged case: open → inspect (photo + GPS stamped) → score against the open checklist rubric (values) → remedy ladder (minor fix / re-inspect / escalate) → close with a PoCE seal.

Weekly / monthly digests of closed work per ward rendered from the canonical story into EN / SW / FR value packs. Advisory draft → approved; never auto-publish. It consumes closed-work telemetry, so upstream verdicts are rendered as gates, not recalculated.

Permit application → zoning check (values only) → quorum decision → deed record on the land-parcel entity. Unknown or ambiguous parcels refuse; open conflict tickets pause the flow.

Suspected structures on land: evidence attached → neighbor + owner notified (due process) → review (quorum if disputed) → resolution / receipt. Child states inherit parent limits and never widen them.

Building hygiene / fire / accessibility inspections ending in certificate issuance — but only with expert sign-off. Export a compliance packet. No auto-certification, no auto-fine.

The facilities-flavored sibling: large-building compliance inspections (fire, accessibility, hygiene) ending in expert sign-off, certificate issuance, and a compliance-packet export for big managed buildings.

Establishes the shared entity spine every other playbook depends on: land / parcel / space hierarchy, entity identities, and lifecycles. No pack works until the names agree.

The JMII-style maintenance entry: WhatsApp / USSD intake, classify, nearest certified vendor proposal, one-tap approval, photo + GPS verification, PoCE receipt, escrow-until-proof.

FIN-native ledger per community: accounts, AR / AP, period close; dues, fines, service charges, vendor payables; scheduled reminders; monthly statement + dashboard.

Community desks: announcements, gate passes, visitor logs, polling — the daily social fabric of an estate or ward.

The community guard pairing inside the safety stack: guard roster, incident reporting, and escalation into the emergency desk.

The full lifecycle expansion of the civic maintenance tick: report → dispatch → verified disbursement, end to end, as one bundle.

Parcel-centric operations: registrations, use changes, valuations, and permits bound to the parcel entity — the working surface for the property-compliance family.