# 18 — Product roadmap

## Phase A — Foundation and MVP

Outcome: a polished self-hosted application that discovers, composes and exports versioned playbooks.

Capabilities:

- built-in catalog;
- library search and filters;
- playbook detail;
- manual repository profiles;
- autonomy and guided composer;
- deterministic prompt engine;
- prompt linting;
- immutable run history;
- Markdown and Run Pack export;
- private playbook import;
- Docker/Unraid deployment.

## Phase B — Repository intelligence

Outcome: profiles become evidence-backed and recommendations become contextual.

Capabilities:

- read-only Gitea connection;
- repository discovery;
- manifest and governance detection;
- profile snapshot review;
- repository findings;
- recommended playbooks;
- integration health.

## Phase C — Authoring and quality lab

Outcome: DevRunbook becomes a professional content-development environment.

Capabilities:

- schema-aware editor;
- prompt preview matrix;
- version diffs;
- static evaluation cases;
- lifecycle promotion;
- quality dimensions;
- fixture package.

## Phase D — Codex-native exports

Outcome: recurring procedures move cleanly into Codex-native mechanisms.

Capabilities:

- AGENTS.md builder with hierarchy guidance;
- Codex Skill export;
- optional DevRunbook MCP server for search/fetch/generation;
- task deep links or compatible handoff where officially supported.

## Phase E — Controlled execution bridge

Outcome: users can launch and observe tasks without sacrificing approval and isolation.

Capabilities:

- local companion/CLI;
- worktree creation;
- exact prompt handoff;
- streaming status;
- command and result evidence import;
- cancel/retry/cleanup;
- no remote privileged execution by default.

Requires a new threat model and ADR.

## Phase F — Teams and governance

Outcome: organizations publish and enforce their own development procedures.

Capabilities:

- workspaces and roles;
- reviewers and approvals;
- policy layers;
- shared repository profiles;
- private registries;
- audit and retention controls;
- OIDC/SSO;
- signed package releases.

## Phase G — Multi-forge and ecosystem

- GitHub adapter;
- GitLab adapter;
- Forgejo compatibility validation;
- plugin/connector architecture;
- curated third-party registry;
- import from Git repositories;
- package signatures and trust roots.

## Phase H — Evaluation runner

Outcome: validated status can include isolated agent execution evidence.

Capabilities:

- disposable fixture environments;
- Codex SDK/MCP orchestration;
- protected-path diff checks;
- command evidence;
- playbook version regression dashboard;
- operator review workflow;
- cost/time reporting.

## Explicit deferrals

Do not pull these into MVP without evidence:

- vector search;
- public ratings marketplace;
- AI-generated playbooks published without review;
- Kubernetes deployment;
- arbitrary plugin execution;
- write access to Git for the web container;
- automatic merging of agent changes;
- financial/billing features.