Automation★ 233
Decapod
A repository governance kernel can attach optional Jev trajectory observations to its assurance loop while retaining deterministic policy, interlocks and proof rules.
How it uses Jev
Optionally judges how likely a proposed coding trajectory is to satisfy declared intent from bounded governance and repository context.
Why it's interesting
Adds a typed, durable observation to an existing assurance workflow without giving the model approval, policy or completion authority.
How often does Jev run?
How often this project calls Jev has not been established yet.