Public Imports¶
Public imports for bijux-canon-runtime define which Python-facing symbols callers may depend on without reaching into internals. Import visibility should follow the contract, not accidental package layout.
What To Check¶
- start with the import root:
packages/bijux-canon-runtime/src/bijux_canon_runtime - separate supported imports from merely reachable internal symbols
- treat undocumented import usage as unstable even if it currently works
First Proof Check¶
srcand boundary-facing modules for the owning implementation surfaceapis/bijux-canon-runtime/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-runtime for runtime authority surfaces, the contract needs to be named as clearly as the implementation.