sync-orientation-docs

To keep orientation docs in sync after structural changes, perform a full-doc scan and count verification to detect stale references and downstream inconsistencies. You then review surgical edit proposals before applying them, ensuring the navigation layer stays trustworthy without losing review control.

Tracing cascade effects involves scanning the full orientation doc set to detect hidden references impacted by changed names, folders, or skills. Cascade-aware proposals trace these structural changes across related docs to ensure no downstream inconsistencies are missed before edits are applied.

Yes, you can update documentation references without losing review control by using a safe change workflow. The process requires a full-doc scan and proposed edit reporting before any changes are applied, producing surgical edits instead of applying changes directly.

You need to run a documentation coherence check for repo maintenance after file operations, status transitions, structural changes, or skill edits. These actions can ripple through navigation docs, requiring a full-doc scan and count verification to identify stale references.

The best way to find stale references in a second-brain repository is performing a doc coherence check. This reads the full orientation doc set to locate downstream inconsistencies and hidden references, generating cascade-aware proposals for exact replacements before applying changes.

A limitation of synchronizing orientation docs is that the process cannot apply changes directly. It requires count verification, cascade detection, and proposed edit reporting first, meaning you must manually review and approve surgical edits before the navigation docs are updated.