π Sprachhinweis / Language Note: Englisch fΓΌr technische Inhalte; Release-Planung wird von KI-Workern verarbeitet. English for technical content; release planning is processed by AI workers.
This document captures the long-term direction for the ai-issue-solver
project. It is intentionally lean and strategic; concrete tasks live in
BACKLOG/open.md.
- Information architecture β every agent only gets the context it needs. See Release 0.7.0 planning discussion.
- Agent-specific context routing β Planner gets more, Solver gets less, Reviewer gets the diff + rules, Watchdog gets cost + status.
- Cost & process control over model benchmarking. See #16, #37, #38, #39.
- Provider abstraction β GitHub-first, OpenRouter, native APIs as fallback.
See
REPO_PROFILE_PROVIDER.md. - Model override policy β model choice is explicit and overridable per run,
with defaults kept in role/provider configuration. See
MODEL_OVERRIDE_POLICY.md. - Knowledge lifecycle β every piece of information either gets
kept/promoted/archived/deleted. Nothing lingers.
- 0.6.0 done β skills + rework + batch cost forwarding.
- 0.7.0 done β Information architecture, role-based context
routing, release-review process. Close-out:
RELEASE_REVIEW_0.7.0.md. Release notes:RELEASE_NOTES_0.7.0.md. - 0.8.0 skipped β planned as Governance & Knowledge Release, but the scope (Handover Audit + Reviewer Runtime + Knowledge Dry Run) had no independent identity once meta-planning began. Pivoted.
- 0.9.0 done β Solver Validation Release. It shipped validation
infrastructure, PR rework, backward-split handling, hard stops for
partial/reject patch failures, dynamic OpenCode/OpenRouter free-model
discovery, and corrected benchmark classification from run reports.
Close-out is recorded in
CHANGELOG.md; the original plan remains inPLANNING_0.9.0.md. - 1.0.0 target β Runnable workflow app for AI-assisted repository
work. The app coordinates transparent, reviewable steps around one
repository: triage, planning, model selection, solver execution,
observation, review, rework, recovery, merge preparation, and
reporting. Product vision:
PRODUCT_VISION_1.0.md.
These need decomposition into BACKLOG/open.md items before they become
executable:
- Knowledge Manager as deterministic workflow (not LLM agent).
- Watchdog as cron-driven skill (not LLM agent).
- Per-role model routing as a config file (
config/role_routing.yaml). - Documentation lifecycle automation (archive / promote scripts).
- New solver features before the documentation & context story is settled.
- Model benchmarking without a cost-control baseline in place.