doc-coverage

To align local documentation with upstream references, run the documentation coverage workflow to scan your project, identify gaps between local docs and source materials, and generate structured TODOs for tracking. It ensures complete, source-backed coverage across bilinear-form lattice packages.

Documentation coverage for lattice theory projects is the process of verifying that local documentation completely and accurately reflects upstream references. It identifies misalignments between reference materials and implemented guidance, enforcing provenance by requiring local upstream copies to validate signatures and constraints.

You can track documentation gaps in lattice packages by using the workflow that generates structured TODO files. It records actionable gaps in docs/GAPS.md and TODO.md, guiding editors through discovery, integration, and verification workflows to fill missing documentation surfaces.

Yes, you need local upstream copies to verify lattice documentation. The workflow enforces provenance by requiring local upstream copies to ensure all local documentation is source-backed, allowing editors to accurately verify signatures and constraints against the original references.

The best way to keep signatures and constraints in sync is to apply a documentation coverage workflow across all in-scope bilinear-form lattice packages. It scans method surfaces against upstream references, guiding editors to fill gaps and verify mathematical signatures.

You should avoid automated documentation alignment for lattice packages when you lack local upstream copies, as the workflow strictly enforces provenance. Without local upstream references to validate against, the system cannot verify signatures, constraints, or track actionable gaps effectively.