Manifest-Driven Update Glossary
Approved terms and invariants for issue 215 planning
Manifest-Driven Update Glossary
These terms were approved in the closed grill. The direct plan carries their execution contract; this glossary does not claim implementation is complete.
| Term | Meaning |
|---|---|
| Baseline | Selected version of Harness-managed scaffold content and contribution definitions. |
| Scaffold Manifest | Recorded adopted scaffold state and ownership evidence. |
| Managed Artifact | Artifact whose obligations follow recorded ownership and the desired Scaffold Plan. |
| Context Plan | Neutral per-scope contribution intent before paths and writes. |
| Scaffold Plan | Desired files, links, dependency/configuration changes and ownership. |
| Validation Candidate | Isolated proposed repository state used to verify an update. |
| Prepared Installation | Reusable dependency/toolchain state for one resolved installation context, including required approved patches. |
| Validation Result | Findings and completion evidence for a candidate under a particular validation context. |
| Cache Entry | Disposable stored derived content/evidence eligible for reuse only when complete input identity matches. |
Context Plan feeds Scaffold Plan; Scaffold Manifest records adoption. Validation Candidate includes required validation context beyond owned writes. A source edit may invalidate a Validation Result while retaining Prepared Installation reuse.
Ignore status does not establish ownership. Planned changes are not completed writes. Cache entries do not establish current-worktree readiness, applied writes or publication. An uncertain cache identity requires fresh validation; incomplete or uncontained candidate inputs block dependent adoption.
Turbo task artifacts and updater cache entries have separate contracts. “Everywhere” means eligible trusted contexts with compatible result-affecting inputs. “No hard limits” rejects performance acceptance thresholds; it does not remove bounded cache storage or correctness requirements. Proven remote restoration is distinct from remote enablement or generic cache-hit counts.