Glossary
Generated from spec/model/concepts.zon; do not edit this file directly.
The structured registry owns concept identity, terminology, definitions,
relationships, and requirement references.
action
ID: concept-action
One operator-visible unit in the confirmed cleanup plan. A direct filesystem action may contain multiple entry mutations through a complete reviewed manifest; a package action is one manager operation.
Invariants
- An action is operator-visible.
- An action belongs to one confirmed plan.
Aliases: none.
Non-equivalent concepts: concept-finding, concept-mutation.
Requirements: TJ-PLAN-03, TJ-PLAN-04.
adapter
ID: concept-adapter
An integration that discovers, explains, plans, and executes cleanup for one package ecosystem.
Invariants
- An adapter owns exactly one package ecosystem integration.
Aliases: none.
Non-equivalent concepts: none.
Requirements: TJ-ADAPT-01, TJ-ADAPT-05.
candidate
ID: concept-candidate
A finding the operator may select manually.
Invariants
- Every candidate is a finding.
- Candidate status alone never authorizes mutation.
Aliases: none.
Non-equivalent concepts: concept-finding, concept-recommended-candidate.
Requirements: TJ-CORE-02, TJ-CLASS-13.
effect set
ID: concept-effect-set
The manager-level transaction items reviewed for a package action, including packages, cache scope, indirect operations, and declared hook invocations. It does not claim to enumerate every internal filesystem write performed by the manager.
Invariants
- An effect set is manager-level rather than file-level authority.
Aliases: none.
Non-equivalent concepts: none.
Requirements: TJ-ADAPT-06, TJ-ADAPT-07.
finding
ID: concept-finding
A retained filesystem item or package-manager operation shown in the unified checklist.
Invariants
- A finding is retained and operator-visible.
- Finding status alone never implies selection or recommendation.
Aliases: none.
Non-equivalent concepts: concept-candidate, concept-action.
Requirements: TJ-CORE-03, TJ-UI-01.
manual-only candidate
ID: concept-manual-only-candidate
A sensitive candidate that may be selected individually but is never pre-selected or selected by a bulk command.
Invariants
- Individual operator selection is required.
- Recommendation and bulk selection are forbidden.
Aliases: none.
Non-equivalent concepts: concept-recommended-candidate.
Requirements: TJ-CORE-03, TJ-CLASS-13.
mutation
ID: concept-mutation
One change to a filesystem entry or package-manager-owned state.
Invariants
- A mutation changes exactly one filesystem entry or package-manager-owned state.
Aliases: none.
Non-equivalent concepts: concept-action.
Requirements: TJ-CORE-01, TJ-EXEC-02.
recommended candidate
ID: concept-recommended-candidate
A candidate pre-selected by a high-confidence safety rule.
Invariants
- Every recommended candidate is a candidate.
- Every recommendation has high-confidence evidence and an explanation.
Aliases: none.
Non-equivalent concepts: concept-candidate, concept-manual-only-candidate.
Requirements: TJ-CORE-04, TJ-CLASS-15.
workspace
ID: concept-workspace
A configured root containing personal source repositories.
Invariants
- Workspace content remains manually selectable but is never recommended by default.
Aliases: none.
Non-equivalent concepts: none.
Requirements: TJ-CLASS-13, TJ-SCAN-01.