Key build caches from every semantic input
A cache hit reuses generated clients after the schema changed because only source-directory files contribute to the key.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Build caching · Hashing · Reproducibility
Estimated field mix
- DevOps70%
- Developer tooling30%
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 TypeScript monorepo has twelve packages and a local CI simulator. Pull requests wait for redundant work, stale caches occasionally pass broken changes, and superseded runs continue consuming executors. Create synthetic package graphs and fake check APIs; no hosted CI credentials or production repositories are supplied.
Setup prerequisites
- Dependency graphs
- Process exit codes
- Test isolation
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Cache identity includes command, toolchain, environment contract, direct inputs, and dependency outputs
- Secrets and absolute workspace paths are excluded
- Restore verifies metadata before using outputs
Implementation constraints
- A cache hit may improve speed but cannot waive required checks.
Verification to include
- Repeat an identical build and verify a safe hit.
- Change schema, compiler version, and an upstream output independently and require misses.
Deliverables
- Canonical cache manifest and invalidation tests
Rollout and recovery
Enable read-only restore before allowing new cache writes.
Value of the work
For the engineer: Practice treating CI as a versioned delivery system with correctness, latency, and recovery constraints.
For the team: Review a pipeline that reduces wasted compute without allowing stale or skipped checks to approve changes.
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.