JJijibora Docs
docs.jijibora.online
★ Sovereign OS · Smart City · Platform Map

Jijibora documentation,
complete and linkable.

The full documentation set for Jijibora — municipal, government, and community services — in one blue-and-white site. Every Markdown file under docs/platform-map is rendered as a page; every internal link resolves; every page carries its own table of contents.

City at dusk — the operating picture Jijibora documents
105documentation pages rendered
32Jijibora playbooks & designs
35API reference files
100%internal links rewritten
Connected city systems flowing togetherStakeholders

For buyers & decision-makers

What Jijibora does, what it can honestly claim, and what a pilot looks like — plain language, no jargon.

Start with the overview →
City operations control loopAdministrators

For operators

Deployment, runbooks, compliance ops, and the rulings that govern the city — how to run it safely.

Start with the deployment guide →

Includes wider scenario ops, the management plane, and governance admin.

Platform Map (non-Jijibora) stakeholders:

  • S-01 — Overview (plain language)
  • What the Commercialization Program Gives You
  • S-03 — Glossary (plain language)
  • S-04 — Week in Review (plain-language summary)
  • Playbook Registry — What You Can Run, Who Runs It, What You Get Back
  • How this site is organized

    Use the left navigation to filter all 105 pages. Each page has an “On this page” table of contents, and every [text](file.md) link in the source is rewritten to the rendered page — including #anchors for section jumps. The build is deterministic: re-run node apps/docs-jijibora/scripts/build.mjs after any change under docs/platform-map.

    Reading paths

    ReaderStart hereThen
    StakeholderS-01 OverviewS-02 Features → S-13 Wider Scenarios
    AdministratorA-01 DeploymentA-02 Runbooks → A-08 Wider Ops
    DeveloperD-01 ArchitectureD-12 Playbook Building → D-11 Spec Index
    API consumerBFF APIClaims → Sourcing

    Status at a glance

    Commercialization backlog: every buildable card is done; remaining items are ops-gated. The claims plane runs end-to-end live with a deliberately SOFT product rollout. See D-17 Backlog Validation and D-15 Honesty Invariants for the fail-closed rules every module obeys.

    Honesty note: Every fact in this set cites a source file; every uncertainty says so. No third-party product brands appear in public API responses, and runtime services never read JSON/YAML lookups from the filesystem — configuration arrives via NATS JetStream KV.