Registry Baseline Glossary

These terms were accepted in the closed grill. The grill log is the decision trail. This glossary does not claim implementation is complete.

Terms

• Registry: the published, versioned set of Registry Items that is the only Baseline distributor and the source for drift management. It is public. Avoid: baseline artifact, release asset, control plane.
• Registry Item: one named, typed bundle of files and metadata in the Registry, in the shadcn registry-item format. Avoid: component; asset when meaning a whole item.
• Baseline: one immutable Registry version, named YYYY.MM.DD-<short sha>. Avoid: stable channel, bundled channel.
• Installed Record: the installer-written file .devpunks/installed.json that records the installed Baseline version, the Recorded Shape, and the item-to-path map. Avoid: manifest, receipt, lockfile.
• Recorded Shape: the repository shape captured at install time: workspace paths, Pack ids, detected technologies. Avoid: context plan, detection result.
• Copied Artifact: a Managed Artifact written verbatim from a Registry Item. Avoid: tier 1, static file.
• Built Artifact: a Managed Artifact rendered from a Registry Item template, Project settings, and the Recorded Shape. Avoid: tier 2, generated file.
• Authored Artifact: a repository-owned file that the installer writes once when absent and never compares afterwards. Avoid: tier 3, scaffold-once file.
• Project Skill: a skill under .agents/skills/<id> that no Registry Item provides; it is an Authored Artifact. Avoid: pre-existing skill, local skill, replaced skill.
• Harness Adapter: installer code that wraps one built subagent body in one harness's envelope. Kept from the CLI context architecture glossary.
• Drift Check: the three-way comparison of local bytes, the installed Baseline, and the latest Baseline. Classes: update-available, local-edit, conflict, shape-drift, missing, stale, link-failed.

Use the existing meanings of Pack, Software Scope, Commit Gate, Project settings, and Managed Artifact.

Relationships

• A Registry contains one or more Baselines; a Baseline contains one or more Registry Items.
• A Pack selects one or more Registry Items through registry dependencies.
• The Installed Record references exactly one Baseline.
• Every Managed Artifact is exactly one of Copied Artifact, Built Artifact, or Authored Artifact.
• A Project Skill is an Authored Artifact.

Axioms

• No content hash of a Managed Artifact is stored in the repository.
• Each local state file has exactly one writer.
• A Baseline is immutable; a correction is a new Baseline.
• The Registry is the only Baseline source; there is no bundled fallback.
• The Registry is public; the installer sends no credential.
• The installer never removes, compares, or overwrites a Project Skill. On an id collision with a Registry Item, the Baseline skill wins and the Project Skill is renamed [DEPRECATED] <name> and reported.
• A Pack is the only selection unit; detection proposes, it never selects.

Retired terms

Superseded from the Manifest-Driven Update Glossary: Scaffold Manifest, Validation Candidate, Prepared Installation, Validation Result, Cache Entry, and Context Plan as a persisted file.