Skip to content
Back to skills

Construct Hierarchy

ASecurity

Construct an acyclic is-a/part-of/instance-of hierarchy with explicit roots, depth, and transitivity constraints.

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
researchnode

Works with

  • cli

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill construct-hierarchy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Construct Hierarchy?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Construct Hierarchy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-construct-hierarchy/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-construct-hierarchy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: construct-hierarchy
description: "Construct an acyclic is-a/part-of/instance-of hierarchy with explicit roots, depth, and transitivity constraints."
---

# construct-hierarchy

## Purpose
Construct an acyclic is-a/part-of/instance-of hierarchy with explicit roots, depth, and transitivity constraints.

## Input contract
```yaml
required: [entity_set, relation_assertions, hierarchy_scope]
optional: [root_policy, multiple_inheritance_policy, depth_limit]
constraints: [relations use declared types; cycles are invalid]
```

## Procedure
1. Normalize entity identifiers and relation types.
2. Insert high-confidence edges and infer only declared transitive edges.
3. Detect cycles, orphan nodes, missing intermediate levels, and root violations.
4. Repair or quarantine invalid edges, then emit roots, depth, and edge rationale.

If the hierarchy is complete enough to test for cycles, orphans, and incompatible parentage, consider `audit-structure-consistency` as the next tactic.

## Output contract
```yaml
produces: [hierarchy_graph, roots, depth_report, cycle_report, edge_rationales]
delta_fields: [findings, evidence_updates, uncertainties]
```

## Quality gates
- Graph is acyclic and every node has an allowed path to a root or an explicit orphan status.
- Transitive closure does not introduce relation-type violations.
- Depth is reported; depth >5 requires explicit justification.

## Parameterization
Caller supplies entity schema, relation ontology, root and multiple-inheritance policies, transitivity rules, and depth limit.

## Failure and counterexamples
Reject an edge that creates a cycle or conflates is-a with part-of.

## Provenance map
- resolved: hierarchy-construction
- intermediate: Pass4/map-field-taxonomy

## Preserved source criteria ledger

| source | criterion |
|---|---|
| hierarchy-construction | Acyclic always; cycles are logical errors. |
| hierarchy-construction | Multiple inheritance is allowed. |
| hierarchy-construction | Depth <=5 unless explicitly justified. |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…