internal/

Package bench implements the scenario benchmark harness: a controlled, local-first, reproducible comparison of direct-MCP vs Ozy-brokered agent performance against a frozen incident scenario.

Package broker defines the single in-process seam through which every adapter performs Ozy's findTool, describeTool, and callTool operations.

Package catalog defines Ozy's persistent capability catalog seam.

Package cli implements the `ozy` command surface (SPEC.md §15).

Package config loads, validates, and redacts Ozy's single configuration file (SPEC.md §11).

Package contract defines Ozy's agent-facing response and error models.

Package daemon hosts Ozy's runtime: it owns configuration, the catalog store, and the in-process broker that every adapter shares (SPEC.md §6.1).

Package downstream connects to configured downstream MCP servers and returns initialized client sessions isolated per server.

Package eval is Ozy's evaluation harness.

Package index discovers tools from connected downstream servers and persists normalized catalog entries.

Package installer drives Ozy's setup and teardown as resumable, idempotent step state machines.

Package mcp adapts Ozy's broker to the agent-facing MCP surface.

Package paths resolves every Ozy install location behind one abstraction so the installer and uninstaller never hardcode directories.

Package render writes typed broker results to an io.Writer in the format the caller requested: human-readable (default), a single JSON document for agents and evals, or a terse concise mode (SPEC.md §15).

Package schema validates downstream-tool arguments against the subset of JSON Schema Ozy catalogs.

Package search ranks cataloged tools for a capability query with a lexical baseline and an optional semantic signal (SPEC.md §10).

Package sidecar is the Go client for Ozy's optional Python embedding sidecar.