1# Mechanism Registry
2 
3The mechanism registry is the durable index of accepted patterns that can update skills. It exists so novelty checks compare proposed behavior changes, not broad keyword overlap.
4 
5Each line in `registry.jsonl` is one accepted mechanism with:
6 
7- `mechanism_id`: stable kebab-case identifier
8- `owning_skill`: published skill that owns the pattern
9- `activation_scenario`: situation where the mechanism applies
10- `behavior_change`: what a future agent should do differently
11- `evidence`: source URLs or repo artifacts supporting the mechanism
12- `failure_modes`: failures the mechanism prevents
13- `status`: `accepted`, `candidate`, `deprecated`, or `rejected`
14 
15Only `accepted` and `candidate` mechanisms participate in novelty checks. Rejected mechanisms should remain in run logs or rejected proposal files unless they are useful enough to prevent repeated rediscovery.
16 
17## Promotion Flow
18 
19Runs propose mechanisms in `proposals/mechanism-proposal.jsonl`. Promotion is gated:
20 
211. The run must pass run-readiness validation for `accepted` or `candidate` mechanisms.
222. A human reviewer must be recorded.
233. Accepted and candidate mechanisms append to `registry.jsonl`.
244. Every promotion appends an event to `ledgers/accepted.jsonl`.
255. Rejected mechanisms append to `ledgers/rejected.jsonl` so future agents do not rediscover them.
26