Cliewen

Appearance

CliewenEvidence-backed Intent Engineering for coding agents

Coding agents can produce plausible changes faster than a person can confidently accept them. Cliewen keeps the requirement, implementation, and acceptance evidence connected in Git, then checks that the connection is intact before merge.

Start reading
Cliewen logo

For agent-driven pull requests

Built for repositories where coding agents make real product changes through Git branches and pull requests.

One thread the repository can check

Goals lead to capabilities, acceptance criteria, and declared evidence—classified test references or genuine Human proof. The clue CLI reports broken links and missing evidence locally and in CI without executing tests.

Methodology, judge, and memory

Cliewen is the methodology, clue is its command-line judge, and the corpus under docs is the permanent system record that agents maintain with the code.

Deliberately visible overhead

Agents prepare the corpus and verified proposal; humans keep control of intent and merge. Small work that changes no meaning stays outside the full loop.

The thread ​

Pick up any artifact and follow it back to why it exists, or forward to what proves it. clue checks that no arrow is missing. It does not run your tests, it cannot tell you that a test proves the right thing, and it cannot tell you the goal was worth having—that judgment stays yours, at the merge.

Three names, three things ​

  • Cliewen — the methodology.
  • clue — the deterministic command-line judge.
  • The corpus under docs/ — the durable record of the system as it exists.

Three moves ​

Install takes one command. Prompting takes ordinary words. The only step Cliewen refuses to do for you is the last one.

Next ​

Start with what Cliewen is and why it exists.

Released under the Apache 2.0 License.

Cliewen