internal/

Package artefact holds each of the five artefacts' own schema, the checks that read one artefact against itself — kind: against its directory, an artefact's own name against its file's basename, the credential slot's shape, the Target declaration's own two cross-field rules, and the Manifest's request, input-schema and path grammars (§3, §4, §12) — and, starting with the Definition, the first checks that read more than one artefact at a time: whether a name an artefact writes for another resolves, and the two checks a (Definition, Target) binding decides that neither artefact alone can (§4, §5, issue #93).

Package cadence reads a Cadence: §10's five-field cron grammar, and both halves of the gloss every surface renders one through — the phrase, which states the times of day, the days and the months the expression selects, and the rate, which states how often that comes to in runs per month.

Package capability is the two effects hyper performs on a Manifest's behalf, and it is the only package in the tool that touches a network or a child process (§5, issue #133).

Package cli is the third seam #87's Implementation Decisions name: argument handling, path stats, the two renderings, ordering, filtering, exit codes, stream discipline.

Package compare is the Comparison (§8, issue #167): one Run rendered against the Run before it, as an ordered list of rows.

Package exit is §12's closed set of exit codes: seven members, one per way an invocation can end, each carrying the outcome of the triple it maps onto (§9, §12).

Package git is the one rule two packages that start a git subprocess must agree on: which of the process's environment such a subprocess may inherit (§7, issue #136).

Package mcp is hyper's second surface: the MCP server §9 states, started by `hyper mcp` and speaking JSON-RPC over the stdio the client handed the process (§9, ADR-0088, issue #195).

Package pin is the version pin: the gate fifteen of §9's sixteen commands compare themselves against before reading a second file, and the edit the sixteenth makes to the file they read (§9, §11, ADR-0020).

Package problem defines the one shape a static-verification finding takes: a value, not a message.

Package projection is §12's path grammar resolved (issue #133): a path in the closed grammar — `$`, `.member`, `["member"]`, and nothing else — evaluated against a Capability's response object, and the projected fields an Operation's record: block reads out of one.

Package registry is `install`'s two reads: the Manifest a ref names, and the `checksums.txt` published beside it (§11, ADR-0087, issue #187).

Package release is the one thing the version pin ever reaches the network for: the published checksum of the release artefact a generated workflow installs (§11, ADR-0020, issue #178).

Package render is hyper's row stream (issue #110).

Package repository finds the repository root and loads the repository: one call walks the five artefact locations, reads and parses each file, and returns what was loaded together with the namespaces built from it (issue #109).

Package revision is what git says about the **code** branch: the commit at `HEAD`, the blob id of an artefact as the working tree holds it, and whether any artefact a Run read differs from `HEAD` or is untracked (§7, issue #136).

Package run is the engine: what happens between `hyper run <procedure>` and the Journal entry it leaves behind (§6, issue #136).

Package schema is hyper's own schema engine — the reading rule and the object shape it reads against (§3, §12, ADR-0081).

Package store is hyper's record: the orphan branch §7 states, and git as the subprocess that reads and writes it.

Package verify is §4's static verification over an already-loaded repository: the second pass, which runs after internal/repository has walked the artefact locations and parsed every file, and which reports every problem it finds rather than the first.

Package version names the version of the running binary — the fact the version pin gate compares against the Repository declaration's pin (§11, ADR-0020) — and, since issue #103, the whole of what `hyper version` prints: the facts a build stamps into a binary, and the page that states them.

Package workflow is the file `hyper project` writes, as a pure function: the facts one Procedure's workflow is derived from in, its exact bytes out (§10, §11, issue #176).

Package yamlsubset is the loader's one rule for issue #88: the strict YAML subset §3 states.