1 min read
Resolver vs Skill Resolver
RESOLVER routes durable wiki knowledge to directories; SKILL-RESOLVER routes tasks to skills, tools, CLIs, MCPs, and services.
Resolver Status
This page prevents the two resolver families from blending together. Filing and action routing are adjacent, but they do not own the same decision. Source: User request, 2026-07-01
Comparison
| Question | First page | Output |
|---|---|---|
| Should this become durable knowledge? | Wiki Brain Operating Model | page, section, ledger, generated view, redirect, or no write |
| Where does a wiki page go? | Filing Decision Tree | directory/category |
| Which skill/tool/MCP/service should run? | Capability Routing Map + Skill Resolver | action route |
| What loads at session boot? | Agent Operations Hub | startup context |
Operating Rule
A capture often uses all of them: action resolver to do the work, brain model to choose durable shape, filing resolver to place the result, index/log protocol to close the loop.
Closeout
If this rule changes, update Filing Decision Tree first, then this companion page, relevant directory READMEs, generated packs if routing changed, wiki/_index.md, qmd, and wiki/log.md. Source: Index Logging Protocol, 2026-07-01
Timeline
- 2026-07-01 | Updated this resolver companion to align with the current filing authority stack: Wiki Brain Operating Model for shape, Filing Decision Tree for directory placement, and Index Logging Protocol for closeout. Source: User request, 2026-07-01
- 2026-05-31 | Resolver vs skill-resolver distinction documented. Source: public wiki expansion, 2026-05-31
- 2026-06-27 | Cleaned table formatting so the comparison renders as a compact wiki table. Source: wiki quality pass, 2026-06-27