Document task inputs beyond package dependencies
A root compiler change passed CI although an unchanged package no longer compiled. Inventory inputs the planner must treat as shared.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Dependency analysis · Build systems
Estimated field mix
- Developer tooling100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional internal tools team maintains eighteen packages. Engineers currently run everything because the affected-package script occasionally misses downstream consumers.
Setup prerequisites
- Create a local six-package fixture with a dependency cycle, shared compiler configuration, and two example changes.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- List compiler, lockfile, environment, and generator inputs separately.
- Assign an owner and invalidation rule to each input.
- Include one change that legitimately affects every package.
Implementation constraints
- Use the local fixture; do not inspect private repositories.
Verification to include
- Trace a package-only edit to its expected tasks.
- Trace an unknown root input to conservative full selection.
Deliverables
- Input ownership matrix.
Rollout and recovery
Review the matrix before enabling selection; retain full CI as fallback.
Value of the work
For the engineer: Practice graph analysis, reproducible commands, and safe developer-tool failure modes.
For the team: Produce an inspectable CI selection plan that avoids unnecessary work without silently skipping consumers.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.