CLI Surface¶
The CLI surface for bijux-canon-reason is the command boundary operators and scripts will treat as stable first. If the command semantics for reasoning output are real, the docs should say so plainly.
What To Check¶
- name the canonical command entrypoint:
bijux-canon-reason - separate supported flags and behaviors from local convenience behavior
- treat scripted usage as contract pressure, not as anecdotal usage only
First Proof Check¶
srcand boundary-facing modules for the owning implementation surfaceapis/bijux-canon-reason/v1/schema.yamlor tracked examples for the documented contract surfacetestsfor executable confirmation that the contract still holds
Bottom Line¶
If callers depend on bijux-canon-reason for reasoning output, the contract needs to be named as clearly as the implementation.