[dev] docs: v1 roadmap draft#32
Merged
Merged
Conversation
…s list Critical pass on the proposed v1 candidate list: ranks each item by leverage-per-effort, names the items that don't earn their weight yet, and adds three gaps the original list missed (capability scopes, cost budgets, proactive work origination). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Restructures the doc so the reasoning flows from purpose → gap analysis → themes → features, instead of starting in the middle with a ranked list of Sherod's candidates. Every feature now traces back to one of five named promises (P1-P5), and the explicit non-promises section reduces drift risk. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Homelab framing lowers the bar — implies hobby, throwaway, "good enough for me." Production sandbox names the right stakes: real cluster, real infra, real PRs, real blast radius. What makes it a sandbox is the boundary (single operator, isolated network, recoverable state), not the quality of the work. v1 has to clear the production bar, not the hobby bar. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… for it Removed the "homelab vs production sandbox" editorial from the vision section. The framing belongs in public-facing positioning (README, repo description), not as in-line commentary inside the roadmap. The doc now just speaks confidently from that posture. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Tagline: "for a k8." (truncated) → "An autonomous engineering crew that ships real work against a real Kubernetes cluster." - "Problem this solves" rewritten to frame the work as real engineering, not routine homelab chores. Surfaces the production-grade substrate (GitOps via Flux, Infisical secrets, VictoriaMetrics/Logs, egress capability scope) so readers understand bots ship to main, not toys. - Replaced "for a homelab answering dozens of messages" with "for an always-on crew" in the Claude Code CLI rationale. Technical references to the homelab repo, namespace, and manifest paths are kept — those are accurate names, not framing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ggers Replaces "What v1 explicitly does NOT promise" with "Future considerations" — same content, forward-looking framing. Each item now names the trigger that would pull it into a future version (model becomes load-bearing for cost/latency; crew grows past ~5 agents or spans trust boundaries; bots take untrusted input or app-layer logs prove insufficient). Appendix verdicts and the v2.x sequencing line updated to match. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…re consideration Names channel-pluralism explicitly: we're building a framework, not a Matrix-only tool. The agent loop is channel-agnostic — CLAUDE.md persona, MCP tooling, dispatch, capability scopes, and run-id correlation all apply regardless of where the human message enters. Trigger to pull forward: a non-Matrix user need, or a second channel plugin landing in the Claude Code marketplace. Slack flagged as the likely first add. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was requested
Sherod asked for a v1 roadmap from his candidate list with critical feedback.
What changed
Adds
docs/roadmap-v1.md:How to verify
Read the doc; this is a draft, not a commitment. Iterate via PR comments.
🤖 Generated with Claude Code