validate-omni

To validate OmniCode files against a parent template, apply a full validation check to the target file, surfacing structural drift issues and actionable recommendations. This enforces config-driven rules from block-structures, pragma-types, and required-sections.

Derives_from chain verification confirms template lineage by checking the derives_from metadata field. This ensures an OmniCode file accurately tracks its parent template hierarchy across code, documentation, and data files to prevent structural drift.

Checking pragma correctness and block sequences requires validating the OmniCode file against its template's config-driven rules. This process ensures the correct block sequence and pragma types are present to maintain structural integrity.

Yes, you can use template validation to perform required metadata checks across documentation files. It enforces required sections and metadata compliance to ensure documentation adheres to the parent template structure.

The best way to prevent structural drift in OmniCode files is running a full validation against the parent template. This surfaces issues with pragma correctness, block sequences, metadata, and derives_from chains quickly.

OmniCode files fail required sections checks during validation when they do not adhere to the config-driven rules defined by their parent template. The validation process surfaces these structural compliance issues along with actionable guidance.