hierarchy-construction

name	hierarchy-construction
description	Tactic for building is-a and part-of hierarchies — establish parent-child relationships, verify transitivity, detect cycles.
execution	tactic
used-by	ontology-building, domain-scoping, relation-typing, taxonomy-validation

Hierarchy Construction

Build taxonomic hierarchies using component_of and instance_of edges. Ensure hierarchies are acyclic, transitive, and complete.

Available SOPs

• edge-batch-creation — create hierarchy edges in bulk
• hierarchy-visualization — inspect current hierarchy structure
• gap-detection — find missing intermediate levels
• consistency-checking (tactic, peer) — verify no cycles

Guiding Principles

• Acyclic always. A cycle in a hierarchy is a logical error. Detect and break immediately.
• Intermediate levels matter. Jumping from "machine learning" directly to "Adam optimizer" skips useful structure.
• Multiple inheritance is fine. A concept can belong to multiple parents (component_of multiple things).
• Depth ≤ 5. Hierarchies deeper than 5 levels are usually over-specified.

Minimum Yield

≥3 hierarchy edges created per invocation. If the hierarchy is already complete for the current scope, report and exit.