Skip to content
MNSTRY.org
Menu Explore

Topic · 5 articles

Boundaries

Five rooms on where a boundary actually is, as opposed to where the interface suggests it is. A view that hides and ships, a pipeline that finishes and sends, an architecture with no path to build a leak out of, an acceptance contract satisfied by an unusable screen, and a fact settled twice. The last two come from a single review and mark the honest limit of the argument the first three make.

Start reading The five-minute version

The through-line: Structural, not behavioral and The agency threshold , the long reads these articles expand on.

  1. 1 Begin with the boundary almost everyone believes in, the view that hides material, and with the reason it protects nothing whatsoever. Projection is not protection
  2. 2 A second boundary gets crossed the same quiet way, when a system treats work being finished as permission to send it to somebody. Readiness is not authorization
  3. 3 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. The unleakable context
  4. 4 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. Mount continuity is not usability
  5. 5 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. Two classifiers, two truths

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.

Practice Pick one thing you keep private by hiding it rather than by placing it. A document in a shared drive with restricted view settings, a file in a repository marked internal, a panel that renders for some people and not others. Ask a plain question about it. If the person you are hiding it from had a copy of the container, would they have the contents? Where the answer is yes, you do not have a boundary, you have a preference, and moving the material is usually a five-minute job you have been deferring for months.

Follow this topic: RSS · agent version