Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
81 changes: 49 additions & 32 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,60 +15,77 @@ The hosted product should monetize managed reliability and trust continuity: dur

## Milestone 1: Honest Self-Hosted Adapter

Goal: a motivated user can run the adapter and understand exactly what works.
Goal: a motivated user can run the adapter and understand exactly what works. **Shipped** — tracked as closed backfill issues #20–#24.

- Implement issue assignment, label, issue mention, and PR review comment triggers.
- Enforce webhook HMAC validation and bot self-comment suppression.
- Enforce worker timeout behavior.
- Keep README status honest about implemented, partial, and planned capabilities.
- Publish security, isolation, self-hosting, hosted-vs-self-hosted, and familiar contract docs.
- Implement issue assignment, label, issue mention, and PR review comment triggers. (#20)
- Enforce webhook HMAC validation and bot self-comment suppression. (#21)
- Enforce worker timeout behavior. (#22)
- Keep README status honest about implemented, partial, and planned capabilities. (#23)
- Publish security, isolation, self-hosting, hosted-vs-self-hosted, and familiar contract docs. (#24)

## Milestone 2: Hosted Control Plane

Goal: support real hosted installations without losing task state or leaking tenant context.

- Persistent task store.
- Durable queue.
- GitHub delivery idempotency.
- Installation-scoped familiar routing.
- Tenant-scoped task API auth for Cave.
- Task audit log and terminal states.
- Marker-backed GitHub status comments that are edited in place per task.
- Maintainer command router for status, stop, retry, explain, and approve.
- **Branch Gardener** — scheduled branch hygiene skill: classify branches, delete dead ones, open draft PRs for PRless work, report to Cave. See [`docs/branch-gardener.md`](docs/branch-gardener.md).
- Persistent task store. (#2)
- Durable queue. (#2)
- GitHub delivery idempotency. (#2)
- Installation-scoped familiar routing. (#7)
- Tenant-scoped task API auth for Cave. (#3)
- Split agent read auth from publication write auth. (#4)
- Hosted familiar memory governance contract between coven-github and coven-code. (#6)
- Task audit log and terminal states. (terminal states #2; audit controls #12)
- Marker-backed GitHub status comments that are edited in place per task. (#13)
- Maintainer command router for status, stop, retry, explain, and approve. (#13)
- **Branch Gardener** — scheduled branch hygiene skill: classify branches, delete dead ones, open draft PRs for PRless work, report to Cave. See [`docs/branch-gardener.md`](docs/branch-gardener.md). (#14)

## Milestone 3: GitHub Correctness

Goal: make the GitHub App reliable across normal repositories.

- Resolve repository default branch through the GitHub API.
- Resolve Check Run head SHA instead of using placeholders.
- Use the repo default branch for PR base and session brief.
- Capture review-comment diff hunk context.
- Resolve repository default branch through the GitHub API. (#9)
- Resolve Check Run head SHA instead of using placeholders. (#8)
- Use the repo default branch for PR base and session brief. (#9)
- Capture review-comment diff hunk context and structured review output. (#11)
- Add transient GitHub API retry classification.
- Add webhook fixture tests for all supported triggers.
- Implement PR, push, and commit review triggers with webhook fixtures. (#10)
Comment on lines +49 to +51

## Milestone 4: Hosted Worker Fleet

Goal: make familiar execution safe enough to charge for.

- Containerized worker backend.
- CPU, memory, disk, network, and timeout limits.
- Workspace cleanup guarantees.
- Token redaction and secret handling tests.
- Usage metering by installation, repo, familiar, and task runtime.
- Tier limits and concurrency controls.
- Containerized worker backend. (#5)
- CPU, memory, disk, network, and timeout limits. (#5)
- Workspace cleanup guarantees. (#5)
- Token redaction and secret handling tests, artifact retention, and audit. (#12)
- Usage metering by installation, repo, familiar, and task runtime. (#15)
- Tier limits and concurrency controls. (#15)

## Milestone 5: Monetization Surface

Goal: make the value legible and buyable.

- `opencoven.ai/github` landing page.
- Hosted beta waitlist.
- Pricing: Community, Hosted Starter, Hosted Team, Hosted Dedicated.
- Cave dashboard for task history, familiar routing, usage, and audit events.
- Demo assets: issue assignment to Check Run, draft PR back to issue, Cave oversight intervention.
- A reference demo showing the ClawSweeper-style operating loop: one visible status, explicit steering commands, durable audit trail, and familiar-specific PR output.
- `opencoven.ai/github` landing page and hosted beta waitlist. (#16)
- Pricing: Community, Hosted Starter, Hosted Team, Hosted Dedicated. (#17)
- Cave dashboard for task history, familiar routing, usage, and audit events. (#18)
- Demo assets: issue assignment to Check Run, draft PR back to issue, Cave oversight intervention. (#19)
- A reference demo showing the ClawSweeper-style operating loop: one visible status, explicit steering commands, durable audit trail, and familiar-specific PR output. (#19)

## Build Sequence & Dependencies

Native GitHub "blocked by" relationships gate these issues; the sequencing tracker (#25) holds the full DAG. Critical path:

`#2 → #4 → #10 → #13 → #19` — durable queue → auth split → review triggers → command protocol → reference demo.

Build waves (topological):

- **Wave 0 — foundation:** #2 unblocks all of M2/M3/M4. #16 and #17 are parallelizable with no code dependencies.
- **Wave 1 — unblocked by #2:** #3, #4, #5, #8, #9, #11, #14.
- **Wave 2:** #10 (needs #4); #6, #7, #15 (need #3); #12 (needs #5).
- **Wave 3:** #13 (needs #10); #18 (needs #3 and #12).
- **Wave 4:** #19 (needs #13).

#2 is the single chokepoint: every M2/M3/M4 engineering issue — including all four hosted paid gates (#5, #3, #7, #6) — sits within two hops of it. Sequence #2 first.

## Current Focus

Expand Down
Loading