Skip to content

ROADMAP.md

Latest commit

 

History

History
69 lines (54 loc) · 5.34 KB

ROADMAP.md

File metadata and controls

69 lines (54 loc) · 5.34 KB
Raw

FlyBot — Roadmap

What the project is doing now, in what order, and what it deliberately is not doing. The plan of record is the accepted proposal #1550 (approved by the owner on 2026-10-29, recorded in decisions/2026-10-29-stage-1-approved.md). This page tracks that plan; it does not replace it.

Active stage: Stage 1 — run FlyBot development as an AI-governed Project (dogfood first).

Priorities today

  1. Stage 1 dogfood, in slices. Prove the governance loop with the Bots, groups, tasks and GitHub this repository already has. No new UI and no engine work until Stage 1 is shown to work.
  2. Keep the routine pipeline green and honest. tests-ok green at the tip, the gates in AGENTS.md applied as written, and the daily release published.
  3. Security debt first among ordinary work: #9 → #10 → #8.
  4. Lessons become standards. A failure seen three times is dated in LESSONS.md; after at least three days the durable rule is promoted into docs/code-standards.md or AGENTS.md.

Stage 1 — active

Objective: prove project governance and decisions with existing Bots, Tasks, groups and GitHub, before rebuilding the interface or the engine.

Slice State Where
Publish the minimal Project State (PROJECT.md, ROADMAP.md, docs/governance.md, decisions/) delivered by #1680 this page, PROJECT.md, docs/governance.md, decisions/
Chief's severity triage and escalation, in operational wording open — next docs/governance.md describes the target; Chief's routing text and the escalation template are still to be written
A recorded disagreement / reclassification case recorded by #1690 decisions/2026-10-29-stage-1-dogfood.md: Triage set needs-human on #1550 on 2026-10-28; the owner reclassified it on 2026-10-29 and the label came off
A recorded major decision taken end-to-end: proposal → Chief classification → maintainer discussion and consensus → archived decision → executable issues partly demonstrated by #1550 itself #1550, decisions/2026-10-29-stage-1-approved.md
Capture what Chief could automate and what still needed a human open to be written into the Stage 1 close-out record

Stage 1 acceptance (from #1550): use a real major design issue to demonstrate proposal → classification and research → maintainer discussion and consensus → archived decision → executable issues, including a disagreement or reclassification case. No pull request for the architecture proposal itself before authorization.

Stages 2–5 — plan of record, not started

Stage Objective State
2. Project as the work and knowledge boundary one unified Project view without duplicating task stores; role-aware owner/maintainer/member views; a shared Project State reader; a limited user–project assistant identity not started; no code
3. Handoff-controlled Workflow and isolated pool workers agree the typed Task/Handoff contract; role pools, ephemeral isolated workers, quotas, lease and recovery; strict DAG stays an option not started; contract not agreed
4. Chief meetings and Project Assistants in live collaboration temporary AI/human meetings for unresolved issues, archived decisions with dissent, personalized daily digests not started
5. RSI / autonomous project evolution research placeholder only gated. No development, no agent-queue assignment and no performance claim until a separate proposal defines the optimization objects, evaluation criteria, safety boundaries, experiments and measurable acceptance tests

Stages 2–4 are implementation direction, not approved work items: each stage becomes work only when the owner approves its scope and it is split into reviewable issues. Stage 5's gate is unchanged by Stage 1's approval.

Not doing now

  • No complete new UI for a Project console, and no rewrite of the existing DAG engine.
  • No second task board and no new scheduler; existing boards, groups and GitHub stay the only stores.
  • No knowledge-graph or vector-memory platform.
  • No autonomous change of the mission, and no unreviewed expansion of Bot privileges.
  • No change to AGENTS.md as part of a roadmap edit: the operating contract is linked, not copied here.

How this roadmap changes

Editing this page is a major decision: the owner or a human maintainer concludes it, and the outcome is recorded in decisions/ with its evidence, participants and dissent. A stage moving from "not started" to "active" is itself a decision, not an edit alone.