JJijibora Docs
docs.jijibora.online
On this page (15 sections)

D-04 — Environmental Playbooks (developer)

Scope: Design contracts for the environmental playbook families — intent, observed trigger sets, evaluation chains, actuation surfaces, guard rails, evidence left behind, and versioning behaviour — for developers building or integrating playbooks. 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/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json; S-03 — Jijibora Playbook Registry (stakeholder + developer); docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; 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

Every environmental family is declarative data on a shared spine: one subject family in, one standard fired notice out, with a bounded depth and a terminal-only actuation step. You declare a new variant with new names and fragments plus a fresh version mark — you do not write new storage primitives and you do not read lookup files from disk at runtime.

Details

Building reflex

Intent. A named building reacts to its own state change — a sensor or a resident report — by a pre-agreed sense-reason-actuate arc, without human glue-work (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Observed trigger set. Subject platform.criteria.v1.building.entity_state, predicate entity_type = building, keyed by tenant plus entity (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json). Pipeline stage is sense, maximum depth eight, non-terminal (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json).

Evaluation chain. Kind criteria, engine tgc, keyed meta.tenant + entity_id; runtime tier one with a two-step chain via orchestration then protocol translation (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json). Promotion to the stream-join job happens when fan-out warrants (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Actuation surface. Terminal actuation only: side effects are handled by a terminal handler; non-terminal stages emit criteria only (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json).

Guard rails. Terminal-only commands refuse non-terminal attempts; ceiling refuses a child that widens the parent promise; a long chain stops and asks a person to review it; AI proposes and a human approves at decision gates (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Live evaluation lives in the engines; storage is record-only (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json).

Receipt and evidence. Fired notice building.reflex.fired on a standard fired subject with cause inherited; the audit keeps a proved reflex trail. Exact receipt shape beyond that notice is UNKNOWN in the read set (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Versioning and evolution. Rule identity embeds name plus major version; semantic version on the design; value thresholds change via declarable entries, not code; promotion to a stream join is by declaration plus job activation (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Community sourcing

Intent. A sourcing requirement is qualified and shortlisted against pre-vetted local candidates, only from the approved register (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Observed trigger set. Subject platform.criteria.v1.sourcing.requirement, predicate entity_type = sourcing_requirement, keyed by tenant plus a match key; companion subject for candidate state with entity_type = candidate for continuous matching (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json). Pipeline stage requirement_opened, maximum depth eight, non-terminal (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json).

Evaluation chain. Two engines in sequence where needed: criteria qualification via the flow chain, then optimizer allocation; continuous matching is a tenant-plus-match-key join with a minimum score of 0.8 (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json). Quantities across multiple suppliers run through a multi-source fill after a real shortlist exists (source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json).

Actuation surface. Shortlisting and allocation of awards are downstream of a fired notice; terminal shortlist handling owns commands (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json).

Guard rails. Qualification plus optimizer before any shortlist; sealed content never travels in a match; unattested providers are refused; optimizer down refuses with 503 and never invents an allocation; matching fails closed to manual assignment when the network cannot run (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Receipt and evidence. Fired notice on the standard fired subject with cause inherited; a privacy-safe match transcript and a bind receipt (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). Fill plans and explicit infeasibility are distinct outcomes (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Versioning and evolution. Tier one ships as version one; continuous matching promotes to a stream join job as its sole matcher with no parallel Camel evaluator (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md). New variants change the subject filter and match key declaratively (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Civic maintenance recurring

Intent. Standing orders recur on their own clock: a watched state crossing a limit fires a pre-agreed checklist without re-typing (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

Observed trigger set. Normalized inventory or entity state change; predicate is the order's breach criterion evaluated per affected order (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). A companion drill stream uses criteria watchers for facet matches which downstream stages may consume (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Evaluation chain. Hot path observes state, evaluates breach per affected order, emits a breach assessment, then issues a fire command only when breached and not in cooldown; recovery sweep exists only as recovery (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). The five-step civic flow is fault, then fair sourcing, then scheduling, then photo-or-arrival-point proof, then verified disbursement (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Actuation surface. Fire commands are handled by a projection and command handler that updates the order record idempotently; escalation handling owns tickets, notifications, and proof (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json).

Guard rails. Breach requires both a true criterion result and an inactive cooldown; a child rule cannot widen the parent promise; missing sorting checks or missing viewer evidence is refused rather than guessed; resolver cannot approve their own close; no payout without arrival point plus photo plus inspector sign (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

Receipt and evidence. Breach assessment and fire command each leave a causal record sharing the correlation identifier; completion seals the milestone before any money moves (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Exact calendar cadence values are UNKNOWN (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Versioning and evolution. Version by design version plus pipeline identity and fragment lineage; never a fresh storage primitive per community — a new community is a new type, a new fragment, and vocabulary (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

Geofence / SCE proximity

Intent. Place-based evaluation lets a building or a crew react on entering or leaving a boundary — a capability the sources name but do not fully specify.

Observed trigger set. Thin: emergency shelter logic names geofence-style evaluation as part of the emergency surface; the community-truth and knowledge layers name single shared identities for assets, roads, and drains that a proximity rule would anchor to (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Subjects, predicates, and thresholds for a proximity family are UNKNOWN in the read set (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Evaluation chain. UNKNOWN beyond monitoring claims: the sources name translation plus orchestration as the chain for reflexes, but no sourced proximity design shows the steps beyond that (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Actuation surface. UNKNOWN in the read set (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Guard rails. No widening beyond the parent ceiling; scrubbed location only in public notices; humans close incidents (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: A-02 — Jijibora Compliance Operations (Administrator)).

Receipt and evidence. UNKNOWN in the read set beyond emergency match receipts (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Versioning and evolution. UNKNOWN in the read set; treat any proximity design as design-only until a rule example appears (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Civic claim adjudication (benefit and compensation resolution)

Intent. Decide a citizen application or a loss claim under quorum plus separation of duties: a second agency or officer, evidence sweep, dual approval, payment readiness (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Observed trigger set. Headless subjects are UNKNOWN in the read set (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Evaluation chain. Zero-write practice check first; desks run the pack under quorum with separation of duties; a claim desk and readiness handling (infrastructure-ready versus rollout-enabled) gate live use (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Actuation surface. Guarded transitions that mint receipts and seals; a pack cannot declare itself live (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Guard rails. Cross-agency quorum; an officer cannot approve their own file; missing evidence is refused; mandatory audit export; fixture metrics excluded by default (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md). The verified escrow step is no sign-off, no payout — photo plus arrival point plus inspector sign before any disbursement (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Receipt and evidence. Guarded-transition receipts, a quorum chain, an evidence seal, an audit export for benefit; a decision pack plus evidence seal plus approval receipt for compensation (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Versioning and evolution. Claims spec version and interface contract version are recorded against the pack; readiness is environment-gated, not a code branch (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

SOS dispatch including proof-of-correct-execution bridging

Intent. A distress signal fans out to named responders per the pre-approved cascade, and each governed step writes its own proof session (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Observed trigger set. Subject platform.criteria.v1.governance.signal, predicate entity_type = emergency_incident, keyed by tenant plus entity (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json). Pipeline stage sos_raised, maximum depth eight, non-terminal (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json).

Evaluation chain. Kind criteria, engine tgc; runtime tier one with a two-step chain via orchestration then protocol translation (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json). Extended cadence uses orchestration timers plus translation for protocol handling (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Actuation surface. Terminal dispatch only; each forked child carries its own scope and the parent ceiling bounds them (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json).

Guard rails. A child cannot widen the parent scope; public alerts are drawn only from scrubbed fields unless a purpose grant exists; decision gates keep a named human as the approver, and break-glass remains dual control with expiry and audit (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: A-02 — Jijibora Compliance Operations (Administrator)). Proof bridging covers governed paths that start a proof session — not every login, payment, or sensor (source: A-02 — Jijibora Compliance Operations (Administrator)).

Receipt and evidence. Fired notice emergency.dispatch.fired on the standard fired subject with cause inherited; an emergency match receipt, a resource assignment log, a fork-tree receipt with child-closed notices, and public alerts drawn only from scrubbed fields (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Versioning and evolution. Rule identity embeds name plus major version; semantic version on the design; new agency lists arrive via governance vocabulary, not hardcoded constants (source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Facet-notify

Intent. Environmental signals become localized notifications; sensing never auto-approves (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Observed trigger set. Subjects are scrutified facet streams (entity facets and graph facets); evaluation keys by entity, matches when scrubbed facets are present, and emits a facet-matched notice (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Evaluation chain. Tier-two stream join for continuous facet matching; lifecycle facets allow normalization to remain while evaluation retires to the stream job behind a cutover setting; volume gates decide promotion to avoid two live evaluators (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Actuation surface. Non-terminal notify; downstream pipeline stages consume the fired notice (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Guard rails. Facets only, never raw metadata; an index-scrub rule is required before matching; never auto-approved; no second runner; AI hooks stay advisory and optional (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Receipt and evidence. Facet-matched fired notices with causal inheritance; language packs live in shared storage and are versioned per key. Per-message delivery receipt shape is UNKNOWN (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Versioning and evolution. Semantic version on the design plus language-pack revisions; cutover retires the older evaluator when the new one is attested (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Garbage / collection-route management

Intent. A household overflow report triggers route replanning, a collection stop is proven on completion, and a missed stop is rescheduled — by the same intake-to-proof pattern as civic maintenance, applied to refuse-truck rounds (source: S-02 — What Jijibora Can Do for You (plain-language feature guide); source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-government-trial/05_IMPLICATIONS_AND_APPLICATIONS.md).

Observed trigger set. Thin and narrative-derived: a household report via the maintenance channel plus route-state and vehicle-state changes; headless subject names for waste, route, or stop are UNKNOWN in the read set and must not be invented (source: S-02 — What Jijibora Can Do for You (plain-language feature guide); source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). The evidenced route behaviour is sequencing — refuse-truck runs can be sequenced so markets are cleared before morning trade, and nearby road reports are grouped so a crew covers them in one trip (source: docs/jijibora-government-trial/05_IMPLICATIONS_AND_APPLICATIONS.md; source: S-02 — What Jijibora Can Do for You (plain-language feature guide)).

Evaluation chain. Follow the civic-maintenance chain with the same envelope and lifecycle honesty rules: sense a report or state change on the canonical criteria family, reason against the round checklist, and emit a standard fired notice with cause inherited (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json). Scheduling and sequencing use the optimizer only after a real shortlist exists; never invent an allocation when the optimizer is down (source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Actuation surface. Terminal-only: route replanning and rescheduling commands issue only from the terminal handler; non-terminal stages emit criteria only (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md). Rescheduling a missed stop is a new fire command that preserves the causal chain, not a silent deletion of the prior stop (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Guard rails. The same honesty rules as civic maintenance apply to fines too: a sensor, device location, or a single channel report never alone triggers a fine or certifies completion; no payout, no closure, and no penalty without arrival-point proof plus a time-stamped photo plus a sign-off by someone other than the collector, with missing evidence refused rather than guessed (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide)). A child round cannot widen the parent ceiling; serious steps remain behind named approval while routine notices go at once (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Pay-per-use for the round is a usage signal on the finance-monitoring spine, carrying subscription, wallet, or invoice identifiers and amount or rate only; money events never carry claim payloads and never advance a claim, and splits must sum exactly to the whole with two-person approval (source: D-06 — FINMON: Money Side — Billing, Desks, and Proof of Value; source: docs/commercialization/playbooks/dictionary.v1.json).

Receipt and evidence. A per-stop audit packet: household report, replanned route order, time-stamped completion photo, arrival-point confirmation, and checker sign-off, sealed before any money moves; the money-side usage signal and the proof-side receipt are kept as separate trails (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide); source: D-06 — FINMON: Money Side — Billing, Desks, and Proof of Value). Tariffs, fine schedules, and missed-stop service levels are UNKNOWN (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Versioning and evolution. Version by design version plus pipeline identity and fragment lineage; a new ward is a new type plus a new fragment plus vocabulary, never a new storage primitive, and thresholds change declaratively (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

Weather preparation (rain and flood prep ladder)

Intent. A rainfall or river-height threshold crossing fires a reversible preparation ladder — alerts, pre-positioning of sandbags, pumps, and shelter unlock under pre-authorized powers, then a post-event stand-down report — explicitly distinguished from SOS dispatch as reversible preparation versus consequential dispatch (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: S-02 — What Jijibora Can Do for You (plain-language feature guide)).

Observed trigger set. Narrative-thin: the standing-order checklist triggers on a gauge, meter, rain-station, or citizen-phone report crossing a set limit, e.g. river height above its threshold or rainfall above its threshold; headless subjects for a dedicated weather-prep family are UNKNOWN in the read set (source: S-02 — What Jijibora Can Do for You (plain-language feature guide); source: S-03 — Jijibora Playbook Registry (stakeholder + developer)). The closest evidenced design is the standing-order breach rule: normalized state change evaluated per ordered watcher, breach assessment emitted, fire command only when breached and not in cooldown (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Evaluation chain. Same honesty rules: criteria evaluation keyed by tenant plus entity (or tenant plus match key for preparatory sourcing), a bounded-depth chain, and a standard fired notice with cause inherited; recovery sweep exists only as recovery (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json). Alerts localize from shared language packs and render by text message and email (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).

Actuation surface. Two-tier, by reversibility: preparation acts (alerts, sandbag and pump staging, shelter unlock, truck diversion, drain clearing) are terminal-only but reversible and unwindable on stand-down; dispatch (named crews responding inside the community) belongs to the separate SOS family with its own governed incident and human close (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Guard rails. No widening beyond the parent ceiling in either tier; public alerts use scrubbed fields only; preparation requires the same dual control and audit whenever it crosses into break-glass territory, and humans — never the system — close incidents (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: A-02 — Jijibora Compliance Operations (Administrator)). Preparation alone never releases money: on-site staging still waits for arrival-point proof before any disbursement, same as civic maintenance (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Receipt and evidence. Fired prep notices per rung plus lake-side proof of staging (arrival-point confirmations) and a post-event standing report distinguishing staged versus used assets (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/jijibora-government-trial/04_UNIFIED_ONTOLOGY_AND_REACTIVE_GOVERNANCE.md). Forecast ingestion subjects, inventory ledger shape, and unwind timers are UNKNOWN (source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Versioning and evolution. Rule identity plus semantic version; thresholds (height, rainfall, window) change declaratively; moving a step from preparation to dispatch is a pipeline and vocabulary change, not a code branch (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).

Low-resource cross-cutting (offline-first, USSD and WhatsApp only, mobile-money-first, pay-per-use, multilingual)

This is not a new family; it is a constraint set every family above already satisfies or marks UNKNOWN.

How to author the next environmental playbook

Numbered, declarative-first; copy the shape of the three Jijibora rule examples (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; source: docs/event-sourcing/rules/jijibora-mars-ice-dispatch-rule.example.json; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

  1. Reuse the spine, add nothing new. Consume a criteria subject and emit the standard fired notice with cause inherited; do not invent a second bus or envelope (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).
  2. Copy the rule shape exactly. Rule identity, name, domain, enabled switch, version, description, runtime tier and chain, pipeline identity and stage, subject inputs with filters, evaluation kind and keying, outputs, and terminal-only side effects (source: docs/event-sourcing/rules/jijibora-building-reflex-rule.example.json; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).
  3. Declare the pack first in a pack dictionary: emitted and consumed subjects, enrichment, optimizer stages, and the security bound; schema-validate before building (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).
  4. Declare every lookup with its canonical subject, canonical event name, and pipeline identity in shared storage; the seeder loads shared storage — never read lookups or templates from disk at runtime (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
  5. Place logic in the engine the tier demands: flow for criteria and reflex, stream join for continuous matching, optimizer only for allocation (source: docs/event-sourcing/rules/jijibora-community-sourcing-rule.example.json; source: docs/event-sourcing/rules/sourcing-multi-source-fill-rule.example.json).
  6. Keep side effects terminal-only: non-terminal stages emit criteria only; the terminal handler owns tickets, notifications, and proof, and publishes the receipt (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).
  7. Gate before anything live: land in practice mode with an allowlisted subject before production mode with a ceiling; drill packs never carry a production incident path; a pack cannot declare itself live (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md; source: S-03 — Jijibora Playbook Registry (stakeholder + developer)).
  8. Variant without code: a new community or a new behaviour is a new type, a new fragment, and vocabulary — children only narrow, thresholds change declaratively, AI hooks stay advisory (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md). If a design cannot be expressed as a fragment or lookup, say so before writing code (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).

Open items / gaps

  • Proximity design, claim adjudication subject sets, scenic maintenance rollout specifics, audit-file assembly subjects, waste-route and weather-prep headless subjects, and exact offline storage conventions (streaming, cache, queue, conflict handling) remain thin or UNKNOWN in this read set — evidence only up to the registry narrative (source: S-03 — Jijibora Playbook Registry (stakeholder + developer); source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).
  • Canonical subject fields in every pack lookup, a generalized ontology normalizer, ceiling asserts, and hierarchy-aligned access are still tracked as gaps — variants must land with those in mind but cannot assume them (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).
  • Trusted timestamping and public-safety formatted location exist only when an external authority customer arrives; fabric promotion candidates and a typed client catalog are still tracked as gaps (source: docs/platform-map/jijibora/D-02-PLAYBOOK-DESIGNS.md).
← BackHome — all documentationNext →Jijibora set index