dataqbs
News

Octorato opens to contributors: public roadmap, RFCs, and good-first-issues

Our open-source OS for AI agents — the one with a budget cap that actually halts runaway agents — just published its public roadmap and opened the door to the community.

Why it matters Anyone can contribute: 9 good-first-issues to start, 2 architecture RFCs to shape the direction, and an honest 5-milestone roadmap labeled by real maturity. We credit every contributor.

Octorato opens to the community

Octorato — our “open-source OS for AI agents” — just published its public roadmap and formally opened the door to contributors.

What makes it different?

Unlike most agent frameworks, Octorato ships FinOps with teeth: a budget cap that fires a hard PreToolUse halt when spend is blown. It’s not a dashboard that watches — it stops execution. That’s the proof-of-seriousness that earns the “OS” label.

Honest about maturity

Today Octorato is still a governance layer, not a full OS runtime. Instead of pretending otherwise, we published the gap analysis as a 5-milestone roadmap — from “convention layer” to “kernel” — each labeled with its real maturity (design / in progress / future). The hardest questions — what the kernel ABI should be, and whether Octorato should own a runtime or stay portable across harnesses — are open RFCs anyone can shape.

How to get involved

  • 🟢 9 good-first-issues (telemetry, schemas, tests — real slices of big goals)
  • 🧠 2 architecture RFCs (kernel ABI + the runtime-vs-convention fork)
  • 🗺️ a roadmap that says “future” out loud instead of overpromising

Start here 👉 Start Here — Contributing. We credit every contributor. 🐙