Your code's second brain.
DrCooper is a local intelligence engine for coding agents — Codex, Claude Code and OpenCode — that unifies semantic navigation, execution and context, persistent memory, a code graph, documentation and knowledge evolution. LLM and JEV are optional and independent: the core works without them.
Status: planning. This repository holds the specification and the product plan; there is no implementation yet. Authorised execution starts with R0 (discovery), not with code.
The canonical set is DC-DOCSET-0.3.0, dated 2026-10-26. It is published byte for byte, with its original SHA-256 hashes.
| Document | Contents |
|---|---|
| Product plan | Entry point, conventions and limits |
| Master specification | Product, architecture, contracts and criteria |
| Roadmap | R0–R6 deliveries and exit gates |
| Backlog | 52 parent issues with verifiable acceptance |
| Increments | 69 subtasks of the 23 L-sized issues |
| Decisions and coverage | Pending ADRs and traceability |
| DrCooper Bench | run / compare / report contract |
| Audits | First review and second |
| Brand brief | Mascot and visual direction |
| Manifest | Inventory, versions, sizes and hashes |
The canonical set is Spanish and stays that way. The English rule applies from 2026-10-27 onward; documents, issues and Project views created before it are not translated.
The 52 parent issues and their 69 increments are published in the Issues tab, grouped by the R0–R6 milestones and labelled by area, priority and size. Increments are sub-issues of their parent and each can have its own PR. Plan dependencies point at the real GitHub numbers.
The execution board is DrCooper — Plan, with four views: Plan (parents), Ejecución (increments by state), R0 (immediate work) and P0 (blocking priority). The Status field and the close/PR workflows live in the Project; the source of truth remains this repository and the issues.
main is protected: every change lands through a pull request. Direct pushes, force pushes and branch deletion are not allowed. A PR must describe the change, link the corresponding issue and provide the acceptance evidence defined in the plan.
Before implementing an issue, check its blocking decisions and dependencies in DECISIONES_Y_COBERTURA.md and ROADMAP.md. L-sized issues are not handled as a single PR: they are split into increments.
Everything that lives in this repository is written in English: code, identifiers, comments, commit messages, branch names, issues, pull requests, documentation and file names.
Conversation with the maintainer is in Spanish. That is a rule about how the assistant talks to the owner, not about what gets committed.
See CONTRIBUTING.md for the full policy.
The documents keep the state and the claims of their 2026-10-26 revision (for example, "there is no remote repository" or "no issue is published"). The set stays intact so the manifest and its hashes remain verifiable. Publishing the repository and the backlog happened later and does not alter the canonical content.
MIT. You may use, modify and distribute the project; attribution is appreciated.