S-13 — Wider Scenarios: Schools, Help Desk, Housing, Facilities, Traffic and Compliance (stakeholder)

Scope: Plain-language guide to the wider community and municipality scenario families — school zones, help desk and complaints, public reporting boards, malls and public spaces and government buildings, housing allocation and relief, traffic corridor monitoring, and real-estate compliance — for ministries, municipalities and community buyers deciding what to adopt. Status: as of 2026-11-09 Blueprint sources: Community-life fragment family guide; facilities fragment family guide; housing fragment family guide; public-property and property-compliance fragment family guides; playbook registry and stakeholder overview in docs/platform-map/jijibora/; reflex and starter-bundle guides in docs/platform-map/jijibora/.

What this means for you

You can now run everyday city work as repeatable, receipt-backed playbooks rather than as phone calls and paper folders — a school road that goes calmer at set hours, a complaint that climbs a clock without disappearing, a housing queue with published reasons, a building safety certificate with receipts behind it, and a monthly public digest that only publishes when a named person approves it. Every wider scenario below proposes and advises first; anything that changes a road, a queue, a building or a record needs a named human to approve it, and nothing fines, pays or closes a case from a signal alone (source: community-life dossier, "Purpose" and "Guardrails" — non-consequential actuation, no fines from reflexes; source: facilities dossier, "Guardrails" — fail-closed, human approval preserved; source: housing dossier, "Guardrails" — no allocation without human confirmation).

Details

These seven families extend the smaller starter sets. They share the same discipline: rules are declared once in plain, reviewable values, read at runtime from a central lookup store, practiced in Soft mode before they touch live records, and proven with append-only receipts. If something is not declared, the family refuses rather than inventing it (source: facilities dossier, "Wiring" — runtime reads lookup store, never invented values; source: housing dossier, "Wiring" — bands and evidence read from lookups, never reproduced as fixed numbers).

1. School zones — safer roads in set hours

Who feels it: Schoolchildren, crossing guards, parents and caregivers, and drivers near a school gate. What changes: When the school calendar says set hours are on, the zone advises — guard rostering is proposed, crossing-safety prompts are raised, and parents and caregivers subscribed to the zone receive a timely advisory (source: community-life dossier, "Wiring" — school calendar window to advisory, guard-roster proposal, parent advisory subscription). Outside set hours, that advisory mode goes quiet; it does not reroute traffic or set signal timing on its own. Who approves: A named school or ward owner approves any roster or movement change. The reflex itself is advisory only and cannot restrict a road or retime a signal (source: community-life dossier, "Guardrails" — consequential acts need a named human owner; school-zones scope is safety and movement only, no revenue logic). Proof you receive: An advisory receipt tied to the school calendar window and the zone, plus the guard proposal record. Guard roster members remain UNKNOWN in the read set and are resolved at runtime — the family never invents people (source: community-life dossier, "Guardrails" — rotations resolved at runtime, members UNKNOWN). What to ask: Which calendar governs the window, who owns the roster, and what happens when the calendar changes mid-term? Window durations and corridor values are UNKNOWN here and must be declared as lookup values before go-live (source: community-life dossier, "Guardrails" — window and corridor values UNKNOWN).

2. Help desk and complaints ladders — report, assign, prove, close

Who feels it: Residents filing a report, front-desk agents, supervisors, and the ward office. What changes: A report arrives by simple channels — free text, messaging apps, or menu-based services such as USSD over WhatsApp and USSD, with no smartphone required — and is classified into a desk category (maintenance, security, pest, cleaning, or other) then confirmed by a human grader within a service clock before assignment (source: community-life dossier, "Wiring" and "Low-resource note" — intake to classify to grader confirm within service window to evidence-required close-out; source: community-life dossier, "Guardrails" — classification needs manual confirm). Unanswered acks climb a declared ladder — acknowledge, urge, escalate, ward office — with timings read from the service-lookup values only (source: community-life dossier, "Wiring" — ladder timings from lookup values only). Who approves: The intake agent cannot also close the ticket; a different human approver closes it, and close-out requires a triage note as evidence (source: community-life dossier, "Guardrails" — separation of duties and evidence-required close-out). Escalation lands on named rotations, never invented people. Proof you receive: A routed ticket with a grader confirmation time, escalation receipts if the clock ran out, and an evidence-backed close-out note. What to ask: What are the service timings per category, who holds grader capacity on weekends, and can a resident appeal a close or ask for reopening — and on what basis? Reopening bands and service timings are UNKNOWN in the read set until bound as lookup values (source: community-life dossier, "Guardrails" — timings are lookup values; reopening operation is described in the administrator companion).

3. Public reporting boards — monthly digests that earn publication

Who feels it: Residents, councillors, ward leadership, and the communications duty team. What changes: Closed civic work is aggregated monthly into a draft digest; the draft is rendered in the household languages (for example English, Kiswahili and French from language packs in the template store) and then waits for human approval before any publication (source: community-life dossier, "Wiring" — closed work to monthly aggregate to draft to human approval to publish; source: community-life dossier, "Guardrails" — publish only with recorded human approval, no auto-publish). Unapproved drafts stay drafts. Who approves: A named communications approver. The digest family renders upstream verified outcomes as gates — it does not create its own savings or costs (source: public-property dossier, "Wiring" — digest invokes no sourcing or solving of its own). Proof you receive: The approved digest with an approval record, scrubbed-fields-only figures, and an archive copy. Sealed or private content never enters a public digest (source: public-property dossier, "Guardrails" — sealed content never in the match or the digest). What to ask: Who signs the digest when the usual approver is away, and what is the correction route if a figure is wrong after publication? Figure shapes and editorial checks beyond approval state are UNKNOWN in the read set (source: community-life dossier, "Guardrails" — approval discipline; exact digest template content UNKNOWN).

4. Malls, public spaces and government buildings — tenancy, rounds, inspections, certificates, bookings

Who feels it: Mall and building managers, tenants, cleaners and guards, park and playground crews, tenants' dispute desks, and residents checking whether a building is safe. What changes: Occupancy of existing storefront space entities is maintained with append-only receipts; security incidents climb a security ladder from ward security to the emergency desk with human approval at each step, never by reflex alone (source: facilities dossier, "Wiring" — occupancy receipts, security ladder ward security to emergency desk; source: facilities dossier, "Guardrails" — emergency-desk step never reached by reflex alone). Public furniture, parks and playgrounds receive preventive rounds — a scheduled visit prompt with a sequenced crew route; a missed round is rescheduled by the same guard and never silently dropped (source: facilities dossier, "Wiring" — round tick to crew route verdict, missed round rescheduled by the same guard). Large buildings pass fire, accessibility and hygiene inspections, then an independent expert sign-off, then a certificate and a receipts-only compliance packet (source: facilities dossier, "Wiring" — seven-stage inspection chain with expert sign-off and packet). Weekly community-use bookings of shared deck-type spaces are recorded as reservations (source: facilities dossier, "Wiring" — booking events recorded as reservations). Who approves: Occupancy, ladder steps, round dispatch, inspections and certificates each need their named approver; the inspecting worker cannot sign off their own inspection, and metering hooks attach by reference only with no invented rates or prices (source: facilities dossier, "Guardrails" — no self-approval, no self-certification; no sign-off, no certificate; metering hooks values-only). Proof you receive: Append-only occupancy receipts, ladder and booking receipts, visit prompts with an inspection-confirmed route, and — for buildings — all three inspection receipts plus the certificate reference in the packet. Spaces that resolve to zero or to multiple matches refuse rather than guessing (source: facilities dossier, "Guardrails" — spaces resolve or refuse). What to ask: Which spaces are registered, who holds the security-ladder roster, what cadence governs rounds, and what covers certificate and packet formats? Rosters, cadence, checklists and formats are UNKNOWN in the fragments until bound as lookup values (source: facilities dossier, "Review state" — cadence, rosters, checklists, formats UNKNOWN).

5. Housing — allocation by declared bands, options surfaced not forced, relief under SOS scope

Who feels it: Applicants, residents, housing officers and allocation panels, and emergency shelters. What changes: Applications are scored only by declared needs and eligibility bands and ranked into a queue with offers proposed — but allocation itself is a separate human decision through a panel with separation of duties and quorum (source: housing dossier, "Wiring" — ranked queue and offers are proposals only, allocation requires separate human confirmation; source: housing dossier, "Guardrails" — no allocation by reflex without human confirmation). There is no enumeration of individuals: eligibility resolves by band key plus evidence reference (source: housing dossier, "Guardrails" — individual enumeration forbidden). Residents see optional add-on resources as suggestions only; the playbook suggests resources and the resident chooses — no forced enrolment, no auto-charge, no assumed consent (source: housing dossier, "Guardrails" — no forced upsell; resident chooses). Emergency housing — evacuation placements and short-term subsistence evidence — runs as a child of the parent SOS ceiling: the child inherits the ceiling and may only tighten it, evidence attaches before any placement is proposed (source: housing dossier, "Wiring" — child inherits parent SOS ceiling; evidence attached first). Who approves: The housing panel approves allocation; the resident approves any optional add-on; the SOS authority owns the parent ceiling for relief placements. Proof you receive: A ranked-queue receipt carrying band keys and evidence references only, offer proposals, suggestion receipts carrying block or unit references with scrubbed fields only, and evidence-attached relief proposals inside the parent ceiling. A context event carrying personal data is refused rather than sanitised-and-proceeded (source: housing dossier, "Guardrails" — no personal data in public tiers). What to ask: What are the published bands, weights, panel quorum and shelter capacities? All are UNKNOWN until bound as lookup values — the family refuses while they are unbound (source: housing dossier, "Review state" — band sets, weights, quorum, inventories UNKNOWN).

6. Traffic corridor monitoring — pattern cases before pattern blame

Who feels it: Drivers, residents along a corridor, the traffic-duty desk, and signal engineers. What changes: Three or more incident reports on the same corridor open a pattern case and a jam-measure advisory with a signal-flow advisory, not a fine and not a road restriction (source: community-life dossier, "Wiring" — incident reports to pattern case to jam-measure and signal-flow advisories; source: community-life dossier, "Guardrails" — pattern case only when signals are quantified: count, corridor, timestamps, severity evidence). Evening demand is read as a pattern over time, not as a single report. Who approves: A named traffic owner approves any flow or restriction change. The reflex opens a pattern case only. Proof you receive: A pattern-case receipt with quantified signals — report count, corridor, timestamps, severity evidence — and advisory records. Where signals are not quantified, the family refuses to open a case (source: community-life dossier, "Guardrails" — scope fences). What to ask: What corridor and severity evidence qualifies, who owns the signal-flow advisory, and what closes a pattern case? Window, corridor, severity and jam values are UNKNOWN until declared (source: community-life dossier, "Guardrails" — only the three-report count is asserted; the rest UNKNOWN).

7. Real-estate compliance — zoning, encroachment, leases, disclosure

Who feels it: Parcel and building owners, neighbours, permit officers, tenants, buyers, and auditors. What changes: A zoning permit runs an ordered sequence — application, values-only zoning check, quorum decision, deed record — pausing while a conflict is open and never skipping the guard to resume (source: property-compliance dossier, "Wiring" — permit sequence; source: property-compliance dossier, "Guardrails" — conflict pauses permit). A suspected encroachment follows due process: evidence is attached, both neighbour and owner notices are served and recorded, and only then is the case reviewed — with quorum where disputed (source: property-compliance dossier, "Guardrails" — due process before review). Building compliance runs hygiene, fire and accessibility inspections to expert sign-off, certificate and receipts-only packet, with no self-certification (source: property-compliance dossier, "Guardrails" — no self-approval, no self-certification). Lease registration and renewal maintain an append-only register and use-change history per parcel, with arrears behaviour explicitly out of scope (source: property-compliance dossier, "Wiring" — append-only register history; arrears out of scope). Valuation comparisons produce transparency findings with mandatory provenance — observed comparisons only, never a projected increase, never a recommended price, never a single figure stated as value (source: property-compliance dossier, "Guardrails" — evidence-based only, no gouge projection). Who approves: Quorum panels decide permits and disputed cases; a different expert signs inspections; disclosure findings need complete provenance before they issue. Proof you receive: A deed receipt on the parcel, a resolution receipt with reviewed evidence attached, a certificate with all inspection receipts, an append-only lease register history, and a disclosure finding carrying comparable refs, evidence refs, and lookup keys. What to ask: What zoning-check values, notice periods, inspection checklists, and arrears rules apply — and who certifies them? Those values are UNKNOWN until bound (source: property-compliance dossier, "Review state" — zoning-check values, notice periods, checklists, formats UNKNOWN).

Open items / gaps

All wider families are Soft drafts — seedable, not yet seeded or live; a Soft apply validates with zero live rows and never declares itself live (source: community-life dossier, "Review status" — Soft draft, not seeded; source: facilities dossier, "Review state" — draft pack, not seeded; source: housing dossier, "Review state" — draft pack, not seeded).
Window and corridor timings, school guard rosters, help-desk service clocks, housing band sets and weights, round cadences, inspection checklists, certificate formats, and metering references are UNKNOWN until bound as lookup values — families refuse while unbound (source: facilities dossier, "Groundedness" — UNKNOWN list; source: housing dossier, "Review state" — UNKNOWN list).
Provisional stream and event names in the facilities, housing and property-compliance families are pending registration; canonical subject keys bind at wiring time (source: facilities dossier, "Purpose" — provisional naming, registration pending; source: housing dossier, "Purpose" — provisional naming, registration pending).
No fines, penalties or payouts arise from any reflex alone in this set; any consequence needs a separately governed disposition (source: community-life dossier, "Guardrails" — no fines or payouts from reflexes; source: facilities dossier, "Guardrails" — no auto-fine behaviour declared).