hoziron-cli contract

Inspect recorded contract bindings — the mapping between a competency's declared contracts (named tool-surface roles, ADR-051) and the concrete integration package bound to fulfil each one (ADR-066 gives contracts a real, schema-bearing package format; see manifest-schemas.md and object-model.md).

This command group is read-only. There is no hoziron-cli contract bind or unbind — bindings are established implicitly when a competency and a compatible integration are both active, not through a separate CLI step.

Synopsis

hoziron-cli contract <subcommand> [options]

Subcommands

SubcommandDescription
list [--json]List recorded contract bindings

hoziron-cli contract list

Queries GET /contracts on the running daemon.

hoziron-cli contract list [--json]

Examples

$ hoziron-cli contract list
CONTRACT             INTEGRATION                    BOUND_AT
claims-write          claims-core-adapter            2026-06-01T10:00:00Z
policy-read           policy-admin-adapter           2026-06-01T10:02:15Z

# No bindings recorded yet
$ hoziron-cli contract list
No contract bindings recorded.

$ hoziron-cli contract list --json
{
  "bindings": [
    {
      "contract": "claims-write",
      "integration_id": "claims-core-adapter",
      "bound_at": "2026-06-01T10:00:00Z"
    }
  ]
}

Destination pins are not managed here

There is no register-pin/promote-pin subcommand in this group. A locally carrier-writable pin store would be a bypass of the licence's egress allowlist, not a lighter-weight copy of it — destination pins live exclusively in the signed carrier licence (see licence.md and ADR-064). There is no CLI path to add or promote a destination pin outside of reissuing the licence.

See Also