bourdon

bourdon

The unscoped bourdon command-line interface — a thin, Apache-2.0 dispatch layer over the @getbourdon/* engine packages. It contains no engine logic: every subcommand delegates to a ported @getbourdon/* package, so the CLI itself is permissively licensed even though the engine packages are BUSL-1.1.

npx bourdon --help
# or
npm i -g bourdon && bourdon serve

The npm CLI exposes only commands backed by a native TypeScript implementation. For the larger Python command surface, install bourdon from PyPI. Keeping the surfaces explicit prevents --help from promising placeholder commands.

Supported commands

• prepare-turn, deeper-context, codex compile-turn — recognition context (@getbourdon/federation + @getbourdon/mcp-server + @getbourdon/inference)
• recognition eval — the scoring harness (@getbourdon/recognition)
• serve — the L6 federation MCP server (@getbourdon/mcp-server), including the non-loopback-bind refusal
• agent {add,list,rotate,set-tier}, grant, ungrant, revoke, staging {list,promote,reject}, audit — trust + audit (@getbourdon/federation)
• audit-leaks — the leak auditor (@getbourdon/redaction)
• agents — the --json desktop-tray contract (local enumeration)
• doctor, export-all, hermes {export,doctor}, claude-code export — the participant layer (@getbourdon/participants)

Load-bearing defaults remain aligned with Python: serve --port 7500 --host 127.0.0.1, codex compile-turn --max-items 6 --max-chars 1800, recognition evaluation thresholds of 0, and audit --limit 50.

Peer networking is opt-in

bourdon serve starts with zero remote peers. A populated ~/.bourdon/peers.yaml is not read unless you grant network authority:

# Load ~/.bourdon/peers.yaml
bourdon serve --federate

# Select a configuration explicitly
bourdon serve --peers-config ./peers.yaml

# Add one or more endpoints explicitly
bourdon serve --peer https://peer.example.com

Use --no-peers when you want an explicit local-only assertion; combining it with --federate, --peer, or --peers-config is an error. Peer URLs must use HTTPS, except that HTTP is accepted for loopback development endpoints. URLs containing credentials, a query, or a fragment are rejected.

License

Apache-2.0. See LICENSE.