vibespec-update

To keep architecture documentation aligned with code changes, identify affected domain specs, contracts, and ADRs, then update the targeted sections in place to preserve formatting, references, and cross-links.

You need to update ADRs and INDEX.md when code changes touch architectural boundaries, initialization, or configuration, ensuring specification documents accurately reflect the current file set and system contracts.

The best way to prevent specification drift when modifying domain contracts is to read current specs, determine affected files, and modify content in place following the required format to maintain lockstep between behavior and interfaces.

To update cross-references in specification documents after refactoring, update targeted sections in place while preserving existing formatting and links, then manage ADRs and refresh INDEX.md to reflect the current file set.

Yes, updating architectural boundaries requires modifying domain detail docs and contracts, because specification documents must be read and updated in place to keep code behavior and interfaces synchronized across components.