Normalize local build paths without merging distinct modules
Relative spellings create duplicate graph nodes. Define canonical module identity under an explicit workspace root.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Filesystem · Identity
Estimated field mix
- Developer tooling50%
- Compiler and language tooling30%
- Security20%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Equivalent local paths share identity
- Escaping paths are rejected
- Case behavior is documented per adapter
Implementation constraints
- Do not silently assume case-insensitive filesystems.
Verification to include
- Resolve relative alias
- Reject path escaping fixture root
Deliverables
- Module identity resolver
Rollout and recovery
Disable reuse for ambiguous path identities.
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.