arrow-maintenance

To audit overlay coherence across large projects, run an explicit audit pass that checks reference coherence, coverage, staleness, drift signals, and orphan artifacts between design specs and code references, applying fixes in place.

Detecting drift between LLDs, EARS specs, and code references requires running a deterministic audit that surfaces stale mappings and reference inconsistencies, ensuring your arrow overlay stays aligned across documentation and implementation.

Maintaining arrow overlay coherence without automatic edits uses ambient mode, which surfaces relevant work and catch-and-recommend guidance by detecting drift signals and orphan artifacts without modifying files directly.

Yes, arrow maintenance works on both brownfield and greenfield projects to map and maintain overlay coherence, surfacing drift and stale mappings before they become blockers in your codebase.

Orphan artifacts and stale mappings in your index.yaml overlay occur when design specs, EARS requirements, and code references drift apart over time. A directed audit pass detects these issues and applies fixes in place.

Yes, arrow maintenance targets large projects with an existing docs/arrows overlay structure. It provides ambient guidance when the overlay exists, or you can run an explicit audit for directed passes.