audit-structure-consistency
Purpose
Audit whether a concept, argument, or graph preserves its declared structural relations and constraints.
Input contract
required: [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
produces: [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
1---2name: audit-structure-consistency3description: "Detect cycles, contradictions, orphans, type violations, and structural incoherence in a knowledge model."4metadata:5 source: https://skillmd.com/skills/yogsoth-ai/audit-structure-consistency6---78# audit-structure-consistency910## Purpose1112Audit whether a concept, argument, or graph preserves its declared structural relations and constraints.1314## Input contract1516```yaml17required: [structure, relation_schema, consistency_rules]18optional: [source_structure, version_history, exception_rules]19constraints: [each inconsistency identifies nodes, relation, and violated rule]20```2122## Procedure23241. Validate node types, relation types, direction, and required fields.252. Check hierarchy, dependency, cardinality, and cycle constraints.263. Compare versions or source structure where supplied.274. Emit inconsistencies, valid exceptions, and repair questions.2829If the structure is internally consistent but leaves required areas unrepresented, consider `detect-coverage-gap` as the next tactic.3031## Output contract3233```yaml34produces: [consistency_report, violated_rules, valid_exceptions, repair_questions]35delta_fields: [findings, uncertainties, open_questions]36```3738## Quality gates3940- Rules and exception policy are declared before checking.41- Structural validity is separated from semantic truth.4243## Failure and counterexamples4445Do not repair a graph silently or call a semantically weak structure consistent merely because it parses.4647## Provenance map4849- `resolved: audit-structure-consistency`50