HDD Propagate

Code-to-doc reverse propagation works by analyzing modified source files and mapping them to affected design documents using the modules frontmatter field. It optionally applies AI-assisted updates to the docs while preserving existing frontmatter and providing human-in-the-loop review gates.

The best way to keep design docs aligned is an automated reverse propagation workflow with guardrails. It maps source code changes to affected design docs using the modules field and provides human-in-the-loop gates to review AI-assisted updates, preventing unintended edits and reducing manual review overhead.

To run code-to-doc propagation in an HDD-driven workflow, execute the command 'hdd propagate --path .' from your root hdd project directory. This analyzes your latest modified source files and reverse-propagates the changes into affected design documents.

Yes, code-to-doc propagation requires a modules field in your design docs frontmatter. You need a root hdd project setup where design documents contain this modules frontmatter to map changed source code files to their corresponding affected documents.

Yes, AI-assisted updates can optionally update affected design docs while strictly preserving existing frontmatter formatting. The workflow includes guardrails and human-in-the-loop gates to ensure formatting remains intact and unintended edits are avoided during the reverse propagation process.

The main limitation of AI-assisted reverse propagation is the strict prerequisite for a root hdd project and modules frontmatter. While guardrails and human-in-the-loop gates prevent unintended edits, users must still manually review AI-assisted updates to ensure documentation accuracy during troubleshooting.