Warden and TheAuditor: a disciplined product direction

Warden is the operator-facing cockpit for active coding work. TheAuditor and Curator bring adjacent disciplines into view: code understanding, review-oriented context, and the ability to carry useful project knowledge into the work being supervised. Together, they point toward a development workflow where a coding session is not cut off from the information that should shape it.

Keep code context close to the decision

In Warden’s working development build, TheAuditor and Curator can sit alongside the tasks that need their perspective. That matters when an operator is reading a plan, assessing a proposed file change, or deciding how to continue a stalled session. Relevant code and project context should be discoverable where the decision happens, not hidden behind a separate ritual after the work is already done.

The broader Warden workflow also includes multi-session supervision, approval visibility, provider and model choice, MCP connectivity, hooks, context management, session records, and cost visibility. The integrations are valuable because they support that operator loop: understand the task, direct the work, review what happened, and return with context intact.

Integration needs a clear contract

The public release will treat integration support as a product commitment with defined boundaries, rather than a loose claim that every installation behaves the same way. That lets operators judge the supported path before they depend on it in a team workflow.

Warden is a working proprietary development build. The public binary is targeted for roughly two to three months; supported TheAuditor, Curator, MCP, platform, and data-handling paths will be published with that release.