Include transform configuration in static-build cache identity
Changing compiler options reuses output produced under older options. Hash normalized inputs and configuration.
- Focused work estimate
- 2h 45m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Caching · Canonicalization
Estimated field mix
- Developer tooling50%
- Compiler and language tooling30%
- Performance engineering20%
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
Fictional static documentation compiler Rowan transforms synthetic text modules through a deterministic local adapter. It never executes candidate source as code.
Setup prerequisites
- Create a synthetic module graph and deterministic transform stub.
- Provide file-change, missing-input and interrupted-output fixtures.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Same inputs reuse output
- Changed options invalidate
- Transform version participates in key
Implementation constraints
- Hash canonical configuration, not property insertion order.
Verification to include
- Reorder equivalent config keys
- Change output-affecting option
Deliverables
- Cache-key contract and cases
Rollout and recovery
Disable cache reuse after unknown configuration changes.
Value of the work
For the engineer: Practice dependency graphs and cache correctness.
For the team: Inspect whether build speed improvements preserve output correctness.
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.