Skip to content

Latest commit

 

History

History
106 lines (83 loc) · 4.2 KB

File metadata and controls

106 lines (83 loc) · 4.2 KB

Gitbot Fleet Roadmap

Current State

Gitbot Fleet coordinates 11 bots through a shared-context system with safety-triangle-aware routing. The fleet-coordinator dispatches findings from Hypatia scans to specialised bots based on confidence thresholds (Eliminate >= 0.95, Substitute >= 0.85, Control < 0.85).

Fleet roster (11 bots):

Bot Purpose Has Roadmap

rhodibot

Git operations, RSR enforcement

Yes

echidnabot

Quality verification, multi-prover

Yes

sustainabot

Dependency management

Yes

glambot

Presentation, badges, formatting

Yes

seambot

Integration seam maintenance

Yes

finishingbot

Completion of partial work

Yes

panicbot

Security scanning (panic-attack)

No (uses panic-attack roadmap)

gsbot

Git-seo, discoverability

Yes

accessibilitybot

Accessibility compliance

Yes

cipherbot

Cryptographic hygiene

Yes

the-hotchocolabot

Developer experience, warmth

Yes

Infrastructure:

  • fleet-coordinator.sh — orchestration layer

  • dispatch-runner.sh — JSONL manifest execution

  • shared-context/ — Rust crate for inter-bot communication

  • robot-repo-automaton — Rust CLI for scan/fix/PR creation (~5% complete)

  • Hypatia scanner integration (~78% failure rate, needs work)

v1.0.0 — Foundation Stabilisation (In Progress)

  • ✓ Fleet coordinator shell orchestration

  • ✓ Dispatch runner with JSONL manifests

  • ✓ 7 fix scripts for eliminate-tier patterns

  • ✓ Shared-context Rust crate for inter-bot communication

  • ✓ Safety triangle routing (Eliminate/Substitute/Control)

  • ✓ Health monitoring (660 lines)

  • ✓ 11 bots deployed with individual roadmaps

  • ✓ Bot modes for echidnabot (Verifier/Advisor/Consultant/Regulator)

  • ❏ Hypatia scanner reliability (reduce 78% failure rate to < 10%)

  • ❏ Fix scripts/submit-finding.sh jq merge failure (array + object) blocking finding ingestion from Hypatia (Issue #46: #46)

  • ❏ Robot-repo-automaton: confidence threshold system

  • ❏ Robot-repo-automaton: integration tests with fleet coordination

  • ❏ End-to-end integration tests across full workflow

v1.1.0 — Robot-Repo-Automaton Maturity

Robot-repo-automaton is currently at ~5% completion. This milestone brings it to production.

  • ✓ License migration to PMPL-1.0-or-later

  • ✓ Hypatia module renaming

  • ❏ Hypatia integration (currently ~10% — HIGH BLOCKER)

  • ❏ Confidence threshold decision logic for auto-fix

  • ❏ End-to-end testing with Hypatia rules engine

  • ❏ Finding publication to shared-context

  • ❏ Production deployment to hyperpolymath repos

  • ❏ Learning loop: findings → observed-patterns → rules

v1.2.0 — CI/CD Pipeline Integration

  • ❏ GitHub Actions integration for automated fleet runs

  • ❏ GitLab CI integration via mirror workflows

  • ❏ Scheduled fleet scans (cron-based)

  • ❏ PR-triggered scans with bot comments

  • ❏ Status checks: block merge on Eliminate-tier findings

v1.3.0 — Observability and Analytics

  • ❏ Self-healing and auto-recovery for bot failures

  • ❏ Advanced analytics and metrics dashboard

  • ❏ Bot dependency graph visualisation

  • ❏ Fleet-wide finding aggregation and trending

  • ❏ Load testing and stress testing under org-scale workloads

  • ❏ VeriSimDB persistence for fleet metrics

v2.0.0 — Intelligent Fleet

  • ❏ Echidnabot: proof verification of scan claims

  • ❏ Learning loop integration with Hypatia across all bots

  • ❏ Cross-bot coordination: bots trigger downstream bots on findings

  • ❏ Campaign system for fleet-wide remediation drives

  • ❏ PanLL dashboard panels for fleet status and findings

  • ❏ Groove protocol integration for inter-service communication

Long-Term

  • ❏ Multi-org federation: run fleet across multiple GitHub organisations

  • ❏ Bot plugin system: third-party bots with safety-triangle compliance

  • ❏ Formal verification of safety-triangle routing logic (via proven)

  • ❏ Chapel distributed execution for multi-machine fleet coordination