Give a specification a CLI and someone will eventually ask it to execute the system. For NexFlow, that would be the most tempting feature to build first and the wrong one. A command that launches agents makes a better demo than a validator. It also turns early implementation choices into de facto rules before the specification has settled them. NexFlow currently describes a specification through documentation, YAML manifests, JSON Schemas, reference examples, validation rules, conform...