JiboExperiments/OpenJibo

OpenJibo

OpenJibo is the working revival track for Jibo.

We are rebuilding the hosted cloud first, then using that foundation for OTA, Open Jibo OS, and a tiered brain that can eventually hand higher-order work to CoffeeBreak without losing Jibo's original charm.

Current Focus

• ship a stable Azure-hosted replacement cloud
• keep the Node prototype as the protocol oracle and capture harness
• port the production path to .NET
• support real devices through repeatable bootstrap steps first
• use OTA later to reduce recovery friction once the cloud is trustworthy

Current release truth lives in docs/development-plan.md. The current cloud release constant is 1.0.19.

Roadmap

The long-range plan is summarized in docs/roadmap.md. In short:

1. Working hosted cloud.
2. OTA-assisted recovery and updates.
3. Open Jibo OS / open-jibo mode conversion.
4. Tiered brain and CoffeeBreak orchestration.
5. Broader ecosystem expansion.

Current Architecture

The repo now has three distinct lanes:

• src/Jibo.Cloud/node Protocol oracle, discovery server, fixture source, and rapid reverse-engineering lab.
• src/Jibo.Cloud/dotnet Production-oriented hosted implementation intended for Azure deployment and long-term maintenance.
• src/Jibo.Runtime.Abstractions The seam between robot/cloud traffic and higher-level runtime and capability logic.

The core shape is:

Jibo device -> OpenJibo cloud -> normalized runtime contracts -> capabilities and planning

First Supported Device Path

The first supported recovery path is enthusiast-friendly, not zero-touch:

QR Wi-Fi -> inject OpenJibo region config -> set robot region ->
RCM/device patch for TLS and host acceptance -> OpenJibo cloud on Azure

That path is documented in docs/device-bootstrap.md.

Design Principles

• Preserve the original skills and visual design.
• Build the hosted cloud before making OTA the default recovery path.
• Keep every migration reversible whenever possible.
• Prefer source-backed slices over speculative rewrites.
• Let Jibo remain the face of the experience, even when higher-level orchestration sits behind him.

Repo Map

OpenJibo/
  docs/
    roadmap.md
    development-plan.md
    device-bootstrap.md
    feature-backlog.md
    public-site-plan.md
    regression-test-plan.md
    release-1.0.19-plan.md
    support-tiers.md
    system-diagram-alignment.md

  scripts/bootstrap/
    Discover-JiboHosts.ps1
    Generate-JiboDnsOverrides.ps1
    Test-OpenJiboRouting.ps1

  src/
    Jibo.Cloud/
      node/
      dotnet/
    Jibo.Runtime.Abstractions/
    Playground/
    OpenJibo.Site/

Living Docs

Use these when you want the active technical truth:

• Development plan
• Feature backlog
• Release 1.0.19 plan
• Support tiers
• System diagram alignment
• Public site plan

If you only read one document for the long view, make it docs/roadmap.md.