Operate index as an evidence-producing execution service. The safe path starts
with capability discovery, makes storage locations explicit, materializes an
artifact under a declared contract, and retains a complete run before making a
replay claim.
The canonical distribution installs bijux-canon-index. Select an implemented
surface deliberately:
Operating context
Entry surface
State and evidence responsibility
shell or automation
bijux-canon-index with JSON output
retain command, exit status, payload, state path and run directory
service client
versioned HTTP application and schema
retain request/response identity; deploy authentication, isolation and durable state externally
in-process integration
named application, domain, contract and infrastructure modules
caller owns composition and persistence boundaries explicitly
preserved automation
bijux-vex compatibility command
verify delegation, then migrate directly to bijux-canon-index
The equivalent module form is
python -m bijux_canon_index.interfaces.cli.app. An HTTP schema is not proof
that a configured backend, plugin, or vector store is
available; run capability discovery in the environment that will execute the
request.
The HTTP application does not supply authentication, authorization, tenant
isolation, provider credential governance, or network sandboxing. Run files are
atomically replaced but are not self-authenticating as a set. Apply deployment
controls externally, redact vector-store credentials in diagnostics, and add a
digest or signature when evidence crosses a trust boundary.