internal/

Package adh is the foundational domain package for the agentic-dev-harness CLI: the shared language every other package speaks.

Package adr is the architecture-decision-record format (SPEC-ADDITIONS §12): the durable, routable home for a team's local trade-off decisions — Status, Context, Decision, and Consequences split into Easier and Harder.

Package authority holds the pure authority decisions of the harness: the autonomy ladder (SPEC §6), the model-gate (SPEC §5.1), and the human safety gate (SPEC §5.2).

Package config resolves the harness configuration by SPEC §3 precedence: built-in defaults, then the user config, then the repo .adh/config.toml, then the .adh/autonomy runtime override, then ADH_* environment variables (each overriding the last); command-line flags override the result at the call site.

Package consolidate is the pure core of the offline self-optimization cycle (SPEC-ADDITIONS §18.4): harvest closed arcs, mine recurring checkable tasks and assign each a stable held-out split, then reflect-and-gate a bounded candidate edit on a strict held-out improvement.

Package contextstore holds the just-in-time context units the harness routes to stages (SPEC-ADDITIONS §10): a large navigable store and a small active working set selected by an arc's labels and touched paths.

Package critic assembles the cold critic's grounding (SPEC-ADDITIONS §19.1): the repository-owned working set a critic reviews against — the arc's touched paths, its acceptance bar, the proof packet the builder left, and the context units routed for its labels and paths (§10).

Package device abstracts on-device (adb) validation (SPEC §4).

Package edit holds the pure guards an optimize/apply step enforces before committing a harness edit (SPEC-ADDITIONS §18.2): the size budget and the hash-based no-op check.

Package evaluation is the deterministic Evaluation stage (SPEC-ADDITIONS §19.2): it adjudicates the cold critic's findings by running the repository artifact each one names, then disposes of the arc.

Package evidence is the append-only audit log for the self-optimization loop (SPEC-ADDITIONS §18.6).

Package failures owns the append-only failure registry (SPEC §4.1): a JSON array of failure notes under a repository path, distilled into lessons (§11).

Package harness holds the self-optimization decisions (SPEC-ADDITIONS §18): classify a miss as a harness defect or an execution lapse (§18.3), and accept a candidate only on a strict held-out improvement via the gate ratchet (§18.2).

Package harnesscheck is the pure harness-integrity self-check (SPEC-ADDITIONS §10.4): given the loaded context store, tool registry, loop registry, and NFR specs, it reports whether the harness is intact and internally consistent — every registry is structurally valid, unit ids are unique, and the cross- references between the pieces resolve (a routed unit's integrity check names a declared §13 tool).

Package judge is the deterministic rule-judge for scoring an output against a set of checks (SPEC-ADDITIONS §11 test-checks; ported from skillsaw's judge, itself a port of SkillOpt-Sleep's judges.py).

Package kpi turns declared KPIs on §10 units and §13 tools (SPEC-ADDITIONS §16/§18) into gated improvement proposals: it measures a subject against the log of how it actually behaved — the failure-record log for units, the tool-run log for tools — and when a KPI's threshold is breached across enough independent time strata to trust it (§18.2), proposes a change to that subject.

Package lesson turns recurring corrections into promotions to a durable owner (SPEC-ADDITIONS §11): it distills failures into governing classes and routes each to its smallest owner.

Package loop models maintenance loops (SPEC-ADDITIONS §15): a named invariant kept true by a sensor and an authorized action, with an explicit retirement condition.

Package metrics is effectiveness accounting (SPEC-ADDITIONS §16): it optimizes useful outcomes per unit of scarce human attention, not raw activity.

Package model is the LLM seam for the five stages (SPEC §1-2).

Package nfr is the nonfunctional-requirement spec format (SPEC-ADDITIONS §10.5): a Planguage-quantified quality attribute named by an agreed taxonomy.

Package oracle implements the differential oracle and invariant checks of the eval layer (SPEC §4, SPEC-ADDITIONS §18): two independently written implementations of the same match rules grade each other, and a planted-defect self-test proves the oracle rejects a known regression.

Package prompt renders a stage's model prompt from templates.

Package redact removes secrets from text before it is persisted (SPEC-ADDITIONS §18.4): the sleep consolidation cycle harvests arc history and stages guiding text that can carry credentials, so every staged string passes through here first.

Package relay is the shared engine for the out-of-band model relay (SPEC §1-2): it emits a stage's prompt and parks a pending turn, then on a later invocation validates the operator's reply and advances the arc.

Package rubric scores a harness guiding artifact against adh's own five-dimension rubric (SPEC-ADDITIONS §18.2) — distinct from the external skillsaw 9-dimension rubric adh consumes at its gate.

Package schedule persists cron jobs that fire an adh command on a cadence and fires the ones that are due (SPEC-ADDITIONS §15, §18).

Package session normalises foreign agent-session stores into one digest the harness can mine, and mines them for corrections that never became arcs.

Package shell runs a repository-owned command through the system shell.

Package skillsaw decodes the eval JSON the external skillsaw CLI emits (SPEC- ADDITIONS §18, Loops B/C), so adh can feed skillsaw's score into its own strict-`>` ratchet (`harness gate`) — skillsaw as the cheap floor under adh's Evaluation bar, never a replacement for human approval or proof (§18.2).

Package stage sequences the five-stage loop (SPEC §1): it runs an arc's current stage through the model seam and advances it, and decides whether the relay may auto-launch the next stage under the autonomy level (SPEC §6).

Package state persists arcs to the .adh workspace as JSON and provides the lifecycle operations the arc commands drive.

Package toolreg is the tool registry (SPEC-ADDITIONS §13): declared capabilities a stage can discover, select by what they verify, and repair.

Package toolrun owns the append-only tool-run outcome log (SPEC-ADDITIONS §16/§18): one record per `adh tool run`, stamped so a §13 tool's declared KPIs can be measured against how it actually behaves over time.

Package vcs is the version-control seam: the small set of git operations the harness needs — inspect the working tree, branch, and commit.

Package verdict is the replication-gated outcome-eval verdict (SPEC-ADDITIONS §18.2): a pure decision core that layers a trust taxonomy over the cheap strict-`>` gate.

Package worker models the adoption epoch and requalification gate (SPEC §14 / fixed-worker): a model or agent change opens a new epoch that must be requalified before normal runs resume.

Package worktree reads the git working tree to ground the relay (§19.1): the unified diff of the change under review, the changed code paths, and the arc footprint (paths + area labels) an execution turn leaves.