Nothing here is a summary written after the fact. These are the problem, mechanism,
and move of each article, in the reading order, joined by its own connective lines.
Any one of them opens into the full argument.
Begin with the boundary almost everyone believes in, the view that hides material, and with the reason it protects nothing whatsoever.
Audience fields, filtered views, and hidden panels look like access controls and are built like them, so material gets placed in a shared repository on the strength of a setting that decides nothing about who holds the file.
Mechanism
A projection is computed from material it must already possess, so hiding is a property of the output while the input travels intact to everyone with the repository, and the only place a read can be prevented is the boundary deciding who gets a copy.
Move
Decide exposure by placement. If material must not be read by a group, it goes in a repository that group cannot clone, and no view, flag, or filter is accepted as a substitute for that.
A second boundary gets crossed the same quiet way, when a system treats work being finished as permission to send it to somebody.
Pipelines that verify their own output tend to treat the last green check as clearance, so the act of completing work silently becomes the act of releasing it and nobody notices the two were ever separate.
Mechanism
Readiness is a property of the artifact and authorization is a choice within a relationship, so a system deriving the second from the first has converted finishing into consent and removed the moment at which a person could decline.
Move
Build the pipeline with no send path at all, so releasing is a separate act by a named person rather than the last step of a build that has been going well.
Both repairs point at one shape, a read path that was never built, which is the only privacy posture with no failure rate to speak of.
Guarded access fails the way all behavioral safety fails, one bug or one persuaded actor at a time, and private context sits behind exactly such guards in nearly every multi-agent system shipping today.
Mechanism
A read path that does not exist has no failure rate; Signal under subpoena could produce only what it possessed, and a domain-locked architecture eliminates cross-domain reads rather than mitigating them.
Move
Design the boundary as absence: scope every actor to its domain, and let shared spaces receive only what a person deliberately carried across.
Structural arguments have a limit and it earns publishing, so turn to a case where every structural assertion held and the person still could not type.
A regression test can assert continuity precisely, pass honestly, and still be the reason a defect survives, because continuity is not the property the person at the screen depends on.
Mechanism
A continuity check answers whether the same element is still present and still focused, and no combination of those answers says where it is, so a contract built only from continuity assertions is satisfied by a layout that puts the element off the screen.
Move
Write on-screen geometry into the acceptance contract alongside continuity, so the composed test asserts that the thing a person is typing into sits inside the rectangle they can see.
The same review turned up a second finding, about what a system does when two of its parts are each allowed to decide one fact.
The same state is often classified in more than one place in a running system, and each classifier is correct given the evidence it accepts, so the disagreement never surfaces as a fault.
Mechanism
Two independent decisions about one fact produce two answers that never meet, so the system never holds a contradiction, only two truths, each locally consistent and consumed by a different half of the layout.
Move
Name one owner for each fact a system acts on, make every consumer read that owner, and treat a second place that decides the same thing as a defect on sight rather than a redundancy.
You have walked The boundary is not the view end to end: the hidden panel that ships its own contents, the finished artifact that sends itself, the read path built as an absence, the acceptance contract that measured everything except where the thing was, and the fact with two owners. Each of them is a boundary drawn in the wrong place, and in every case the repair was to move the line rather than to guard it harder.