technology-validate

Per-tech standard validation automates compliance checks against defined frontmatter rules and SSOT guidelines. It ensures consistency across tech stacks by verifying required fields like name and description exist, required sections are present, and references are correctly registered.

Yes, you can use automated standard compliance checks as a pre-commit hook. The validation process applies to pre-commit workflows to guarantee standard adherence across technologies before code is committed, ensuring frontmatter and structural guidelines are met.

The best way to verify required sections and references in per-tech standard files is to run an automated structural validation check. It validates that required sections exist, formatting is correct, and all references are correctly registered according to defined SSOT guidelines.

Yes, frontmatter validation checks both name and description fields against SSOT guidelines. The validation ensures these required fields exist and comply with the defined structural rules, guaranteeing standard adherence across different technology stacks.

You need to run per-tech standard validation checks during code reviews, before commits, or when creating and modifying standards. This ensures frontmatter includes required fields, sections exist, and references are correctly registered across technologies.