internal/

Package approve is the gate writer: `lifecycle approve --stage <s>` (spec-lifecycle.md §5, implementation-plan.md §2.6).

Package archive implements `lifecycle archive <change>` (spec-lifecycle.md §6.2, implementation-plan.md §2.5): the 5-step pipeline that turns an approved change folder into a permanent projection update — gate-check, conflict-check, pre-image digests, native fold + relocate, post-image digests + monotonic-seq ledger append — plus a cheap post-write self-check.

Package atomicwrite writes a file such that a concurrent reader — or a crash — never observes a half-written result: the bytes are written to a temp file in the *same directory* as the target, flushed, and then atomically moved into place (implementation-plan.md §3, "Atomic writes").

Package config loads and validates lifecycle.yml (spec-lifecycle.md §10, implementation-plan.md §2.10): the project config `lifecycle init` writes and every command reads, at repo root, sibling of openspec/.

Package constitution is a thin exec wrapper around the sibling adr-sourced-constitution primitive's `constitution` binary (spec-lifecycle.md §7, implementation-plan.md §2.7).

Package guard implements `lifecycle guard` (spec-lifecycle.md §6.3, implementation-plan.md §2.4): the deterministic, no-LLM fidelity check that the archive ledger (internal/archive's ledger.jsonl), the archived changes it describes (openspec/changes/archive/**), and the live projection (openspec/specs/**) all still agree with each other.

Package scaffold implements `lifecycle init`'s side of the build: it authors the managed pointer blocks in agent-instruction files (CLAUDE.md, AGENTS.md) and fans the embedded Layer-2 skills out into a repo's agent-skill trees, keeping both drift-protected via openspec/.state (implementation-plan.md §2.9, §2.12, §5/§6 of the mirrored constitution plan).

Package schema embeds the natively-owned kentra-spec-lifecycle schema descriptor (spec-lifecycle.md §4, implementation-plan.md §2.2): the artifact set (proposal -> specs -> design -> tasks), its requires: DAG, and the four artifact templates (spec-lifecycle.md §4's stage/content table; the tasks.md template carries §4.2's milestone/validation-contract grammar verbatim).

Package spec is the format engine: the pure-Go, parse/render half of spec-lifecycle's reimplementation of the OpenSpec on-disk format (implementation-plan.md §0.5, §2.3; spec-lifecycle.md §6.1), pinned to the grammar of `@fission-ai/openspec` v1.5.0 (commit 546224e).

Package status implements `lifecycle status` (spec-lifecycle.md §5/§9.1, implementation-plan.md §2.6): the read-only gate-state reporter over the records internal/approve writes.

Package testutil holds shared test guards for OS-dependent filesystem behavior.

Package validate implements the custom-artifact structural checks spec-lifecycle.md §3.3 wires into each gate's pre-check ("lifecycle validate --stage <s>") and implementation-plan.md §2.3 assigns to M2.