S-06 — Environmental Playbooks (for stakeholders)

Scope: Plain-language explanation of what "environmental" means on Jijibora: playbooks that watch for a change in the world and react by themselves under a pre-agreed checklist, leaving proof behind for residents, estate managers, and officers to check. Status: as of 2026-11-09 Blueprint sources: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; S-03 — Jijibora Playbook Registry (stakeholder + developer); S-02 — What Jijibora Can Do for You (plain-language feature guide); docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md

What this means for you

Environmental means a building, a crew roster, or a neighbourhood that notices something on its own — for example a sensor state change, a resident report, or a standing checklist reaching its time — and follows the single pre-approved response without five separate phone calls (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Each playbook below states who feels the change, what is different for that person, what stops the playbook from doing too much, and what record you can inspect afterwards. Where the sources do not state a detail, this document says UNKNOWN rather than guessing.

Details

What "environmental" means in plain words

On this platform the environment watches itself. A thing in the world — a building, a pump, a gate, a crew, a flood gauge, a resident's report — is named once in a shared list, and when its state changes the playbook reacts instead of waiting for a dashboard refresh (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). The sources describe the arc in three words: sense, then reason, then act (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json). Sense is the sensor or a resident reporting something; reason is checking that report against a pre-agreed checklist; act is the small, allowed action — telling the right people, calling the right crew, opening a shelter — and leaving a receipt behind (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

Two things make this safe to buy. First, nothing acts on raw device noise: it acts only on named things in the shared list, a building that was registered, a crew that was registered, a gauge that was registered (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Second, serious steps keep a named person in charge: a manager taps once to approve a proposed crew, a board approves what the assistant proposes, an inspector signs before any money moves (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

The starter product you buy first is the daily desk — maintenance reports, dues, gate passes, and the assistant that classifies and narrates in English and Swahili (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). The environmental families in this document are the expansion: after the desk is working, the same primitives are switched on for reflex, sourcing, recurring rounds, emergency cascade, and sensing (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Full orchestration of standing orders and solver routing is described as a Month 4+ add-on, and emergency dispatch is a later tier, so treat the later families as a ladder, not Day 1 (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

1. Building reflex — a building that reacts without glue-work

Who feels it. Facilities directors who own pumps, generators, gates, air-conditioning, lifts, and shuttle buses, and the residents who live with those systems (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). In the town version, the same people are the public-works desk and the crews who hear about rain, power, or water before water reaches doorsteps (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What changes for them. Instead of waiting for a refresh or convening five emergency meetings, the building reacts in seconds when a sensor or a resident report changes its state (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). The trial example is rainfall crossing a threshold and disaster, public works, transport, and welfare crews each receiving their pre-approved task at once (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). On an estate, the same reflex is what starts cooling in a care wing during a heatwave or diverts heavy trucks off fragile roads during rain, instead of waiting for a phone tree (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What prevents overreach. Only the terminal actuation step may issue commands; the sensing and reasoning steps may only observe and share findings internally (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json). The system reasons over named buildings only, and the reaction is limited by depth — the playbook may only walk a short chain before stopping and asking a person to review it, so a trigger cannot loop forever (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Routine notices go at once, while serious steps still need a named officer to tap Approve (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What the audit looks like. The verifier keeps a proved reflex trail: a record that the reflex fired, in a standard message shape that preserves cause, so you can see what the building sensed, why it fired, and what actuation followed (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Exact award-file schema beyond that fired notice is UNKNOWN in these sources (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

2. Community sourcing — a need arises and the nearest qualified crew is shortlisted

Who feels it. The community or county buyer and the panel manager who must fill a vacancy quickly, and the local plumbers, masons, and mechanics on the approved register who want fair work without red tape (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What changes for them. When equipment fails — a pump losing pressure, a culvert damaged — the system checks the municipal register of pre-vetted certified local technicians in that ward, selects the closest qualified technician, and coordinates tools and materials (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). In the estate product, the same step is the maintenance desk proposing the nearest certified vendor and a manager approving in one tap (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Fair local hiring changes from "who you know" to "distance, verified skills, and fair rotation," recorded so auditors can see the ranking (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

What prevents overreach. The system may only pick people inside the approved register and cannot invent skilled workers who do not exist (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Qualification comes before any shortlist: no award is made until the authority verdict arrives, and thresholds that define local content can be changed declaratively without code (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Sealed private content never travels inside a match, and an unattested provider is refused (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json). In the estate desk the AI only proposes; the human approves (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What the audit looks like. A privacy-safe match transcript (facets only, sealed content never in the match) plus a bind receipt, and an onboarding ledger for each provider step (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). For the estate desk, every assignment is narrated in plain English and Swahili — who, how far, what cost is held — and the verification step seals the milestone before any money moves (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

3. Civic maintenance rounds / recurring orders — standing orders that recur on their own clock

Who feels it. Ward and estate managers who walk the same checks on the same clock, and residents who would otherwise phone twice for the same recurring service (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

What changes for them. A standing order is a pre-agreed checklist written once in plain language — for example when the river passes its set height, send warnings, unlock the school shelter, and alert Public Works — and it starts by itself when the gauge, meter, rain station, or citizen's phone report passes the set limit (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Warnings reach families before water reaches doorsteps, shelters open on time, and teams do not need five emergency meetings (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). On an estate, that means drain clearing, pump checks, and generator checks recur on their own clock instead of being re-typed each month (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What prevents overreach. Each standing order carries an explicit limit — a height, a count, a time window — and may act faster than the council promise but may never secretly loosen it; a child rule that widens the parent promise is refused when it is written (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). A recurring chain that would trigger forever after a few steps stops and asks a person to review it (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Routine alerts go at once, while serious steps need a named officer to approve (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What the audit looks like. The same case file serves all departments, so nobody copies forms or walks memos across town — water engineer, health officer, and procurement clerk see the same record at once (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Each round leaves a breach or fire record when the order's limit is crossed, and a completion record when work is proven with photo and arrival point before closing (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Exact calendar cadence values per ward and any per-ward loosening beyond the example are UNKNOWN in these sources (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

4. Emergency and SOS dispatch — a distress signal fans out to named responders

Who feels it. The emergency commander or disaster office, agency crews and the community guard as responders, and residents in the affected low-lying areas who receive warnings (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). In the estate product, emergency dispatch is explicitly deferred as a later add-on tier, not part of the starter desk (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What changes for them. An emergency signal fans out to named responders instead of letters crossing town; each responder task carries the exact location and needed materials (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). The flood example tasks disaster, works, transport, and welfare crews per the pre-approved plan in seconds, and sends local-language warnings to low-lying residents (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

What prevents overreach. Only the terminal dispatch step may act, and each forked child case carries its own limits; a child cannot widen the parent's scope (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Public alerts are derived from scrubbed fields only, unless a purpose grant exists (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Emergency information shared with a crew expires after a short window rather than staying open indefinitely (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Ceilings still refuse widening even in a crisis, and a named human — never "the system" — closes the incident (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What the audit looks like. An emergency match receipt plus a resource assignment log, a fork-tree receipt with child-closed notices, and public alerts drawn only from scrubbed fields (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Each governed emergency action writes its own audit trail; the interaction is also welcoming the responsible officer's approval as its closing step, never automatic (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

Who feels it. Residents who receive warnings and reminders, and the community desk led by Kutuma reminders plus the disaster and public-works desks for warnings (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What changes for them. One shared entry updates every desk at once, so notices reach residents in local languages — flood warnings, dues reminders, gate passes, polling — without re-typing (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Announced templates are rendered from shared language packs in English, Swahili, and French, and sent by message and email (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Sensing insights inform people; they do not approve anything by themselves (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What prevents overreach. Sensing match facets are scrubbed before they may be used — surprising raw metadata inside a facet is refused rather than matched — so private detail never travels in a public notice (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json). A notice may not be published outside its ceiling, and break-glass announcements require dual approval with a time limit and an audit entry (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What the audit looks like. Notification templates live in shared storage and are versioned per key, so an auditor can see which language pack sent which notice and when (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Per-message delivery receipt shape is UNKNOWN in these sources (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

6. Waste management — household reports, replanned routes, and proof per stop

Who feels it. Residents who report overflowing containers or missed pickups, drivers who run the collection round, and the ward or estate desk that owns the round (source: S-02 — What Jijibora Can Do for You (plain-language feature guide); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What changes for them. A household report follows the same path every other maintenance report follows: intake on the channel the resident already uses, classification and location, proposal of the nearest certified service, one-tap approval by a named manager, then the driver route is replanned and resequenced — for example refuse-truck runs can be sequenced so markets are cleared before morning trade (source: docs/jijibora-government-trial/05_IMPLICATIONS_AND_APPLICATIONS.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). Nearby stops are grouped so a crew covers them in one trip, saving fuel, and an overflowing report re-plans the round instead of waiting for the next weekly list (source: docs/jijibora-government-trial/05_IMPLICATIONS_AND_APPLICATIONS.md; source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). A stop marked as missed is rescheduled rather than silently dropped, and a completion record — not a device ping — closes the stop (source: S-02 — What Jijibora Can Do for You (plain-language feature guide); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What prevents overreach and false fines. Never does a sensor, a phone location, or a driver-device signal alone trigger a fine or certify a collection. The organisation's own rule across all civic maintenance is no payout and no certification without arrival-point proof plus a time-stamped photo plus an inspector sign-off (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). The driver or collector cannot approve their own close, missing sorting or arrival checks are refused rather than guessed, and a sensor report can only open an inquiry — the fine, if any, requires the same photo plus arrival-point plus sign-off evidence as any other verified work (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). Routine notices go at once; any penalty step is a serious step that needs a named officer to approve (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

What the audit looks like. An audit packet per stop: the household report, the replanned route order, the time-stamped photo of the completed collection, the arrival-point confirmation, and the inspector sign-off, sealed into one permanent record before any money moves (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). Fare and contract detail beyond that packet — specific collection rates, per-stop fines, and missed-collection rescheduling timers — is UNKNOWN in these sources (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

7. Weather preparation — a reversible prep ladder, distinguished from emergency dispatch

Who feels it. Families in low-lying areas receive the early warnings; caretakers, public-works crews, and welfare teams act on the prep tasks; the disaster office watches the post-event report (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide)).

What changes for them. Weather preparation is a three-rung ladder driven by a rainfall or river-height threshold crossing, on pre-approved standard operating plans without five emergency meetings (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). First, alerts go out in local languages and drivers are warned to avoid low bridges (source: docs/jijibora-government-trial/06_CONTEMPORARY_ISSUES.md; source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). Second, pre-positioning happens on pre-authorized powers — sandbags and pumps staged, drains cleared, heavy trucks diverted off fragile roads, and the school shelter unlocked by its caretaker — all under the checklist the council already approved (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md; source: docs/jijibora-government-trial/05_IMPLICATIONS_AND_APPLICATIONS.md). Third, a post-event report records what was staged, what was used, and what remains, so the round can be stood down cleanly (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

How preparation is distinguished from dispatch. Preparation is reversible: sandbags can be unpacked, pumps recalled, shelter re-locked, and trucks re-routed when the threshold falls back, and no money or certification moves on preparation alone. Dispatch is consequential: the emergency cascade tasks named crews to act in the community, opens a governed incident, and each governed step writes its own proof session and needs a named human to close it (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). In short: preparation follows the pre-authorized checklist and can be undone without audit damage; dispatch creates a record that stays and must be closed by a person (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide)).

What prevents overreach. Each prep step still respects its ceiling: a ward may act faster (for example a shorter hours promise) but never loosens the council promise, and a child rule that widens the parent is refused when written (source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). Public alerts use scrubbed fields only, unless a purpose grant exists (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

What the audit looks like. Alerts sent, staging tasks issued, arrival-point proof for drain clearing or pump placement, and a post-event standing report showing what was staged versus used (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md). Forecast ingestion subjects, sandbag inventory specifics, and preparation-unwind timers are UNKNOWN in these sources (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Low-resource, cross-cutting: how every family above works where phones are few and cash is phone-first

All seven families are designed to run without a smartphone app, without continuous internet, and without a monthly subscription assumption (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-07 — Starter Packs for Stakeholders).

Offline-first capture. Reports and proof are captured offline and sync later; offline tolerance on mobile is part of the starter non-negotiables, not an add-on (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-07 — Starter Packs for Stakeholders). Detailed offline storage, queuing, and conflict conventions are UNKNOWN beyond the tolerance guarantee in these sources (source: S-07 — Starter Packs for Stakeholders).
USSD and WhatsApp-only users, no smartphone dependency. Headless logic lives in background engines and surfaces are optional consumers — WhatsApp, USSD, text messages, and web — so a resident needs no smartphone app to report, to be dispatched, or to receive a receipt (source: Architecture — Design Thesis and Planes (Developer Concept Doc); source: Jijibora Competitive Positioning — Buyer's Language; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Mobile-money-first down payments. Money moves by mobile money first: repair and escrow disbursement reaches the artisan by mobile money only on verified proof, with card and bank as secondary rails (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-government-trial/02_TRIAL_PROPOSAL.md). In practice pilots run with manual reconciliation until live payment keys are in place; automatic deductions are not promised (source: S-07 — Starter Packs for Stakeholders).
Pay-per-use metering, no monthly subscription assumptions. Usage is metered per charged unit — per certified bag, per work order, per dues transaction — with a split that must sum exactly to the whole and two-person approval, rather than a presumed standing monthly fee (source: D-06 — FINMON: Money Side — Billing, Desks, and Proof of Value; source: docs/commercialization/playbooks/dictionary.v1.json). Exact pay-per-use price tables are UNKNOWN and unpublished until the pilot charter is signed (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Multilingual narration in English, Swahili, and French. Every step is narrated in plain English, Swahili, and French from shared language packs, so a USSD or WhatsApp user receives the same proof story in the language they chose (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

What to ask the provider before you sign

Which ISO-style evidence pack numbers will you receive for each family, and who recomputes the receipt chain on your behalf (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer))?
Which steps need a named manager or board member to tap Approve, and which steps are allowed to act without that tap (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)?
How do I pause or disable a single reflex or recurring round without affecting other families, and what record shows that pause (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)?
Which warnings are sent in Swahili and French, and what is the single entry point that updates every desk at once (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer))?
What is explicitly not in the pilot — for example standing orders and emergency dispatch — and what date or condition moves those into scope (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)?
How is personal data kept out of notices and receipts, and how long does emergency access remain open on a phone after handover (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)?
For waste rounds, what proof closes a stop, and how is a missed collection rescheduled (source: docs/jijibora-government-trial/05_IMPLICATIONS_AND_APPLICATIONS.md; source: S-02 — What Jijibora Can Do for You (plain-language feature guide))?
For weather preparation, which steps are pre-authorized and reversible, and what closes a preparation stand-down (source: docs/jijibora-government-trial/06_CONTEMPORARY_ISSUES.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer))?
How do I pay per use rather than by monthly subscription, and how are residents who only have USSD or WhatsApp reached in English, Swahili, or French (source: D-06 — FINMON: Money Side — Billing, Desks, and Proof of Value; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)?

Open items / gaps

Reflex reaction speed is described as seconds, but no sourced numeric service-level target is stated for building reflex — UNKNOWN in the read set (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).
Civic sensing notification cadence and break-glass thresholds (time limits, approvals) are stated as design intent; live production threshold values are UNKNOWN until the customer charter is signed (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Automated emergency friend-list or proximity targeting beyond pre-approved standard operating plans is UNKNOWN and should not be assumed; the sourced plan only covers the pre-approved cascade (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).
Per-message delivery receipt shape, fiscal year fee values, and savings percentages are UNKNOWN and unpublished until the pilot baseline is measured (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).
Waste-management headless subjects, per-stop tariff and fine schedule, missed-collection rescheduling service levels, and forecast ingestion for weather preparation are UNKNOWN in the read set — only narrative behaviour is sourced (source: S-02 — What Jijibora Can Do for You (plain-language feature guide); source: docs/jijibora-government-trial/05_IMPLICATIONS_AND_APPLICATIONS.md).
Offline queuing and conflict conventions beyond "offline tolerance," plus exact pay-per-use price tables, are UNKNOWN and unpublished until the pilot charter is signed (source: S-07 — Starter Packs for Stakeholders; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).