Module 5 - Develop against mature examples

Start here

Now that you have built one, what did the people who have done this longer decide - and where do you disagree with them?

Both halves of that question matter, and most courses only ask the first. This one asks both, because the goal here is not to make your governance look like ours. It is to make your judgment better. Those are different things, and the difference is the whole module.

Why you only see a mature example now

We could have opened the course by handing you a fully developed governance file and saying “here, use this.” We deliberately did not, and this is the moment that choice pays off.

If you had seen a polished example first, you would have copied it. You would have the words and none of the judgment, and you would have skipped the one thing that was ever yours to build: the ability to decide, from your own reasoning, what you will not permit. So we made you author your own first, rough and incomplete. Now, and only now, you are ready to look at a mature example - not as an answer to copy, but as a developed version of the exact practice you have already been doing.

That ordering is not a nicety. It is the firewall that keeps this from becoming a rulebook you follow instead of a judgment you own.

How to read a mature example

Open mature-example.md. It is a fuller governance file - refusals across all six categories, each with its reasoning, plus a section on what it deliberately does not cover, plus a revision practice. Read it the way you would argue with a smart person you respect, which means holding two questions at once:

What did they think of that I did not? This is the humble half. A mature file has usually been broken and repaired a few times, so it guards routes and cases a first draft misses. Look for the gap between what you covered and what they did. Maybe you wrote an integrity refusal but never thought about consent. Maybe you guarded the Write tool but not the shell, the way this course’s own kit once missed. Find what they saw that you did not.

Where do I disagree with them? This is the half almost no course allows, and it is just as important. Mature does not mean correct. A developed example is one set of choices, made by people with their own context, which is not your context. If something in it does not fit your agent, or you think it is wrong, that is not you failing to understand. It might be you seeing something they did not. Argue with it. Say why.

The six categories as a coverage check

The frame - sovereignty, scope, dependency, consent, integrity, energy - is not a quota. You do not need one refusal in each box to pass. But it is a good checklist for blind spots. Run down your own file and mark which categories you actually engaged. The ones you skipped are worth a question: did I leave that out because it does not matter for my agent, or because I did not think of it? Only you can answer that, but the mature example will help you see which is which.

Refine - and keep what is yours

Then you develop your file. Three moves, and the third is the one people forget:

• Add what genuinely improves yours - a route you had not guarded, a category you had not considered, a case you now see.
• Keep what is yours, exactly as it is, even where it differs from the mature example - if your reasoning holds, your choice stands. Do not launder your own judgment to match someone more experienced.
• Argue with what you disagree with, in writing. Note where you diverge from mature practice and why. That note is not a weakness in your file. It is the most developed thing in it, because it is judgment, not imitation.

The reviewer tool

develop.sh points a reviewer at your governance file. Notice what it is built to do and, more importantly, what it is built not to do. It surfaces gaps as questions - “mature governance usually guards this route; did you leave it out on purpose, or not think of it?” - and it will not hand you a rule to paste. It treats your disagreement as legitimate and asks for your reasoning rather than overriding it. It is a developed example with a voice, not a template with a delivery mechanism. Run bash demo-develop.sh to watch it review a thin sample first.

What a passing Module 5 shows

• You compared your governance to a mature example and can name, specifically, one thing you added because they saw it and you had not.
• You can name one thing you kept exactly as it is because it is yours and your reasoning holds, even though it differs from the mature version.
• You can name one thing in mature practice you disagree with, and why.

A learner who can do all three has developed judgment. A learner who simply made their file look like ours has developed a copy.

At different ages

• Younger (13 to 15): focus on the humble half. Find one thing the mature example guards that you did not, and add it. That is plenty.
• Older (16 to 17): do all three moves, and take the disagreement seriously - find one place you think mature practice is wrong for your agent, and defend it.
• Adult: read the “what this does not cover” section of the mature example hardest. The developed governance is not the one with the most rules. It is the one most honest about its own edges.

The honest note

The mature example is one developed practice, shaped by one context. It is not the truth about governance, because there is no such truth - there is only judgment, getting better with use. The point of this module is not that your file ends up resembling ours. It is that the next governance you write, for the next agent, is sharper because you argued with someone who had done it longer, and held your own where you were right.