The Learning Loop
One problem a week, everywhere at once.
One problem a week. The same problem across every channel — the pattern, a policy you can run, a scenario you can break, a signed record you can verify.
How it works
Each week takes one execution pattern and points every channel at it. Because the loop runs on the pattern library, the substance of a week exists before the week begins — what gets produced weekly is the outward-facing half.
Over a year this covers fifty-two specific problems. That is how a category gets built — not by describing the category, but by owning the problems inside it one at a time.
Week 1
Prevent an AI coding agent from deleting production.
The most viscerally understood failure in the category, and the one people already fear without being sold on it.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 2
Prevent margin leakage at checkout.
The wedge that is already live in production, with a number a finance team recognises.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 3
Prevent an agent spending money nobody approved.
Everyone running agents has felt this, and almost nobody has a control for it.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 4
Control what an agent sends out.
The security question that decides whether agents reach production at all.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 5
Require the approval a deploy assumes it has.
Branch protection that the automation itself holds the credentials to satisfy.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 6
Stop the payment that clears a stale check.
High value, heavily controlled, and still failing in the gap between review and release.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 7
Grant the narrowest access that works, and expire it.
Standing privilege is the most common precondition of an incident.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 8
Decide what an agent may read, and what it may keep.
Retrieval quietly widens the blast radius of every later action.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 9
Let support move fast without letting policy drift.
Individually small, collectively enormous — the classic invisible leak.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 10
Stop the same last unit selling twice.
A measurable marketplace penalty, not a hypothetical risk.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 11
Check delegated authority before the order posts.
Segregation of duties is usually assumed rather than checked.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Week 12
Govern changes to the rules, not only actions under them.
Every control has an edit button; loosening one is the fastest way to make a blocked action succeed.
- A copyable GitHub example
One repository per problem. Only decionis/govern is public today.
- A 60-second demonstration
Recorded against the sandbox scenario above.
- A written walkthrough
Titled for the problem, not for our category vocabulary.
Runway
Twelve weeks are scheduled against a fifteen-pattern library. Naming what is unscheduled is more useful than discovering it in month four.
What the loop produces is measured in the Decionis Index.