Jason Woltje
7272cfdc88
The enforcement half of the lease broker ships and denies; the promotion half has no production caller anywhere in the package. Verified across 0.0.48, 0.0.49 and 0.0.50-next.2207: begin_verification / observe_receipt / promote_lease are invoked only by broker-test-client.ts, the acceptance spec, unit tests, and two probes under docs/. Consequence: no lease on any host can reach VERIFIED, so mutator-gate denies every mutator with MUTATOR_UNVERIFIED via a gate that nothing shipped can satisfy. Runtimes that enforce the gate in-process (pi, via mosaic-extension's tool_call hook) are bricked for mutators; runtimes whose gate is wired through a settings hook escape only when that hook is absent — i.e. by being ungated. This adds the client. It implements protocol steps 1, 4 and 5: 1. begin_verification -> mint a challenge, return the exact receipt text 2. the MODEL emits that text verbatim as its entire latest message 3. the runtime adapter ships that message to the observer socket 4. observe_receipt -> PENDING_PROMOTION 5. promote_lease -> VERIFIED Step 2 is deliberately NOT implemented here, and that is the point. is_verbatim_receipt uses hmac.compare_digest against the exact minted string — explicitly "not a transcript substring" — which makes promotion a LIVENESS PROOF: it requires a live model that received the challenge in its context and echoed it exactly. receipt-observer-client.py will post ANY string as the latest assistant message. A promotion client that posted its own receipt would satisfy the broker while proving nothing — a gate-disabler indistinguishable from a working fix unless someone specifically looks. Emitting the receipt therefore belongs to the runtime adapter, where a real model turn happens. A local diagnostic that posts its own receipt exists in the operator's repo and is deliberately NOT shipped here. The construction binds the exact normative source bytes, so a VERIFIED lease means "this agent is running THIS law", not merely "this session id is known". h_source/h_payload are derived by importing the framework's own normative_fragments.build_payload rather than reimplementing it: the broker derives them the same way and any divergence yields PAYLOAD_BINDING_MISMATCH. There must be exactly one implementation. session_identity() prefers the generation FILE over the env var, matching lease_generation.py. Sending a generation higher than the broker's would revoke the session's own authority (daemon.py:342-344), so it never guesses. Verified end-to-end on sb-it-1-dt under a real lease-gated anchor: a mutator denied rc=2 MUTATOR_UNVERIFIED, then begin -> observe -> promote -> VERIFIED, then the same mutator allowed rc=0. Negative controls pass: a fresh session is still denied, and an unrelated session still reads UNVERIFIED — promotion is per-session and does not leak. Still open: adapter wiring for step 2. Lazy promotion on first mutator attempt avoids colliding with the Constitution's first-response mode declaration, since compare_digest requires the receipt to be the WHOLE message.
@mosaicstack/mosaic
CLI package for the Mosaic self-hosted AI agent platform.
Usage
mosaic wizard # First-run setup wizard
mosaic gateway install # Install the gateway daemon
mosaic config show # View current configuration
mosaic config hooks list # Manage Claude hooks
Headless / CI Installation
Set MOSAIC_ASSUME_YES=1 (or ensure stdin is not a TTY) to skip all interactive prompts. The following environment variables control the install:
Gateway configuration (mosaic gateway install)
| Variable | Default | Required |
|---|---|---|
MOSAIC_STORAGE_TIER |
local |
No |
MOSAIC_GATEWAY_PORT |
14242 |
No |
MOSAIC_DATABASE_URL |
(none) | Yes if tier=team |
MOSAIC_VALKEY_URL |
(none) | Yes if tier=team |
MOSAIC_ANTHROPIC_API_KEY |
(none) | No |
MOSAIC_CORS_ORIGIN |
http://localhost:3000 |
No |
Admin user bootstrap
| Variable | Default | Required |
|---|---|---|
MOSAIC_ADMIN_NAME |
(none) | Yes (headless) |
MOSAIC_ADMIN_EMAIL |
(none) | Yes (headless) |
MOSAIC_ADMIN_PASSWORD |
(none) | Yes (headless) |
MOSAIC_ADMIN_PASSWORD must be at least 8 characters. In headless mode a missing or too-short password causes a non-zero exit.
Example: Docker / CI install
export MOSAIC_ASSUME_YES=1
export MOSAIC_ADMIN_NAME="Admin"
export MOSAIC_ADMIN_EMAIL="[email protected]"
export MOSAIC_ADMIN_PASSWORD="securepass123"
mosaic gateway install
Runtime launchers
mosaic claude # Launch Claude Code with Mosaic injection
mosaic yolo claude # …with --dangerously-skip-permissions
mosaic codex | opencode | pi
mosaic claudex (EXPERIMENTAL)
Runs GPT models inside the Claude Code harness by pointing Claude Code at a
local claude-code-proxy that
translates the Anthropic Messages API to a ChatGPT-subscription (Codex OAuth)
backend. This is not Anthropic Claude — model behavior, tool use, and output
quality may differ. Intended for evaluation, not production delivery.
mosaic claudex # launch (prompts through the proxy readiness gate)
mosaic yolo claudex # …with --dangerously-skip-permissions
mosaic claudex --print "hello" # trailing args are forwarded to Claude Code
Prerequisite: the claude-code-proxy binary must be installed and
authenticated (claude-code-proxy codex auth …). mosaic claudex runs a
preflight that verifies the binary, the OAuth state (triggering a device re-auth
if needed), and a trusted local listener before launching; it fails closed
if the proxy cannot be brought up with a verified identity.
Isolation (never touches your real Claude state). claudex always launches
against an isolated CLAUDE_CONFIG_DIR (default ~/.config/mosaic/claudex/home).
The ambient CLAUDE_CONFIG_DIR is deliberately ignored, and a guard proves the
resolved dir can never be — or live under — the real ~/.claude. A claudex
session therefore cannot mutate your normal Claude Code config.
No token leakage. claudex never reads the proxy's credential file. Claude
Code is handed only ANTHROPIC_AUTH_TOKEN=unused pointed at the loopback proxy;
the entire credential-bearing env family (ANTHROPIC_*, AWS_*, GOOGLE_CLOUD_*,
GOOGLE_APPLICATION_CREDENTIALS, *_TOKEN, *_KEY, *_SECRET, …) is stripped
from the composed environment. The Bedrock/Vertex routing switches
(CLAUDE_CODE_USE_BEDROCK, CLAUDE_CODE_USE_VERTEX, and the _SKIP_*_AUTH
pair) are force-removed regardless of value — otherwise their mere presence
would route Claude Code to the real Anthropic API via AWS/GCP and bypass the
proxy. The proxy holds the real OAuth credential.
Model tiers (override via env).
| Tier | Env var | Default |
|---|---|---|
| primary (opus/sonnet) | ANTHROPIC_MODEL |
gpt-5.6-sol |
| small/fast (haiku) | ANTHROPIC_SMALL_FAST_MODEL |
gpt-5.6-luna |
Operator-provided values win over the defaults. Additional overrides:
MOSAIC_CLAUDEX_CONFIG_DIR (isolated config dir), ANTHROPIC_BASE_URL (proxy
endpoint).
Hooks management
After running mosaic wizard, Claude hooks are installed in ~/.claude/hooks-config.json.
mosaic config hooks list # Show all hooks and enabled/disabled status
mosaic config hooks disable PostToolUse # Disable a hook (reversible)
mosaic config hooks enable PostToolUse # Re-enable a disabled hook
Set CLAUDE_HOME to override the default ~/.claude directory.