Part II · Chapter 2 · The Boundary · lesson 11
Write yours, and let the referee read it back
15 min
Builds on Count what is inside the line before you draw it
Ten lessons of somebody else's boundary. Now yours, in your own words, and the test is the one the field below states: whether you would read it out to a customer.
Three things to get into it, in roughly this order.
What is inside, as nouns you could count. Not the platform and its supporting infrastructure — the systems, named or counted, and the people, named or counted. If you do not know the counts, write the counts you believe and note that you believe them. A number you are unsure of is still a number somebody can check; an adjective is not.
The predicate you used. The sentence that decides borderline cases, written so that a stranger would sort them the same way you did. Holds or can reach customer records is a predicate. Core is not.
What is outside, named. At least one thing. Preferably the three from the milestone of this track, each with what it holds and why it is out. This is the part that almost no first attempt contains, and the part that does the most work in front of a reader.
Your own register
Nothing here is graded, and nothing here leaves your browser unless you are signed in. A filled-in register is an inventory of your known weaknesses, so keep the real one where your auditor can see it — this is somewhere to think.
One or two sentences, in your own words. The test is whether you would read it out to a customer.
Reading it back
Read your own sentence once more, out loud if you are somewhere you can.
Three questions, and they are the three a reviewer asks without saying so. Can somebody count from it? Does a borderline system sort the same way for them as for you? And is there anything in it you would not want to say in a call — because if there is, that is the sentence you will be asked about, and it is cheaper to fix now than to defend later.
Then the referee.
What does not line up
What your boundary now disagrees with
Nothing yet, because there is nothing in here yet. An empty workspace has no contradictions and tells you nothing.
These are contradictions between things you wrote. Nothing here can tell you whether any of it is enough — that is a judgement, and it moves with the auditor, the boundary and the year.
What it is doing above is narrow and worth being precise about. It is comparing the things you have written against each other. A control whose owner sits in a team your boundary excludes. Evidence whose period does not touch the window you declared. A system you put inside the line in one lesson and never mentioned again — which is the signal this whole track has been building towards, because a system inside the line with no control naming it and no evidence attached is the exact shape of the thing that produces a question you cannot answer.
It is not telling you whether the boundary is good. It cannot: that judgement needs an auditor, a buyer and a year, and nothing in here is any of those. The count it shows rises as you fill the workspace in honestly, which is the one property that makes it safe to look at — a number somebody has deliberately made larger cannot be screenshotted and sent to a customer as a claim.
And it is blind to the largest category of problem. It cannot see the system you never wrote down. The free tool connected to production with an API token, the spreadsheet the finance process depends on, the contractor's laptop: all of those are outside your boundary by omission rather than by decision, and omission looks identical to a clean register from in here. The only instrument for that is going and looking.
If the panel found nothing
That is a statement about your workspace, not about your organisation, and the most likely explanation is that there is not much in it yet. An almost-empty register has no contradictions by construction. It is the least informative state the thing can be in, and it is the state that feels best, which is a combination worth distrusting.
The useful next move is the one that makes the number go up: go back and record the control you are least comfortable with, or the exclusion you are least confident in, and see what it collides with.
Worth remembering
- A boundary a reader can use contains three things: countable nouns, the predicate that sorts borderline cases, and at least one named exclusion.
- A number you are unsure of is still checkable; an adjective is not.
- Read it out loud — anything in it you would not say in a call is the sentence you will be asked about.
- The referee compares what you wrote against what else you wrote. It has no opinion on whether the boundary is good, and neither does anything else you could install.
- A system inside the line with no control naming it and no evidence attached is the shape that produces a question you cannot answer.
- The engine is blind to the system you never wrote down; omission looks identical to a clean register from inside, and the only instrument for it is going and looking.
- No contradictions in an almost-empty register is the least informative state available, and the one that feels best.