Skip to content

Epic: BoJ capability-expansion roadmap (13 items) #87

Description

@hyperpolymath

Background

Strategic-direction issue capturing the 14 on-mission gaps surfaced in the 2026-05-20 session. Update 2026-06-01: All Tier A code-items shipped except item 14 impl; all Tier B RFCs landed; Tier C remains.

BoJ's character: unified consolidation, formal verification, multi-agent coordination, trust tiers, security posture. Each item below was scored as "on-mission" rather than "could conceivably ship."

Tier A — implementable (real code)

Tier B — RFCs (design-first)

Tier C — multi-week campaigns

  • 11. Discharge last 4 believe_me axioms — proof-debt audit reduced 31 → 4 in v0.4.0. Closing the last 4 lets BoJ claim "zero unproven axioms in the ABI" — rare in the wild.
  • 12. Cross-cartridge composition proof — currently each cartridge is verified in isolation; cross-cartridge boj_cartridge_invoke is not proven-safe end-to-end. Research-grade work; JOSS-paper-shaped.

Scoring rationale

All 14 selected because they're on the BoJ character axis:

  • Items 1, 13 → first-class MCP citizen
  • Items 4, 10, 2, 3 → trust-tier + multi-agent coherence (the real ambition)
  • Items 5, 6 → bidirectional agent loop (not just request/response)
  • Items 7, 8, 9 → consolidation-mission completeness
  • Item 14 → deployment-target breadth (Workers + remote browser clients)
  • Items 11, 12 → formal-verification differentiation

What's NOT on this list (deliberate)

  • Payments / crypto cartridges — outside BoJ's character; muddies trust model
  • CRM cartridges — not on-mission; consolidation ≠ "everything"
  • More git forges (Gitea, Bitbucket, Forgejo) — git-mcp generic covers them
  • Yet-another-message-queue — queues-mcp already generic
  • Making the existing stdio bridge run in a browser/Worker — architecturally wrong; item 14 is the right framing

Sequencing rule

Status 2026-06-01: 11 of 14 done. Only item 14 (impl), 11, 12 remain.

  1. Item 14 impl (Streamable HTTP transport) — RFC already landed (ADR-0013); next biggest deployment-shape change. 2 PRs over ~1-2 weeks per ADR.
  2. Items 11 / 12 — long-running proof campaigns, no rush.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew capability or improvement to existing behaviourmeta:umbrellaParent issue aggregating child issues

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions