audit-structure-consistency
Purpose
Audit whether a concept, argument, or graph preserves its declared structural relations and constraints.
Input contract
yamlrequired: [structure, relation_schema, consistency_rules] optional: [source_structure, version_history, exception_rules] constraints: [each inconsistency identifies nodes, relation, and violated rule]
Procedure
- Validate node types, relation types, direction, and required fields.
- Check hierarchy, dependency, cardinality, and cycle constraints.
- Compare versions or source structure where supplied.
- Emit inconsistencies, valid exceptions, and repair questions.
If the structure is internally consistent but leaves required areas unrepresented, consider detect-coverage-gap as the next tactic.
Output contract
yamlproduces: [consistency_report, violated_rules, valid_exceptions, repair_questions] delta_fields: [findings, uncertainties, open_questions]
Quality gates
- Rules and exception policy are declared before checking.
- Structural validity is separated from semantic truth.
Failure and counterexamples
Do not repair a graph silently or call a semantically weak structure consistent merely because it parses.
Provenance map
resolved: audit-structure-consistency


