Fully autonomous software development for the konflux-ci organization.
This repo is a living design document exploring how to get from the current state of development across konflux-ci to a fully-agentic workflow with zero human intervention for routine changes. The goal is agents that can triage issues, implement solutions, review code, and merge to production autonomously — while being secure by design.
This is not a product spec. It's an evolving exploration of a hard problem space, meant to rally the konflux-ci contributor community around the vision and invite experimentation and contribution.
- docs/vision.md — The big picture: what we're trying to achieve and why
- docs/problems/ — Deep dives into each major problem domain, each evolving independently:
- Intent Representation — How do we capture, verify, and enforce what changes are wanted?
- Security Threat Model — Prompt injection, insider threats, agent drift, supply chain attacks
- Agent Architecture — What agents exist, what authority do they have, how do they interact?
- Autonomy Spectrum — When to auto-merge vs. escalate to humans
- Governance — Who controls the agents and their configuration?
- Repo Readiness — Test coverage, CI/CD maturity, what's needed before agents can be trusted
- Code Review — How agents review code, including security-focused sub-agents
- Architectural Invariants — Enforcing things that must always be true, grounded in the existing architecture repo
- Agent-Compatible Code — Language properties that affect agent effectiveness
- Codebase Context — How agents acquire codebase understanding and how to structure org-level context
- docs/landscape.md — Survey of existing AI code review tools and how they relate to our goals (time-sensitive — check the date)
- docs/experiments/ — Logs and results from trying things in practice
Pick a problem area that interests you. Read the existing document. Add your perspective, propose solutions, poke holes in existing proposals. Open a PR.
If you want to run an experiment — try an agent workflow in a repo, test a security guardrail, prototype an intent system — document what you did and what you learned in docs/experiments/.