epistemic-protocols / route
AGENTS.md175 starsChanged 37 days agoMITView on GitHub
Responsibility under the Northstar (root AGENTS.md). A protocol helps only if it arrives before a misalignment hardens, and a person cannot be expected to remember every protocol at that moment. This plugin puts what the agent needs to bring the fitting protocol in at the head of its context, and it is one way a user takes up the optional premise layer (premise/README.md). Boundary. The plugin carries no skill. purpose.md is the one home of the two protocols to reach…
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aitesis/AGENTS.mdAGENTS.md
- analogia/AGENTS.mdAGENTS.md
- anamnesis/AGENTS.mdAGENTS.md
- .claude/principles/AGENTS.mdAGENTS.md
- design/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- epharmoge/AGENTS.mdAGENTS.md
- epistemic-cooperative/AGENTS.mdAGENTS.md
- euporia/AGENTS.mdAGENTS.md
- heuresis/AGENTS.mdAGENTS.md
- horismos/AGENTS.mdAGENTS.md
- hyphegesis/AGENTS.mdAGENTS.md
- hypotyposis/AGENTS.mdAGENTS.md
- katalepsis/AGENTS.mdAGENTS.md
- lean/AGENTS.mdAGENTS.md
- merismos/AGENTS.mdAGENTS.md
- periagoge/AGENTS.mdAGENTS.md
- proplasma/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- encapsulationSkill
- formal-reviewSkill
- outcomeSkill
- realizeSkill
- rederiveSkill
- releaseSkill
- verifySkill
The file
Files
route/ — the delivery layer
Responsibility under the Northstar (root AGENTS.md). A protocol helps only if it arrives before a misalignment hardens, and a person cannot be expected to remember every protocol at that moment. This plugin puts what the agent needs to bring the fitting protocol in at the head of its context, and it is one way a user takes up the optional premise layer (premise/README.md).
Boundary. The plugin carries no skill. purpose.md is the one home of the two protocols to reach for first; hooks/ and scripts/ are the delivery machinery that puts it, the protocol table and the premise index in front of the agent at session start, and scripts/route-premise.mjs holds that index. evals/ holds the routing cases and the harness that measures whether a delivered premise is applied. Each protocol's own contract stays in that protocol's directory; Route adds no checkpoint of its own.
Next. purpose.md, then README.md for which parts are experimental.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

