noCV
CBUILD-103 · Establish dependency identity

Detect static-build dependency cycles with a readable path

Practice briefTaskIntermediate

Recursive imports hang graph traversal. Detect cycles and return the concrete edge path.

Focused work estimate
2h 15m + prerequisites
Priority in the scenario
High
Engineering practice
Graphs · Algorithms

Estimated field mix

  • Compiler and language tooling60%
  • Developer tooling40%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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

  • Acyclic graph builds
  • Cycle includes involved modules
  • Repeated traversal terminates

Implementation constraints

  • Bound reported cycle length for large inputs.

Verification to include

  • Traverse diamond graph
  • Introduce three-node cycle

Deliverables

  • Cycle detector and fixtures

Rollout and recovery

Refuse cyclic graph outputs until cycle policy is defined.

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.