Roadmap

The initiatives follow the dependency order. Their status, targets, and requirements live in the jjforge Project. Planning explains the IDs.

I0 to I2 have their requirements written. The epics of I3 to I7 get their requirements when their initiative starts.

• I0 Foundations
  • E01 Planning and docs
  • E02 Contract first
  • E03 Module boundaries
• I1 Identity and access
  • E04 Human login
  • E05 Authorization baseline
  • E06 Agent and workload principals
  • E07 Scoped tokens
  • E08 Secrets
  • E09 Audit log
• I2 Browse jj repos (MVP)
  • E10 Orgs and repos
  • E11 Ingest through the git bridge
  • E12 History
  • E13 Files and diff
  • E14 Web browsing
  • E15 CLI
• I3 Review and land
  • E16 Review rounds
  • E17 Stacks and landing queue
  • E18 Conflicts as work items
• I4 Native sync
  • E19 Spike: jj-cli and non-git remotes
  • E20 Object store
  • E21 Sync protocol
  • E22 Change ownership and push policy
• I5 Events and automation
  • E23 Operation log as events
  • E24 Gates and observers
  • E25 Sandboxes
  • E26 Durable workflows
  • E27 Quotas and budgets
• I6 Components
  • E28 Registry and catalog
  • E29 Install as grant
  • E30 Supply chain
  • E31 Configuration as code
• I7 Specs and measurement
  • E32 Measurement store
  • E33 Spec trace
  • E34 Experiments and promotion
  • E35 Metering

Not on the backlog yet

These stay here until I2 ships: the build cache and remote execution, the artifact store, issue tracking inside the forge, and an AI panel in the web app.