Minimum Viable Contract

Not every capability needs the full extended contract on day one. The minimum viable contract is the smaller version, just enough fields to make a capability legible: a name, its inputs and outputs, what it promises, and what it explicitly leaves out.

It's the default cdad init scaffolds unless you pass--extended. For a lot of capabilities it's also the right stopping point. More fields don't automatically mean more legibility, and a contract nobody finishes filling out is worse than a short one that's actually complete.

The appendix'sContract Schema Referenceshows both the minimum viable and extended versions filled in side by side, so the first one you write doesn't start from a blank page.