Cortex gives software-engineering agents durable state, explicit uncertainty, bounded changes, and verification tied to the workspace a human will actually use.
A strong model can write the function. The hard part is keeping why this theory won, what would disprove it, which files are allowed to move, and whether the visible behavior truly passed intact through a long task.
Cortex turns those fragile thoughts into a local case file with enforceable gates. The model stays the planner and author; the kernel keeps the work honest, recoverable, and inspectable.
Each action advances one explicit state. Skipped disproof paths, undeclared change boundaries, competing owners, stale receipts, and unverifiable claims become data—not forgotten instructions.
A shared result envelope, explicit required inputs, executable next actions, closed enums, and honest tool degradation reduce the amount of protocol the model must reconstruct on its own.
Revision-bound receipts, cross-case disproof recall, multi-agent leases, bounded handoffs, typed claims, and full provenance preserve sophisticated work without forcing it into a simplistic autopilot.
Install the pure-Go binary, open a case in any Git repository, and expose the compact MCP profile to your agent. Specialist tools are optional and degrade without fabricated output.
$ go install github.com/abdul-hamid-achik/cortex/cmd/cortex@latest $ cortex open "Fix checkout redirect" --actor agent-auth ✓ [investigating] task opened with durable evidence state $ cortex serve compact MCP profile ready
More tools without structure create more ways to get lost. Specialized tools plus a durable kernel create accumulated engineering judgment.
