verify

To verify note schema compliance, run a three-step quality gate that checks description quality, validates frontmatter structure, and performs health checks. This enforces schema requirements and surfaces structural mismatches in your documentation pipeline.

A health check for documentation notes is a periodic probe that detects data drift, consistency issues, and integrity problems. You need it during periodic maintenance to ensure notes remain accurate and aligned with reference schemas over time.

You validate frontmatter fields by applying a schema compliance check that verifies note structure and fields align with the defined schema. This deterministic process surfaces mismatches between the note description and the reference schema.

Yes, the note verification process includes deterministic steps with error handling to manage schema mismatches and frontmatter requirement failures. It applies recite, validate, and review checks to surface issues systematically.

The best way to run a QA gate for note creation workflows is applying combined verification that recites description quality, validates schema compliance, and performs health checks. This enforces frontmatter requirements and maintains data integrity.

You can detect data drift and consistency issues by running periodic health probes as part of the note review process. These health checks identify integrity problems and ensure notes conform to the defined schema over time.