Open Source Toolkit

Everything described elsewhere on this site, the scoring methodology, the extraction priority model, the shape of a contract, is backed by a real, runnable command-line tool, and that tool is open source. That's not a footnote. It's the difference between a framework you have to trust and one you can go verify yourself, field by field.

The cdad CLI implements check,roadmap, init, validate, andgraph as five real commands with real output files, not five slide-deck labels. The contract schemas thatinit scaffolds and validate checks against live in the same repository as the code that reads them. If you want to know exactly what makes a contract pass validation, or exactly how the legibility questionnaire turns answers into a score, the answer isn't a claim on this page. It's a file you can open.

That matters most for the parts of the methodology that are easiest to be skeptical about from a distance. Multiplying three axes instead of adding them, scoring half-points on partial answers, deciding what counts as an exception path worth flagging. None of that is arbitrary once you can see the logic that implements it, and none of it is hidden behind a paywall or a sales call to check.

The toolkit being public also means it's inspectable by the exact audience it's built for. An engineer deciding whether to adopt this in their own repository doesn't need to trust a vendor's pitch. They can read the schemas, run the CLI against a real repo, and judge the output on its own terms before committing a single capability to it.