Starter bundles — what you can adopt first, and what comes later
Scope: The starter bundle catalogue in plain language, organised by stage of adoption: the four day-1 bundles the sources name, the five expansion bundles that are not yet catalogued, and entity storage — the one shared place where every city thing is kept once, named once, and remembered once — as the land and history backbone under every bundle. Each bundle is a repeatable business process, not a custom build (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Status: as of 2026-11-09 Blueprint sources: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; Playbook Registry — What You Can Run, Who Runs It, What You Get Back; S-01 — Overview (plain language)
What this means for you
You start small and grow on the same foundations — nothing is moved or rebuilt when you expand. In the source wording, every expansion is a fragment activation on the same shared foundations, with no move of existing records: in plain words, a later bundle switches on more of what you already have, the data model does not change, and it is not a new contract family (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). The described order is starter first, then escrow for a capital project, then weather-reactive orchestration, then federation across estates (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Catalogue numbers exist for the four day-1 bundles below; the five expansion names are provisional placeholders, not catalogue numbers. The expansion table therefore says, row by row, what is UNKNOWN rather than presenting a placeholder name as a promise (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Details
Stage 1: Day-1 bundles
| Bundle | What it ships (plain-language contents) | Who it's for | What's deliberately out of it |
|---|---|---|---|
| Jamii Starter — the community starter | The starter desk in three parts: a maintenance desk that takes a resident's report by messaging app, text-menu phone service, or mobile app, classifies it, proposes the nearest certified vendor for a manager's one-tap approval, verifies the fix with photo and position proof, and holds money in escrow — money held until proof arrives — until the fix is sealed; a financial desk that tracks dues, fines, service charges, and vendor payables, sends reminders, and issues a monthly statement; and a community desk for announcements, gate passes, visitor logs, polls, light proposals and votes, and an assistant that answers from community documents in English, Swahili, and French (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). The community starter is named in the registry as the starter half of the Estate Safe bundle (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). | Estates and housing communities buying a first deployment; the flagship product in the sources is for estates, homeowners' associations (HOA), and similar communities (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). | Full orchestration — standing orders and solver routing, the last being the automatic assignment of the nearest suitable crew — is excluded from the starter pack; emergency dispatch and clinical features are later add-ons; federation across estates is later still; and capital-project escrow is a separate contract (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). |
| Claims Orchestration pilot | An umbrella offer bundling motor-claim handling with a provider panel, service-level times, approval bands, intake forms, and lifelong vehicle or building identity (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). The motor work itself is: first-notice intake from a plate or vehicle number, assigning an adjuster and garage, evidence checks, an amount decided by approval band and risk, a service-level clock, and settlement (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). The person who creates a claim cannot approve their own claim, missing evidence is refused, and a provider who is not on the approved panel is refused (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). | An insurer, health-plan, or government desk buying the pilot (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). | A published price and any savings promise — the pilot price is unpublished until a baseline is measured and no savings figure is promised (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Live operation before real checks pass — live sign is given only when real checks pass, and packs run first as a practice check (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Which other claim types sit inside this one bundle is UNKNOWN in the read sources beyond the bundled motor pack (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). |
| Estate Safe | The Jamii community starter plus the community guard, as one bundle under one subscription (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). A child's subscription cannot be widened beyond the parent's, and the revenue split behind the bundle stays visible as a pinned profile (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). | A homeowners' association (HOA) or estate manager (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). | Explicit exclusions for this bundle are UNKNOWN in the read sources; what is described is the pairing itself — starter plus guard under one subscription — with the child's subscription fenced at the parent's limits, and an entitlement receipt per estate in return (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). What the short name for the guard stands for is UNKNOWN in the read sources, so this note does not expand it (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). |
| Materra AMCOS pilot | A different job from estate maintenance: a farmer registry, field forms, certified bags, market prices, and a cooperative organisation (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Usage is metered per certified bag and revenue follows the Materra pilot split — "honesty over volume" (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). | A farming cooperative — called AMCOS in the sources — run with a union operator (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). | Explicit exclusions for this bundle are UNKNOWN in the read sources; what is described is the field job above, with a bag meter receipt, a union wallet split receipt, and a cooperative report in return — not estate maintenance (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). |
Across all four day-1 bundles, real money movement remains gated until finance keys, a human approver, and the payments ledger are ready, and every pack runs first as a practice check and cannot declare itself live (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
Stage 2: Expansion bundles — pack definition in progress / provisional
| Bundle (provisional name) | What it ships (plain-language contents) | Who it's for | What's deliberately out of it | Status |
|---|---|---|---|---|
| Ontology / Reflex Management Pack | UNKNOWN in the read sources. The closest expansion the sources do describe is the orchestration product — standing orders, predictive models, and emergency mode for facilities directors who own pumps, generators, gates, and similar systems — but the sources do not equate that product with this provisional name (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). | UNKNOWN in the read sources | UNKNOWN in the read sources | Pack definition in progress / provisional — placeholder name only (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md) |
| Event-Sourcing Management Pack | UNKNOWN in the read sources. The related facts the sources do describe are: rules live in one editable place separate from the software, every change leaves a dated receipt, and packs run first as a practice check before live — but those facts are not presented as this pack's contents (source: S-01 — Overview (plain language); source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). | UNKNOWN in the read sources | UNKNOWN in the read sources | Pack definition in progress / provisional — placeholder name only (source: S-01 — Overview (plain language)) |
| Civic Maintenance full lifecycle | UNKNOWN in the read sources as a separate bundle. The maintenance steps the sources do describe — report, dispatch, verified close, escrow hold — are already in the day-1 starter desk, and recurring automatic work is described only as the later standing-orders expansion (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md; source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md). | UNKNOWN in the read sources | UNKNOWN in the read sources | Pack definition in progress / provisional — placeholder name only (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md) |
| Community desks | UNKNOWN in the read sources as an expansion distinct from the starter desk. A community desk — announcements, gate passes, light proposals and votes, and document-based answers — is already inside the day-1 starter pack, so what an expansion version would add is not described (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). | UNKNOWN in the read sources | UNKNOWN in the read sources | Pack definition in progress / provisional — placeholder name only (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md) |
| Emergency Guard | UNKNOWN in the read sources, including whether it is the same thing as the community guard paired inside Estate Safe or as emergency dispatch. Emergency dispatch is described as a deferred add-on outside the starter pack, and a community guard is described only as paired inside Estate Safe; neither is equated with this provisional name (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). | UNKNOWN in the read sources | UNKNOWN in the read sources | Pack definition in progress / provisional — placeholder name only (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md) |
How the two stages relate. Every expansion above, once defined, is expected to follow the same rule as the described ladder: switched on on the same shared foundations with no move of existing records, in the order starter, escrow for a capital project, weather-reactive orchestration, then federation (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). Whether the five provisional names above map one-to-one onto that order is UNKNOWN in the read sources (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md).
Entity storage as the smart-city backbone: land and history
Entity storage — the one shared place where every city thing (a building, a parcel, a person, a crew, a vehicle, a sensor station) is kept once, named once, and remembered once — is the backbone all four bundles stand on; it is not a fifth bundle, and the sources do not catalogue a land bundle (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: S-01 — Overview (plain language)). A parcel is one piece of land with a boundary and an owner or occupant; a timeline is the dated history kept under its one name.
Land usage. The backbone picture puts parcels in a ladder — municipality, then estate, then block or building, then unit or parcel — with land-use types (what the land is for) kept as values on the parcel, and applications, disputes, and assessments attached as the parcel's claims and dated history (source: S-01 — Overview (plain language)). That exact ladder, any land-use type list, and any parcel-attached application, dispute, or assessment are UNKNOWN in the read sources; what is in scope is narrower — construction permits are named as one kind of work the same shared engine can run, with the kind of work a setting rather than a different system — and building-based claims and a lifelong building history summary are sourced for buildings, not parcels (source: S-01 — Overview (plain language); source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). The smart-city uses of a parcel — a zoning check before a permit, use-change history, an occupancy link to who lives or works there, ground-service route planning along streets and facilities, and a public land audit — are UNKNOWN as described workflows in the read sources; their closest anchors are claims that carry stage, people, and receipts, building history shared only for a stated purpose within a time limit (a time-limited lease, in plain words), and the maintenance flow's selection of the closest qualified technician with exact location and materials (source: S-01 — Overview (plain language); source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
Entity history. The promise is one continuous timeline per city thing — changes, other names it has carried (aliases, in plain words), attached photos and papers, and time-limited permissions — with every claim resolving to one of those things, so "who owned what day by day" stays answerable from the thing's own timeline (source: S-01 — Overview (plain language); source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back). Sourced is the pattern: history is the product, every change leaves a receipt, and lifelong vehicle and building identity is bundled in the claims pilot. One timeline covering all six kinds of city thing together, and the exact claim-to-thing rule, are UNKNOWN in the read sources (source: S-01 — Overview (plain language); source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
What this buys you, in buyer words. Land records that update once and reach every desk: information entered once updates all municipal desks at the same time, as in the pump story in the town registry source (source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). And history that makes audits straightforward: money moves only on photo, on-site position proof, and an inspector's signature, and weeks of manual audit assembly become an export (source: S-01 — Overview (plain language); source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md). The zoning dispute story — illustrative, not a sourced workflow: an application filed today and a resolution tomorrow both land on the same parcel file, with receipts in order, so the parcel remembers both. Whether that workflow exists today on those terms is UNKNOWN in the read sources — ask for it by name before signing (source: S-01 — Overview (plain language)).
Open items / gaps
- Contents, buyers, and exclusions for all five expansion bundles are UNKNOWN in the read sources; treat every expansion name as a provisional placeholder, not a catalogue offer (source: docs/jijibora-gtm/02_PRODUCT_STRATIFICATION.md; source: docs/jijibora-gtm/03_ENTRY_POINT_AND_STARTER_PACK.md).
- Explicit exclusions for the Estate Safe and Materra AMCOS bundles, and the wider contents of the claims pilot beyond the bundled motor pack, are UNKNOWN in the read sources (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
- No price or savings figure is stated in this catalogue; the claims pilot price is explicitly unpublished until a baseline is measured and no savings is promised at sale (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
- Real money movement for Estate Safe, Materra AMCOS, and the claims pilot remains gated until finance keys, a human approver, and the payments ledger are ready (source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).
- Land backbone items — the parcel ladder, land-use types, parcel-attached applications, disputes and assessments, zoning checks, occupancy links, ground-service route planning, and public land audit — are UNKNOWN in the read sources, as is one continuous timeline covering buildings, parcels, people, crews, vehicles, and sensor stations together (source: S-01 — Overview (plain language); source: Playbook Registry — What You Can Run, Who Runs It, What You Get Back).