S-03 — Jijibora Playbook Registry (stakeholder + developer)

Scope: Catalog of Jijibora playbooks — each entry is a named business process an operator/verifier can run, with plain-language customer view and a short design contract (subjects, effect, guardrails). This file is the stakeholder registry; the developer companion is docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md). 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; docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md; Playbook Registry — What You Can Run, Who Runs It, What You Get Back; D-17 — Backlog Validation (platform-map recommendations); docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md

What this means for you (plain)

Jijibora is sold as five named products on one shared substrate, never as the substrate itself (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md). A playbook is a repeatable, sellable procedure: the customer buys the procedure, the desk runs the pack, guardrails refuse anything unsafe, and the audit packet proves it happened (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Each expansion is a fragment activation + APF vocab add, not a migration (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

1. Building reflex — "a building that reacts to weather"

Plain: Facilities directors who own pumps, generators, gates, HVAC, elevators, shuttle buses run the Orchestration product; when a sensor/state change fires, the building reacts in seconds instead of waiting for a dashboard refresh (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md). Example from the government trial: rainfall crosses a threshold, then disaster, public works, transport and welfare crews are each tasked per the pre-approved SOP without five emergency meetings (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md).
Who runs it: Facilities director / public works desk (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md).
What evidence the verifier keeps: The rule description states the arc is sense-reason-actuate via Kestra + Camel, with SurrealDB as store-of-record only (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json). Stakeholder value is reaction speed plus a proved reflex trail; exact receipt shape is UNKNOWN beyond building.reflex.fired (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json).
Proof point: Requires Product 1 installed first (needs resource catalog + identity) (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md).

2. Community sourcing — "fair local sourcing, no favoritism"

Plain: When equipment fails (pump loses pressure, culvert damaged), the system checks the municipal register of pre-vetted certified local plumbers/masons/mechanics in that ward, selects the closest qualified technician, and coordinates tools/materials (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md). In the estate product the same step is the maintenance-desk dispatch: Akili proposes assignment (nearest certified vendor via KaziSasa graph) and a manager approves in one tap (Decision Gate) (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Who runs it: Community/county buyer + panel manager; service providers as candidates (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Evidence: A match transcript that is privacy-safe (facets only, sealed content never in match) plus a bind receipt, and onboarding ledger per step for provider onboarding (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Community-ticket vendor subtasks inherit parent limits and cannot widen them (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Value: Small local tradespeople get fair access without red tape; the rule design adds TGC qualify + solver-gateway before shortlist (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json).

3. MARS/ICE dispatch — SOS to crew, vehicle, facility

Plain: An emergency signal fans out to named responders instead of letters crossing town; responder tasks include exact location and needed materials (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md). In the estate product, emergency dispatch (MARS) and clinical features (AfiyaLink) are explicitly deferred as Tier C/D add-ons, not in the Starter Pack (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Who runs it: Emergency commander / disaster office; agency crews and community guard as responders (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md).
Evidence: Rule design emits emergency.dispatch.fired; the registry requires an emergency match receipt + resource assignment log, fork-tree receipt with child-closed notices, and public alerts derived from scrubbed fields only (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Value: Coordinated cascade (disaster + works + transport + welfare) in seconds per pre-approved SOP (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md).

4. Government benefit / compensation claims (claims packs)

Plain: Benefit = citizen application, cross-agency check, evidence sweep, dual approval, payment readiness (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Compensation = claim after loss, assessment, liability check, public-officer separation of duties, payment approval (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Who runs it: Agency desk plus a second agency as approver (benefit); Ministry/county compensation desk (compensation) (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Evidence: Cross-agency approval chain + evidence seal + audit export (benefit); compensation decision pack + evidence seal + approval receipt (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). All claims packs run first as a zero-write practice check; a pack cannot declare itself live (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Claims console UI and readiness semantics (infra_ready vs rollout_enabled, default off) are shipped and validated (source: D-17 — Backlog Validation (platform-map recommendations)).
Value: No self-approval, no payment without evidence; the verified escrow step is "no sign-off, no payout" with photo/GPS/proof before disbursement (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md).

5. Civic maintenance pilot (repairs linked to finance + photo proof)

Plain: One connected flow: fault detected → fair local sourcing → smart scheduling/routing → work on site with phone photo + GPS → inspector approves → mobile-money disbursement to the artisan; "zero ghost workers, zero fake invoices" (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md). The estate equivalent is the AI Maintenance Desk: intake → dispatch → verification (photo + GPS, optional inspector sign, PoCE receipt seals milestone) → escrow release only on proof (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Who runs it: Ward/public-works desk + ward inspector + Finance; estate manager + resident + vendor (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Evidence: The verifier receives time-stamped photo of finished work, GPS confirmation, and inspector signature before any shilling moves; maintenance is linked directly to finance and photo proof (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md). Every step is narrated in EN/SW ("Water leak at Block C, assigned to Juma (certified plumber, 0.8 km), ETA 2h, escrow KES 3,500 locked") (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Value: Eliminates ghost projects and ends cross-department blame (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md).

6. Procurement tier (multi-source fill + solver)

Plain: A buyer who needs a quantity (e.g. 100 kg across farms) gets a feasible allocation plan, not a hand-rolled spreadsheet; allocation is invented only after a real match (source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json; source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md). The solver runs only after match; if the solver service is down, the pack refuses (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md).
Who runs it: Buyer/authority desk; shortlisted suppliers as candidates (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Evidence: Fill plan (sourcing.fill_plan) or explicit infeasible (sourcing.fill_infeasible) (source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json). City Ready bundle rule: "solver only after a real match; live dispatch never invented when a service is down" (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Value: Cheapest feasible fulfillment across multiple suppliers with load on the real optimizer; optional routing stage thereafter (source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json).

7. Audit-file assembly (photo-backed compliance report)

Plain: When the World Bank, AfDB, or national treasury asks for proof of delivery, the authority generates a verified, photo-backed compliance report in two clicks (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md). The estate product adds monthly statement PDF (Gotenberg) + Superset budget-vs-actual dashboard (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Who runs it: Finance director / county operator + auditor touring PoCE receipt recompute (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Evidence: Photo/GPS/lab verification + PoCE receipt + PDF certificate (Escrow product) (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md). Exact award-file schema beyond these receipts is UNKNOWN (no sourced schema in the read set).
Value: Audit defense without reconstructing folders; pilot audit is an explicit exit gate (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

8. Citizen notifications (announcements, reminders, warnings)

Plain: One shared registry entry updates all desks instantly, so notices reach residents in local languages — flood warnings, dues reminders, gate passes, polling — without re-typing (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Who runs it: Community desk + billing desk (Kutuma reminders); disaster/public-works desk for warnings (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md).
Evidence: Notification templates live in NATS KV (SOVEREIGN_TEMPLATES / NATS KV templates, EN/SW/FR) and are rendered multi-channel via Matrix + Kutuma (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Per-message delivery receipt shape is UNKNOWN in the read set.
Value: Information entered once updates every desk; no photocopied forms (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md).

9. AI hooks (advisory-only — never the decider)

Plain: Akili (and the local Gemma4 lane for air-gapped communities) classifies, extracts location/urgency/photo, proposes assignment, and answers resident questions with citations; a human approves in one tap and the board approves what AI proposes (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Who runs it: AI assistant as proposer; estate manager / board / inspector as approver (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Evidence: Optional AI enrichment hooks (CLAIMAI-00) are tracking-only; the core path must work with hooks empty and there is no second runner (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md). Lifelong entity_state facet smoke is "never auto-APPROVED" (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md).
Value: Faster intake and narrative without ceding approval authority; no autonomous sign-off, no autonomous payout.

10. Industrial / local-content gate

Plain: Hire and supply with a minimum local-content share; no award until the authority verdict arrives (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Thresholds change declaratively without code change (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Who runs it: Buyer/authority desk; supplier as candidate (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Evidence: Local-content verdict receipt + award decision receipt (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). EU EUDR evidence pack is a Month 6+ supplier sell, deferred (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md).
Value: Fair industrial policy that is enforceable at award time rather than argued after payment.

The contracts (developer)

Short contracts: subjects, effect, guardrails. One row per playbook.

Playbook	Consumes	Emits / effect	Guardrails (refuse if…)
Building reflex (`rule:jijibora:building-reflex:v1`, v1.0.0, Tier-1 Camel, chain `kestra→camel`) (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json)	`platform.criteria.v1.building.entity_state` filter `entity_type=building` (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json)	`building.reflex.fired` on `platform.criteria.v1.match.fired`, `inherit_causation`, keyed `meta.tenant`+`entity_id`, pipeline `pipe:jijibora:building-reflex` stage `sense` (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json)	Non-terminal stage: commands only from terminal `actuate` handler; SurrealDB is SoR only, evaluation in Camel/Kestra (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json)
Community sourcing (`rule:jijibora:community-sourcing:v1`, v1.0.0, chain `kestra→solver-gateway`) (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json)	`platform.criteria.v1.sourcing.requirement` filter `entity_type=sourcing_requirement`, keyed `meta.tenant`+`payload.match_key` (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json)	`sourcing.match.fired` on `platform.criteria.v1.match.fired`, pipeline `pipe:sourcing:qualify-to-shortlist` stage `requirement_opened` (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json)	Terminal `shortlist` owns commands; sealed content never in match; unattested provider refused; solver only after match (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md)
MARS/ICE dispatch (`rule:jijibora:mars-ice-dispatch:v1`, v1.0.0, chain `kestra→camel`) (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json)	`platform.criteria.v1.governance.signal` filter `entity_type=emergency_incident`, keyed `meta.tenant`+`entity_id` (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json)	`emergency.dispatch.fired` on `platform.criteria.v1.match.fired`, pipeline `pipe:jijibora:mars-ice-dispatch` stage `sos_raised` (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json)	Terminal `dispatch` owns commands + PoCE; child cannot widen parent scope; public alert scrubbed fields only (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back)
Gov benefit / compensation claims packs	Exact subjects UNKNOWN in read set — see UNKNOWN table in D-02 (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back)	Guarded-transition receipt, quorum chain, evidence seal, audit export (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back)	Cross-agency quorum; officer cannot approve own file; missing evidence refused; mandatory audit export; pack cannot self-declare live (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back)
Civic maintenance pilot	UNKNOWN in read set — comprises fault + sourcing + routing + photo/GPS + inspector approval + escrow disbursement as narrative (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md)	PoCE-sealed milestone; verified escrow disbursement via M-Pesa/Stripe/bank (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)	Resolver cannot approve own close; missing triage/photo evidence refused; no payout without GPS + photo + inspector sign (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md)
Procurement tier (multi-source fill, `procurement.multi_source_fill@1`, `decision-request-v1`) (source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json)	`platform.criteria.v1.match.fired` filtered `meta.pipeline_stage=continuous_match` (source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json)	`sourcing.fill_plan` on `platform.criteria.v1.sourcing.fill_plan` or `sourcing.fill_infeasible` on `platform.criteria.v1.sourcing.fill_infeasible`; `min_score 0.8`, `min_suppliers_then_score` (source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json)	Solver `:3070` down → 503/invent_refuse, no OPTIMAL fake; engine-down refuse in Soft (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md)
Audit-file assembly	UNKNOWN in read set (assembles PoCE receipt + photo/GPS/lab + PDF certificate) (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md)	Verified photo-backed compliance report; PDF certificate via Gotenberg; Superset budget-vs-actual (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)	No payout/file without photo + GPS + inspector sign; honest empty if compose unmet (source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md; source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md)
Citizen notifications	UNKNOWN headless subject in read set (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)	Kutuma reminders (SMS/WhatsApp/email); Matrix + Kutuma announcement/gate-pass/poll templates from NATS KV EN/SW/FR (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)	Tenant-scoped + APF + audit + break-glass (dual approval, TTL) are Starter Pack non-negotiables (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)
AI hooks (advisory)	Optional enrichment stage hooks (CLAIMAI-00, tracking) (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md)	Proposal/narrative/citation only; core path works with hooks empty; no second runner (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md)	Never auto-APPROVED; manager/board approve; no autonomous award/payout (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md)
Industrial / local-content gate	UNKNOWN headless subject in read set (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back)	Local-content verdict receipt + award decision receipt (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back)	Authority verdict required before award; missing verdict blocks; threshold declaratively changeable (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back)

Cross-cutting pull rules (apply to every pack): do not invent a second event bus or envelope; extend the ontology normalizer to a shared pack helper; Soft = outbox + allowlisted subject, LIVE = JetStream + ceiling; solver only after match, invent_refuse if :3070 down (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md). Pack KV lookups must declare canonical_subject, canonical_event_type, pipeline_id (TODO in read set) (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md). No bespoke tables: new community = new CNS entries + interface catalog + manifest + fragments + APF vocab, zero schema changes; if a new table is needed, STOP AND ASK (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md).

Open items / gaps

Headless subjects for gov claims, audit assembly, credit/reminder anatomy, local-content gate, and civic-maintenance stages are UNKNOWN in the read set — no sourced consumes/emits subjects were provided for those packs (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
ESP-02 (canonical subject fields in KV lookups), ESP-03 (generalize ontology normalizer), ESP-04 (Soft outbox + ceiling assert), ESP-05 (estate-flood Soft voyage sharing correlation_id), ESP-08 (hierarchy-aligned ACL), ESP-10 (SSE client catalog), ESP-11 (Flink candidates per stage) are TODO/TRACKING — the corresponding contracts above are Soft-design, not live-proven (source: docs/commercialization/33_EVENT_SPINE_PLAYBOOK_BACKLOG.md).
REAL money movement (Estate Safe, Materra AMCOS, claims pilot) reports meters/prices, but live disbursement is gated until finance keys, a human approver, and the payments ledger are ready; real-money gates FCT-18, INTRQ-20, FINMON-16 remain OPEN-OPS (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: D-17 — Backlog Validation (platform-map recommendations)).
Starter Pack timeline: maintenance desk + dues + gates + Akili are the Month 0–3 start; standing orders, escrow-for-capex, solver routing, and Federation are Month 3–6 adds; Care (US), EUDR evidence pack, FedRAMP High are Month 6+ defers (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md).
Emergency-call location formatting and trusted timestamping require a PSAP/TSA customer; they are not promised in the Starter Pack (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: D-17 — Backlog Validation (platform-map recommendations)).
Pilot exit criteria (95% tickets digital, dues +15pp, audit recompute) are customer-defined and unpublished until baseline is measured — no savings promise is made at sale (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).