validate-kb-extension

Validating knowledge base markdown files requires checking that every feature contains required subsections like Inclusion, Success Criteria, and Cross-Tree Refs, while ensuring referenced feature IDs exist to prevent dangling references.

A knowledge base extension schema contract defines the formatting conventions for domain-taxonomy features. You need it during repository pre-flight checks to enforce section completeness and verify cross-tree constraint references before incomplete entries progress.

To check for dangling feature references, safely parse the cross-tree constraints YAML file and verify that every referenced feature ID exists within the scanned domain-taxonomy markdown files, halting the pipeline if any are missing.

Yes, knowledge base validation applies to enterprise domain-taxonomy files by recursively globbing across all domains and features, extracting ordered feature lists, and generating a deterministic YAML report of completeness and formatting errors.

Automating KB extension contract enforcement involves running rule-driven section validations against the conventions contract file, checking for quantified success criteria and structured failure scenarios, and outputting a structured YAML validation report.

Knowledge base validation fails on incomplete failure scenarios because the rule contract enforcement checks that all five required H3 subsections, including Failure Scenarios, are fully populated and meet the defined KB extension conventions.