ControDocs

tldr — Internal map of what Contro is building: what's live, what's WIP, and what's planned. Audience: devs, designers, management. Everyone under NDA.

What this site is

This is the canonical "how this repo fits together" reference for the team. It's deliberately candid: where the code is messy, the docs say so. Where we don't know something yet, it's logged as an Open question rather than guessed at.

How to read it

• Repo at a glance — one-table overview of every workspace, its status, and where it lives.
• Debate lifecycle — the state machine a single debate moves through.
• Scoring — how the AI judge scores comments.
• Infrastructure — deploy targets, the k3s cluster, the data layer.
• Development — code style, test rules.
• Open questions — things to resolve, aggregated.

note

Unknowns here are a feature, not a bug. Flagging unknowns explicitly is how we make them tractable.