structure-validate

You can validate your project's SSOT structure by running a scan that checks the README, .instructions directory, folder hierarchy, and internal links to ensure they stay coherent and consistent before release.

SSOT validation identifies and reports inconsistencies in a project's Single Source of Truth. It is needed after repository structural changes, during audits, or before releases to prevent documentation drift and broken references.

Checking for broken internal links and README inconsistencies involves scanning key project artifacts and cross-links to detect drift. This process confirms that the README and .instructions directory match the approved folder tree.

Yes, you can audit your project's folder hierarchy and documentation without external dependencies. The validation protocol independently scans repository artifacts to produce a structured report of any structural inconsistencies.

The best way to detect documentation drift after repository changes is to run an automated SSOT validation protocol that scans core artifacts like the README and .instructions directory, outputting a structured report of inconsistencies.

Your validation report shows missing .instructions files because the SSOT validation protocol scans for the presence and consistency of key documentation, flagging absent or incoherent artifacts in the project directory.