internal/

Package agent embodies the Loop as a compact ReAct cycle over the fixed M1 tool belt (edit / read_file / ls / exec / run_pov), talking to a model through the pluggable model seam and choosing that model through the Router seam.

Package artifact defines quarry's atomic unit as a minimal, content-addressed core with a thin envelope — the versioned contract between the Client (System A) and the Infrastructure (System B).

Package chain models exploitation as content-addressed capability transitions and the chains built from them.

Package channels defines the four code seams between the Client (System A) and the Infrastructure (System B), plus the emit gate that every outbound pattern must pass.

Package config resolves client configuration from flags/env with sane defaults, and manages the persistent client signing key used to attest emitted pattern artifacts.

Package gitcommons materializes the public abstract tier of the knowledge commons as a git-native tree (ADR-0001, quarry-commons): content-addressed artifact abstracts, a prefix-sharded behavioral-key index, and a Bloom-filter root digest for cheap "novel or prior-art?" existence checks before any fetch.

Package hydrate seeds the Knowledge Commons from ARVO / OSS-Fuzz vulnerability entries — the first System-B deliverable.

Package loop is quarry's supervisor: one complete cycle of the expanded scientific method, end-to-end, on a real target.

Package mcp is a minimal Model Context Protocol client (stdio transport, JSON-RPC 2.0).

Package model is the pluggable model seam.

Package oracle is the deterministic verifier at the center of quarry.

Package router is the model-selection seam.

Package runner executes the authoritative target and produces the oracle.RunResult.

Package store is quarry's grounding substrate: one embedded SQLite database (knowledge base + hypothesis frontier + provenance + trajectory event log) plus a content-addressed blob directory.

Package target ingests a target descriptor and prepares it for the Loop: it resolves how the target is built and run, keeping the target's build environment separate from the agent's toolkit.

Package toolcat is the tool catalog + MCP broker.

Package verify is the oracle-as-referee: it wires the runner (which produces RunResults on the authoritative target) to the pure oracle evaluator, and records every judgment as an experiment in the Datastore.