intent-layer

Files (4)

• SKILL.md
• evals.json · evals/
• capture-protocol.md · references/
• node-anatomy.md · references/

SKILL.md (first lines)

> Hermes: first load `skill_view("graph-powers:graph-engineering")` for native calls and host-policy limits. `content/` paths are `file_path` values relative to the common registered-document parent. Source tools/model frontmatter is not host enforcement.

# Intent Layer

For a diff audit, read `content/skills/intent-layer/references/node-anatomy.md § Diff-scoped advisory audit` only when changed rules, paths, commands, consumers or invariants could contradict instructions. Otherwise report no relevant drift and stop. This route never builds a hierarchy.

For hierarchy work, build the smallest `AGENTS.md` hierarchy that tells an agent where rules change. Start at the root;
add a child only for a subtree with a distinct purpose, owner, tooling or safety rule. Each node
links downward; avoid copying global rules and remove no user decisions.

Read `content/skills/intent-layer/references/capture-protocol.md` while deciding whether a node earns existence and
`content/skills/intent-layer/references/node-anatomy.md` only while writing/auditing its shape. Validate navigation and
applicable instructions from root to target. Stop when every real boundary has one concise owner and
a new child would add no decision-relevant context.

From GrupoUS/graph-powers, MIT.

More from GrupoUS/graph-powers