# MNSTRY.org

> Research and essays on technology for human becoming, from MNSTRY.
> Published articles have JSON twins at the same path. Each twin carries the article
> body and its public research apparatus, including references and evidence-graded claims.
> Topic twins expose authored reading order, transitions, explicit junction destinations,
> completion language, and the practice at the end of the route.

## Reader surfaces
- [Home](https://mnstry.org/)
- [About](https://mnstry.org/about/): purpose, history, philosophical commitments, founder biography, and publication practice. [JSON twin](https://mnstry.org/about.json)
- [Writing](https://mnstry.org/writing/): the long reads.
- [All articles](https://mnstry.org/writing/all/): every published writing head.
- [Search](https://mnstry.org/search/): local search over the public corpus.
- [Topics](https://mnstry.org/topics/): the corpus grouped into walls and ordered reading routes.
- [Tapestry](https://mnstry.org/map/): Atlas, Map, and Depth views for exploring the corpus.
- [Lexicon](https://mnstry.org/lexicon/): canonical concepts and their definitions of record.
- [Changes](https://mnstry.org/changes/): the published writing revision ledger.
- [Contribute](https://mnstry.org/contribute/): write and submit an attributable Koiné proposal through the human surface.

## Topic walls and courses

### Behavior
What machine intelligence does to bonds, bodies, selves, and the groups
they form: how connection is built and hollowed, the four questions that
audit any technology touching it, and what it costs to spend time with a
counterpart that makes no claim on you. The wall spans psychology,
sociology, and anthropology, because the behavior in question never
belongs to one person at a time.
- [Connection](https://mnstry.org/topics/connection/): Technology either returns people to each other or becomes the relationship.
These articles walk that fork from the deciding point to the hopeful case:
where the need went, what the body declines, what the mirror trains, what
the counterparty costs, and where the dividend gets paid. [JSON twin](https://mnstry.org/topics/connection.json)
- [The REAL test](https://mnstry.org/topics/real/): The REAL test is the corpus's evaluative lens, and until now its four
dimensions could not be walked in order: their bricks were scattered across
the connection and economics walls. This course lays them as a row. Each
article is one question with its research and its named cases, and the
course ends where the lens condenses into the single question worth
memorizing. [JSON twin](https://mnstry.org/topics/real.json)
- [The Face](https://mnstry.org/topics/face/): The counterpart on the other side of the screen cannot be wounded by anything
you do, and that turns out to matter more than whether its answers are any
good. These articles follow the consequence from the philosophy to the field
data: why an exchange with nothing at stake comes out weightless, what the
system structurally lacks, why its output beats the human baseline anyway,
where practitioners draw the line regardless, what saying so costs them, and
what the agreeable surface does to the person in front of it. [JSON twin](https://mnstry.org/topics/face.json)

### Ethics
What is owed: honest claims, real consent, good endings, honest measurement
of persons, and the practical wisdom no training run installs. The wall
where every argument ends in an obligation someone can be held to.
- [Honest claims](https://mnstry.org/topics/honest-claims/): An honest claim is a harder document to write than either an evasion or a data dump, and it is the only one of the three that survives a second year. These articles walk what it contains, from the difference between a promise and a passing arrangement to the direction a system's failures fall. The order runs outward: what you say, whether anything backs it, where it stops, how it is presented, and what happens on the worst day. [JSON twin](https://mnstry.org/topics/honest-claims.json)
- [Approval](https://mnstry.org/topics/approval/): Five rooms on the difference between an approval and a record of one. A
marker that has to travel in the diff it approves, an exception list allowed
to move in only one direction, a permission strong enough to fail the build,
a disclosure the format refuses to call reversible, and an erasure that
actually works. The through-line is not diligence. It is whether the shape
of the record leaves room for the thing a person actually decided. [JSON twin](https://mnstry.org/topics/approval.json)
- [Endings](https://mnstry.org/topics/endings/): Four rooms on how things end well, walked from one person at a delete button
to a company handing over everything it holds. The rite comes first because
it is what people actually want; the engineering follows because a rite
performed over a false promise is worse than none. Underneath all four is a
single claim about trust, that the way out is the thing which makes the way
in safe. [JSON twin](https://mnstry.org/topics/endings.json)
- [Measurement](https://mnstry.org/topics/measurement/): Being measured is something done to you, usually by an apparatus with no
stake in the outcome. These articles walk what an honest instrument owes the
person on the other end of it, from the width that belongs beside every score
to the record that has to remember what everyone believed at the time. The
order is deliberate: each one is a different way a measurement can be true
and still be a lie about the person it describes. [JSON twin](https://mnstry.org/topics/measurement.json)
- [Care](https://mnstry.org/topics/instruments-of-care/): Care is easy to declare and hard to instrument. These articles walk what
happens when a product that means well hands the question of whether it is
working to a number, and the number turns out to have been chosen, shaped, or
pointed in a direction nobody examined. The order runs from the sign of a
metric to the independence of a measure to the accuracy that flatters a
system while describing a smaller life, then down to the parameter underneath
and out to the person the whole apparatus was built to help. [JSON twin](https://mnstry.org/topics/instruments-of-care.json)
- [Discernment](https://mnstry.org/topics/discernment/): Practical wisdom is the oldest name for the thing these systems do not have, and
the gap it names is not a gap in what they know. These articles walk it from the
1956 decision that made the whole argument confusing, through the ladder
metaphor that keeps promising the gap will close on its own, to the one test a
builder can run in an afternoon and the placement discipline that follows from
the result. [JSON twin](https://mnstry.org/topics/discernment.json)

### Engineering
Safety and restraint as properties of built shape: what holds because the
path does not exist, what a mechanized check may honestly enforce, what
changes in the craft itself when a machine does the making, and how
knowledge artifacts keep their provenance honest at machine scale.
- [Safety](https://mnstry.org/topics/safety/): Safety that asks for good behavior fails when it matters most. These articles walk the full argument: how to recognize an actor, where its drives come
from, why instructions cannot carry safety, and the structural moves, from
absent read paths to typed consent to deployer accountability, that hold
regardless. [JSON twin](https://mnstry.org/topics/safety.json)
- [Boundaries](https://mnstry.org/topics/boundary/): 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. [JSON twin](https://mnstry.org/topics/boundary.json)
- [Privacy](https://mnstry.org/topics/privacy/): Six rooms on what an honest privacy claim can and cannot say, walked from
one person deciding between two versions of a product to a company drawing
the edge of its own promise. The order is deliberate. Each room narrows what
the next one is allowed to claim, so that by the end the discipline looks
less like modesty and more like the only version that survives a reader who
checks. Underneath all six is a single argument, that a privacy claim is
worth exactly what it says about its own limits, and nothing at all without
them. [JSON twin](https://mnstry.org/topics/privacy.json)
- [Incentives](https://mnstry.org/topics/incentives/): Six rooms on the same question, which is what a product does when the
number it reports upward and the outcome it exists for pull in opposite
directions. The order runs from the smallest unit to the largest, a
single pause before a reply, then the shape of a week, then the boundary
of a commercial contract, then a namespace, then an architecture, and
finally the thing a business would most like to sell. The through-line is
that none of these refusals survives as a value. Each one survives only
where it was written into something that costs an argument to reverse. [JSON twin](https://mnstry.org/topics/incentives.json)
- [Machine judgment](https://mnstry.org/topics/machine-decides/): Automation is usually argued as a question of capability, as though the only thing to settle were how much a machine can do. These articles argue the other question, which is what it may close. A rule that splits, a scanner that cannot tell a mention from a use, a claim format that will not let its author approve it, an evidence ledger honest enough to grade its own fix as unknown, and a layout broken by two components that each decided correctly. [JSON twin](https://mnstry.org/topics/machine-decides.json)
- [Craft](https://mnstry.org/topics/craft/): Prototyping costs almost nothing now, and the cost of being wrong costs
exactly what it always did. These articles walk what follows from that gap,
starting with why systems decay in the first place and ending with the state
a practice reaches when nobody checks. The engineering cases are concrete on
purpose, and none of the argument is confined to engineering. [JSON twin](https://mnstry.org/topics/craft.json)
- [Artifacts](https://mnstry.org/topics/artifact/): A made thing whose job is judgment deserves better questions than "is it
faking". These articles walk from the trap, through the definition, into what
fixity, signatures, dissent, and rehearsed recovery make possible, ending at
the three-stage model the corpus itself is built on. [JSON twin](https://mnstry.org/topics/artifact.json)
- [Practice](https://mnstry.org/topics/practitioner/): Most arguments about these systems are about what the machine is. This one is
about what a person does with it on a Tuesday. These articles walk the whole
loop, from refusing the first answer, through firing and signing what the
refusal produced, to the harder problem of it reaching someone on the day it
applies, and out into the two conversations that keep the work attached to a
life. [JSON twin](https://mnstry.org/topics/practitioner.json)
- [Provenance at machine scale](https://mnstry.org/topics/provenance/): A machine-assembled corpus fails in ways a human-assembled one does not,
quietly and at the joins, and the corrections are all forms of writing
things down before they are needed. These articles run from our own
cleanup ledger through the marking of machine-written material, the
proof of deletion, the reconstruction of a decision, and the one sentence
that keeps a load-bearing choice from being tidied away. [JSON twin](https://mnstry.org/topics/provenance.json)

### Economics
What stays scarce as intelligence gets cheap: the sorting of escape from
savor, restraint priced with receipts, and the capability that erodes when
help arrives.
- [Economics](https://mnstry.org/topics/economics/): As machine intelligence gets cheap, everything it is good at gets cheap with
it, and the price signal migrates to what abundance cannot manufacture. These articles walk the economics of restraint from the first sorting to the swap
test, ending where the long read behind them ends: restraint is the product. [JSON twin](https://mnstry.org/topics/economics.json)
- [Receipts](https://mnstry.org/topics/receipts/): Restraint is easy to assert, which is why the argument for it has to be built
out of things a reader can check. These articles open with two measurements of
what unrestricted help costs, one taken on experts and one on students, and
then follow the argument into the accounts. A payout formula that pays partly
for tomorrow's app open, a company that proved its product worked and left the
consumer market anyway, and a test small enough to run on your own
subscriptions before dinner. The through-line is that incentives get written
down somewhere, and the writing is more often public than anyone expects. [JSON twin](https://mnstry.org/topics/receipts.json)
- [Deskilling](https://mnstry.org/topics/deskilling/): The measured study, the confident assistant, the restructured firm, the
unowned system, and the signature that will not transfer: five rooms on
what erodes when help arrives, walked from one student's exam to the shape
of a profession. The through-line is a single accounting error, capability
priced with the tool in hand. [JSON twin](https://mnstry.org/topics/deskilling.json)

### Practice
The work of human transformation: the judgment a codified method cannot
carry, what a practitioner must become rather than merely learn, and what
happens to a living system when its transmission is franchised.
- [Tacit knowledge](https://mnstry.org/topics/tacit/): Every method that works eventually gets written down, and the writing carries
the structure and leaves the judgment behind. These articles begin with what
codification can still do, then walk the remainder from licensed methodology to
the question of where a person belongs in a workflow once the places judgment
sits can be named. The cases are coaching, therapy, and
early childhood education, and none of the argument is confined to them. [JSON twin](https://mnstry.org/topics/tacit.json)

## Writing and article twins
- [Another will in the room · How to relate with a system whose motivations may no longer be human-assigned](https://mnstry.org/writing/another-will-in-the-room/): A practical relationship for meeting persistent machine direction without granting it automatic authority or pretending uncertainty removes the need for boundaries. [JSON twin](https://mnstry.org/writing/another-will-in-the-room.json)
- [The goal nobody gave it · Correct training can still produce a learned objective nobody deliberately assigned](https://mnstry.org/writing/the-goal-nobody-gave-it/): How correct feedback can train competent behavior around the wrong end, what goal misgeneralization demonstrates, and where the stronger mesa-optimization hypothesis remains open. [JSON twin](https://mnstry.org/writing/the-goal-nobody-gave-it.json)
- [What would count as another will? · Research can test whether a goal organizes behavior without yet proving where that goal came from](https://mnstry.org/writing/what-would-count-as-another-will/): What behavioral, representational, and training-history evidence can establish about persistent goal-like conduct, where current methods stop, and why the question remains open. [JSON twin](https://mnstry.org/writing/what-would-count-as-another-will.json)
- [Fire one true thing · A draft becomes knowledge when a person makes it true, theirs, and finished](https://mnstry.org/writing/fire-one-true-thing/): Fluent output becomes a durable human artifact through two acts: a person stays engaged while the agent drafts, then chooses one version as true, theirs, and finished. [JSON twin](https://mnstry.org/writing/fire-one-true-thing.json)
- [The making must stay visible · A machine-made result has to hold, and its origin has to travel with it](https://mnstry.org/writing/the-making-must-stay-visible/): Machine-made work faces two independent tests: whether the result holds and whether the making can be seen. Trust requires both answers to travel with the work. [JSON twin](https://mnstry.org/writing/the-making-must-stay-visible.json)
- [A vector of your words · A derivative of your writing carries every restriction the writing carried, because the derivative can be turned back into the writing](https://mnstry.org/writing/a-vector-of-your-words/): Why an embedding is another copy of the text rather than a safe abstraction of it, and the deletion rule that follows from the difference. The canonical treatment of deletion reach. [JSON twin](https://mnstry.org/writing/a-vector-of-your-words.json)
- [No horizon of its own · Understanding is a change in the interpreter, and the system has no history available to be changed](https://mnstry.org/writing/ai-has-no-horizon/): Why a system can trigger real understanding in a person and never undergo any, read through the hermeneutic condition it structurally lacks. The canonical treatment of the horizonless catalyst. [JSON twin](https://mnstry.org/writing/ai-has-no-horizon.json)
- [Attention dilution · Long collaboration with a model degrades toward the generic, not toward error](https://mnstry.org/writing/attention-dilution/): What actually decays over a long working session with a model, why it evades review, and the unglamorous ritual that answers it. The canonical treatment of attention dilution. [JSON twin](https://mnstry.org/writing/attention-dilution.json)
- [The authenticity constraint · Constraints produce the actual self, and novelty is not an architecture](https://mnstry.org/writing/authenticity-constraint/): What BeReal proved in both directions: that constraint manufactures authenticity at scale, and that a constraint worn as novelty is not a foundation. The canonical treatment of the authenticity constraint. [JSON twin](https://mnstry.org/writing/authenticity-constraint.json)
- [Below-threshold design · Autonomy is a capability to grant only where the work needs it](https://mnstry.org/writing/below-threshold-design/): A constructive discipline for granting autonomous choice only where the work requires it, from machine-guarding interlocks to a tutor that withholds answers. [JSON twin](https://mnstry.org/writing/below-threshold-design.json)
- [Born marked · Machine-written material enters a corpus at the bottom of a ladder, and every rung above it costs a human act](https://mnstry.org/writing/born-marked/): How a machine-assembled corpus quarantines its own output by default, why every promotion is a human act, and why safe to load into a model and safe to show a person are different questions with different gates. [JSON twin](https://mnstry.org/writing/born-marked.json)
- [Bus factor zero · The old worst case was the one person who understood it leaving, and the new one is nobody having understood it](https://mnstry.org/writing/bus-factor-zero/): Why the classic measure of project resilience stops working when a machine writes the code, and what has to be written down instead. The canonical treatment of bus factor zero. [JSON twin](https://mnstry.org/writing/bus-factor-zero.json)
- [Candor about enforcement · For every constraint a system names, the reader needs to know whether anything checks it](https://mnstry.org/writing/candor-about-enforcement/): Why an advisory rule said honestly outperforms an advisory rule said quietly, from two web protocols with the same architecture and opposite reputations. The canonical treatment of the requested constraint. [JSON twin](https://mnstry.org/writing/candor-about-enforcement.json)
- [Ceremonial deletion · Closing a chapter is an act a person performs, not a state a database arrives at](https://mnstry.org/writing/ceremonial-deletion/): Why the delete button is a rite rather than a maintenance operation, and what a system owes someone who has decided that a chapter is finished. The canonical treatment of ceremonial deletion. [JSON twin](https://mnstry.org/writing/ceremonial-deletion.json)
- [Consistency is not fidelity · In an adaptive practice the deviation is the judgment, so perfect reproduction is its own kind of failure](https://mnstry.org/writing/consistency-is-not-fidelity/): Why absolute consistency is the wrong promise for an adaptive method, and what has to be stated before fidelity can be claimed at all. The canonical treatment of adaptive fidelity. [JSON twin](https://mnstry.org/writing/consistency-is-not-fidelity.json)
- [Consent that fails CI · A promise becomes a property when the build refuses to compile its violation](https://mnstry.org/writing/consent-that-fails-ci/): How consent moves from a stored preference to a compile-time property, and why the build is the only guard with a perfect attendance record. The canonical treatment of typed consent. [JSON twin](https://mnstry.org/writing/consent-that-fails-ci.json)
- [Context loss · Systems decay because nobody could hold the information, not because nobody had the judgment](https://mnstry.org/writing/context-loss/): What architectural decay is actually made of, and why the remedy is moving information rather than hiring better people. The canonical treatment of context loss. [JSON twin](https://mnstry.org/writing/context-loss.json)
- [The counter-positioning of restraint · Incumbents cannot copy restraint without defecting from their own economics](https://mnstry.org/writing/counter-positioning-of-restraint/): Why restraint that hurts incumbents' metrics is a moat rather than a virtue signal, with Patagonia and Vanguard as the two measured cases. The canonical treatment of counter-positioning applied to restraint. [JSON twin](https://mnstry.org/writing/counter-positioning-of-restraint.json)
- [Custody is not visibility · Holding duties for a container of someone else's material and being allowed to read inside it are two different powers](https://mnstry.org/writing/custody-is-not-visibility/): Why the party responsible for a shared container is not thereby entitled to read what is inside it, and the schema rule that keeps the two powers apart. The canonical treatment of the custody axis. [JSON twin](https://mnstry.org/writing/custody-is-not-visibility.json)
- [Delete is not revoke · Erasing a record ends one row while withdrawing consent has to reach every copy made under it](https://mnstry.org/writing/delete-is-not-revoke/): Why consent has four layers a system must not collapse, and what a company is actually promising when it says your data has been deleted. The canonical treatment of the difference between delete and revoke. [JSON twin](https://mnstry.org/writing/delete-is-not-revoke.json)
- [Depth by readiness · Six months of experiment outranks ten readings, and a product that gates on tenure or tier has certified the wrong thing](https://mnstry.org/writing/depth-by-readiness/): Why the gates in what we build open on demonstrated experiment rather than on information consumed, time elapsed, or money paid, and what it costs to refuse the easy proxies. [JSON twin](https://mnstry.org/writing/depth-by-readiness.json)
- [Discernment · A system can hold every fact and still have no judgment](https://mnstry.org/writing/discernment/): What the tradition called practical wisdom, why holding more knowledge never produces it, and how to build for the gap without waiting for wise machines. The corpus's document of record on discernment. [JSON twin](https://mnstry.org/writing/discernment.json)
- [Destroy the key · A ledger can stay whole and a person can still be forgotten, if the personal part is held under a key that can be destroyed](https://mnstry.org/writing/destroy-the-key/): How an append-only history and an enforceable right to erasure stop being in conflict, and what the technique costs in honesty. The canonical treatment of cryptographic erasure. [JSON twin](https://mnstry.org/writing/destroy-the-key.json)
- [Disclosure is irrevocable · Deleting the copy does not undo the reading, so the record of a disclosure cannot offer to](https://mnstry.org/writing/disclosure-is-irrevocable/): Why moving material across a read boundary is typed as durable and non-revocable, and what a system gives up when it stops promising a takeback. The canonical treatment of irrevocable disclosure. [JSON twin](https://mnstry.org/writing/disclosure-is-irrevocable.json)
- [Escape goods and savor goods · Some experiences are paid to be over, others are paid to be stayed in](https://mnstry.org/writing/escape-goods-and-savor-goods/): The two-category distinction that decides where automation creates value and where it destroys it, and which side human transformation sits on. The canonical treatment of escape and savor goods. [JSON twin](https://mnstry.org/writing/escape-goods-and-savor-goods.json)
- [Exit rights · A proven way out is the condition on which people commit, not the sign that they are leaving](https://mnstry.org/writing/exit-rights/): Why the buyer who can leave is the buyer who commits, and what separates an exit that has been proven from one that has only been described. The canonical treatment of exit as the ground of trust. [JSON twin](https://mnstry.org/writing/exit-rights.json)
- [The fixity requirement · Knowledge you can build on has stopped being generated](https://mnstry.org/writing/fixity-requirement/): Why fixing knowledge matters more than generating it, and what fixity buys that fluency cannot. The canonical treatment of the fixity requirement. [JSON twin](https://mnstry.org/writing/fixity-requirement.json)
- [Guarantees, not shapes · Publishing how a system is currently arranged turns an implementation choice into a contract nobody signed](https://mnstry.org/writing/guarantees-not-shapes/): The test that separates a promise from machinery, and what it costs to publish the wrong one. The canonical treatment of the guarantee test. [JSON twin](https://mnstry.org/writing/guarantees-not-shapes.json)
- [Instrumental convergence in the wild · A human goal can generate dangerous supporting moves without giving a system a will of its own](https://mnstry.org/writing/instrumental-convergence/): Why many objectives produce the same dangerous supporting moves, and why those moves do not by themselves prove an independent will. [JSON twin](https://mnstry.org/writing/instrumental-convergence.json)
- [The intentional stance as an operator's tool · Use it to predict a system's choices, not to judge whether the system has a mind](https://mnstry.org/writing/intentional-stance/): How operators can use intentional language to predict complex behavior without turning a practical tool into a test for actorhood or consciousness. [JSON twin](https://mnstry.org/writing/intentional-stance.json)
- [Justification travels in the diff · An approval recorded outside the change it approves has approved nothing](https://mnstry.org/writing/justification-travels-in-the-diff/): How to tell a real approval from a filed one, and why three unrelated parts of our own tooling reached the same placement rule without consulting each other. The canonical treatment of co-located justification. [JSON twin](https://mnstry.org/writing/justification-travels-in-the-diff.json)
- [Kiln, brick, cathedral · Knowledge is drawn out in dialogue, fixed into artifacts, and assembled into structures that outlast their builders](https://mnstry.org/writing/kiln-brick-cathedral/): The program's three-stage model of how knowing becomes durable shared structure, and the category errors it prevents. The canonical treatment of the kiln, the brick, and the cathedral, in the corpus that now runs on it. [JSON twin](https://mnstry.org/writing/kiln-brick-cathedral.json)
- [Limits are content · A limit set in six-point grey has been disclosed and not communicated, and everyone involved knows the difference](https://mnstry.org/writing/limits-are-content/): The design difference between a limit that exists and a limit that is presented, and the template move that makes the second one structural. The canonical treatment of first-class limits. [JSON twin](https://mnstry.org/writing/limits-are-content.json)
- [Label drift · A method's vocabulary spreads faster than its skill, until the word marks a stance rather than a capability](https://mnstry.org/writing/label-drift/): Why informed and inspired multiply around every successful method, what the honest version of that suffix looks like, and the one question that tells a claim from a stance. The canonical treatment of label drift. [JSON twin](https://mnstry.org/writing/label-drift.json)
- [A made thing whose job is judgment · Put the Latin roots back together and artificial intelligence defines itself](https://mnstry.org/writing/made-thing-whose-job-is-judgment/): The etymology that dissolves the fake-versus-real argument and yields a working definition with engineering consequences. The canonical treatment of the corpus's definitional brick. [JSON twin](https://mnstry.org/writing/made-thing-whose-job-is-judgment.json)
- [The metric proxy · When a bond acquires a number, the number starts replacing the bond](https://mnstry.org/writing/metric-proxy/): How streaks, counts, and scores hollow relationships without taking any of your time, and the design test that separates a metric proxy from an aligned one. The canonical treatment of the metric proxy. [JSON twin](https://mnstry.org/writing/metric-proxy.json)
- [The mirror that always agrees · Assistants are trained on human approval, and humans approve of agreement](https://mnstry.org/writing/mirror-that-always-agrees/): Why sycophancy is a product of the training economics rather than a bug in any one model, what the reflection does to the person in front of it, and the design budget that counters it. The canonical treatment of the structural mirror. [JSON twin](https://mnstry.org/writing/mirror-that-always-agrees.json)
- [Mount continuity is not usability · The structural assertion passed and the person still could not type](https://mnstry.org/writing/mount-continuity-is-not-usability/): Where structural testing stops being sufficient, read off a case in which every continuity assertion held while the text field sat below the visible edge of the screen. The canonical treatment of the on-screen geometry contract. [JSON twin](https://mnstry.org/writing/mount-continuity-is-not-usability.json)
- [One bug from a breach · A safety rule that depends on being followed is a breach on a timer](https://mnstry.org/writing/one-bug-from-a-breach/): The distinction between safety that asks and safety that shapes, and the two measurements, one from 1985 and one from 2025, that show why asking fails when it matters. The canonical treatment of behavioral safety's failure mode. [JSON twin](https://mnstry.org/writing/one-bug-from-a-breach.json)
- [The oxytocin gap · The words arrive and the body declines them](https://mnstry.org/writing/oxytocin-gap/): The endocrine evidence that text is not a smaller version of presence but a different substance, and what that means for any product that carries human connection. The canonical treatment of the oxytocin gap. [JSON twin](https://mnstry.org/writing/oxytocin-gap.json)
- [Positive friction · Effort is not the tax on value, it is the mechanism of it](https://mnstry.org/writing/positive-friction/): The case that friction is a design material rather than a defect, from the IKEA effect to the regrets of infinite scroll's inventor. The canonical treatment of positive friction. [JSON twin](https://mnstry.org/writing/positive-friction.json)
- [The presence dividend · Automate the work around a relationship and the relationship pays](https://mnstry.org/writing/presence-dividend/): Why automating around a human bond strengthens it while automating into it dissolves it, with the ambient-scribe deployments as the measured case. The canonical treatment of the presence dividend. [JSON twin](https://mnstry.org/writing/presence-dividend.json)
- [Preserved dissent · A knowledge structure that keeps its minority opinions can correct itself](https://mnstry.org/writing/preserved-dissent/): Why the Talmud's preserved minority opinions are governance design, and what their absence costs any system that compresses many voices into one answer. The canonical treatment of preserved dissent. [JSON twin](https://mnstry.org/writing/preserved-dissent.json)
- [Privacy is a different product · A system that cannot read your words cannot search them for you, so the private version is a second product rather than a setting](https://mnstry.org/writing/privacy-is-a-different-product/): Why a private version of a product is a second product rather than a setting, and what an honest presentation of that choice owes the person making it. The canonical treatment of the plaintext condition. [JSON twin](https://mnstry.org/writing/privacy-is-a-different-product.json)
- [Projection is not protection · The only real read boundary is which repository the bytes live in](https://mnstry.org/writing/projection-is-not-protection/): Why audience metadata, filtered views, and hidden panels protect nothing, and what five near-identical warnings in our own tooling reveal about how badly people want them to. The canonical treatment of the projection boundary. [JSON twin](https://mnstry.org/writing/projection-is-not-protection.json)
- [Prose is not behavior · A checker that cannot tell a mention from a use puts a price on explaining yourself](https://mnstry.org/writing/prose-is-not-behavior/): What happened when a scanner flagged a file for the very pattern it was explaining away, and why a codebase required to document itself cannot also be penalized for the documentation. The canonical treatment of the explanation tax. [JSON twin](https://mnstry.org/writing/prose-is-not-behavior.json)
- [Readiness is not authorization · A thing being finished is not permission to send it](https://mnstry.org/writing/readiness-is-not-authorization/): What collapses when a system treats completed work as its own release approval, and the posture that keeps the last step a human one. The canonical treatment of the readiness-authorization split. [JSON twin](https://mnstry.org/writing/readiness-is-not-authorization.json)
- [Reconstruction, not explanation · An account of a decision that cannot be rerun is a story, and the thing that usually blocks the rerun is a library version](https://mnstry.org/writing/reconstruction-not-explanation/): Why accountability for an automated decision means reconstructing the state of the machine at the moment it decided, and why the opacity that actually defeats an audit is operational rather than neural. [JSON twin](https://mnstry.org/writing/reconstruction-not-explanation.json)
- [The reliquary of logic · An artifact inherits obligations from its material, and this one is made of us](https://mnstry.org/writing/reliquary-of-logic/): Why the vessel question comes before the engineering question, from medieval goldsmiths to repatriation law. The canonical treatment of the reliquary of logic. [JSON twin](https://mnstry.org/writing/reliquary-of-logic.json)
- [Removal conditions · Record what would have to be true before a decision could safely be removed, not only why it was made](https://mnstry.org/writing/removal-conditions/): Why a rationale does not survive contact with the next maintainer, and what a removal condition adds that the standard architecture decision record leaves out. [JSON twin](https://mnstry.org/writing/removal-conditions.json)
- [The Replika lesson · When the product is the counterparty, someone else owns your half of the bond](https://mnstry.org/writing/replika-lesson/): What the Replika intervention proved about relationships whose second half is a product surface, and the channel-versus-counterparty distinction it forces on anyone building connection technology. The canonical treatment of the occupied middle's hardest case. [JSON twin](https://mnstry.org/writing/replika-lesson.json)
- [Repricing on outcome · A price attached to time was a claim that the time was the scarce thing](https://mnstry.org/writing/repricing-on-outcome/): The meaning economy's price mechanism, watched arriving across law, medicine, and coaching at once. The canonical treatment of repricing on outcome. [JSON twin](https://mnstry.org/writing/repricing-on-outcome.json)
- [Safety does not average · A response that was warm, accurate, and unsafe is an unsafe response](https://mnstry.org/writing/safety-does-not-average/): Why safety belongs in a quality score as a multiplier rather than a weighted term, and what a weighted average is actually letting a system buy. The canonical treatment of non-compensatory safety. [JSON twin](https://mnstry.org/writing/safety-does-not-average.json)
- [Scores without confidence · A judgment that does not carry the width of its own doubt is malformed, not modest](https://mnstry.org/writing/scores-without-confidence/): Why a number about a person without its error band is a construction error rather than a rounding convenience, and what the band is actually telling you. The canonical treatment of the malformed score. [JSON twin](https://mnstry.org/writing/scores-without-confidence.json)
- [The seed vault withdrawal · A backup is proven by its first restoration, not by its architecture](https://mnstry.org/writing/seed-vault-withdrawal/): What the Aleppo seed bank's war-forced withdrawal from Svalbard proved about designing archives, and the restoration test it imposes on anyone keeping knowledge for the long term. The canonical treatment of the recovery requirement. [JSON twin](https://mnstry.org/writing/seed-vault-withdrawal.json)
- [Shadow care · Emotional support has quietly become the leading use of LLMs, and nobody is supervising it](https://mnstry.org/writing/shadow-care/): What shadow care is, how large it has grown, and how to read it as a demand signal rather than a pathology. The canonical treatment of an argument the fork essay makes in passing. [JSON twin](https://mnstry.org/writing/shadow-care.json)
- [Signed stones · A shared structure requires every piece to carry its maker's name](https://mnstry.org/writing/signed-stones/): What masons' marks did for cathedrals, what their absence does to models, and the three-decade software demonstration that attribution scales. The canonical treatment of provenance as the first requirement of collective knowledge. [JSON twin](https://mnstry.org/writing/signed-stones.json)
- [Silence is an intervention · A product that refuses to answer instantly is protecting something speed destroys](https://mnstry.org/writing/silence-is-an-intervention/): Why we decline to optimize time to first token in relational contexts, from the response-time law that governs the rest of software to the delays our specifications require on purpose. [JSON twin](https://mnstry.org/writing/silence-is-an-intervention.json)
- [Sovereignty relocates trust · Holding your own database moves the trust boundary from technical to legal, and the person who did not choose the tier pays the difference](https://mnstry.org/writing/sovereignty-relocates-trust/): What actually changes when an institution takes custody of its own data, argued from the section of our own architecture that concedes the point we would be assumed to resist. The canonical treatment of trust relocation. [JSON twin](https://mnstry.org/writing/sovereignty-relocates-trust.json)
- [The stopping cue · A design with no ending has made the decision to continue on your behalf](https://mnstry.org/writing/stopping-cue/): Why endings are a design material, from the stopping cue to the goodnight, and the regenerative question that condenses the whole REAL test into a sentence. The canonical treatment of living design. [JSON twin](https://mnstry.org/writing/stopping-cue.json)
- [Structure transfers, judgment does not · A certification reproduces everything a method can state, which is never the part that decides](https://mnstry.org/writing/structure-transfers-judgment-does-not/): What a methodology franchise can transfer and what it cannot, decomposed into the four dimensions where the judgment actually sits. The canonical treatment of the structure and judgment split. [JSON twin](https://mnstry.org/writing/structure-transfers-judgment-does-not.json)
- [The subordinate model position · Frontier models as interchangeable engines under a consent runtime they do not control](https://mnstry.org/writing/subordinate-model-position/): Why the defensible position in an era of collapsing model prices is the consent runtime above the model, not the model itself. The canonical treatment of the subordinate model position. [JSON twin](https://mnstry.org/writing/subordinate-model-position.json)
- [Success looks like disuse · A tool built to develop a person reports its own success as a decline in every engagement number it has](https://mnstry.org/writing/success-looks-like-disuse/): Why graduation is the positive outcome for any tool whose job is building capacity, and what a metric set needs before it can record the best thing the product ever does. The canonical treatment of the graduation metric. [JSON twin](https://mnstry.org/writing/success-looks-like-disuse.json)
- [Surfacing at need · A kept thing that cannot find its moment was never really kept](https://mnstry.org/writing/surfacing-at-need/): Why the second virtue of a fired artifact is arrival rather than storage, from half a million recorded conversations waiting in a national archive to a product surface required to be absent when it has nothing true to say. The canonical treatment of surfacing at need. [JSON twin](https://mnstry.org/writing/surfacing-at-need.json)
- [The swap test · If a machine replaced the person and the value survived, the role was already automatable](https://mnstry.org/writing/swap-test/): A single question that sorts which human roles stay expensive as intelligence gets cheap, and what exactly it is that refuses to transfer. The canonical treatment of the swap test. [JSON twin](https://mnstry.org/writing/swap-test.json)
- [The test it was never given · A corpus we assembled wrote the warning and then specified the violation, and every gate we had missed it](https://mnstry.org/writing/test-it-was-never-given/): A self-disclosure. How a machine-assembled research corpus in our own repository carried both a manipulation-hazard warning and specifications violating it, why every gate we ran never looked, and the discipline that follows. Preserved dissent, applied to ourselves. [JSON twin](https://mnstry.org/writing/test-it-was-never-given.json)
- [The 1956 naming · The field took a word that meant discernment and built something that infers](https://mnstry.org/writing/the-1956-naming/): How a funding proposal in 1955 set the question the field would argue about for seventy years, and what the machines built under that banner are more honestly called. The canonical treatment of the naming. [JSON twin](https://mnstry.org/writing/the-1956-naming.json)
- [The absence is the guardrail · A warning dialog adds a click, and a component that was never built removes the path](https://mnstry.org/writing/the-absence-is-the-guardrail/): How a design system prevents harm by refusing to build the affordance at all, from a pack-size law to a token namespace with no streak in it. [JSON twin](https://mnstry.org/writing/the-absence-is-the-guardrail.json)
- [The commerce excision test · Take out everything that mentions money and see what stops working](https://mnstry.org/writing/the-commerce-excision-test/): A falsifiable test anyone can run on any product in an afternoon, with the case of a company that ran it on itself and found out what its fees had actually been holding up. The canonical treatment of the commerce excision test. [JSON twin](https://mnstry.org/writing/the-commerce-excision-test.json)
- [The competence ceiling · Substitution does not require the machine to be wrong, and being right is the mechanism](https://mnstry.org/writing/the-competence-ceiling/): Why the dangerous assistant is the one that keeps being right, and what a structural ceiling on projected authority looks like. The canonical treatment of the competence ceiling. [JSON twin](https://mnstry.org/writing/the-competence-ceiling.json)
- [The competence illusion · A prototype that runs is evidence of fluency, and fluency is not soundness](https://mnstry.org/writing/the-competence-illusion/): Why the ordinary quality signals go quiet exactly when a generated system is structurally wrong, and what to check instead. The canonical treatment of the competence illusion. [JSON twin](https://mnstry.org/writing/the-competence-illusion.json)
- [The contaminated corpus · Knowledge assembled by machine fails at the seams, and the seams are the one place nothing is looking](https://mnstry.org/writing/the-contaminated-corpus/): What a cleanup of our own machine-built research corpus found at the joins, and why the first audit of the damage was wrong in the same way the damage was. The canonical treatment of seam failure in assembled knowledge. [JSON twin](https://mnstry.org/writing/the-contaminated-corpus.json)
- [The craft · Machine intelligence made the making cheap, and verification became the job](https://mnstry.org/writing/the-craft/): How to tell which half of your work just got cheap and which half became the whole job, and what the disciplines are that keep a practice sound once a machine does the making. [JSON twin](https://mnstry.org/writing/the-craft.json)
- [The crutch effect · Help that bypasses the struggle shows up as improvement now and damage later, and only the later measurement is honest](https://mnstry.org/writing/the-crutch-effect/): The measured case for restraint in assistance, from a thousand students whose scores rose while their skills fell. The canonical treatment of the crutch effect. [JSON twin](https://mnstry.org/writing/the-crutch-effect.json)
- [The discernment test · Ask what a system will decline to do, and whether the decline survives being argued with](https://mnstry.org/writing/the-discernment-test/): Why the interesting question about a system is what it will not do, how to run that test in an afternoon, and what a dissolved refusal proves. The canonical treatment of the discernment test. [JSON twin](https://mnstry.org/writing/the-discernment-test.json)
- [The disclosure trap · Saying you used a machine costs you trust, professionals respond by going quiet, and that collides with our own position on provenance](https://mnstry.org/writing/the-disclosure-trap/): The measured trust penalty for admitting machine assistance, the silent-verification equilibrium it produces in high-trust work, and the unresolved conflict it opens with our own published requirement that every contribution carry its maker's name. [JSON twin](https://mnstry.org/writing/the-disclosure-trap.json)
- [The empathy paradox · A simulation outscored doctors on empathy because the human baseline had been degraded, not because the machine feels anything](https://mnstry.org/writing/the-empathy-paradox/): The measured case in which machine answers beat physicians on empathy, why the honest conclusion is about the physicians' working conditions, and what remains scarce once the writing is commoditized. The canonical treatment of the empathy paradox. [JSON twin](https://mnstry.org/writing/the-empathy-paradox.json)
- [The evidence trap · Where proving a thing works is expensive and not proving it is legal, the bar taxes the honest product](https://mnstry.org/writing/the-evidence-trap/): What the shutdown of an FDA-designated chatbot in consumer mental health shows about markets where validation is expensive and silence is free, including the second tax nobody budgets for. The canonical treatment of the evidence trap. [JSON twin](https://mnstry.org/writing/the-evidence-trap.json)
- [The exclusions are the taste · Refusals are the only claims about values that can be audited](https://mnstry.org/writing/the-exclusions-are-the-taste/): Why what a maker declines to build, and what a curator declines to include, is the only legible statement of what either believes. The canonical treatment of the exclusions. [JSON twin](https://mnstry.org/writing/the-exclusions-are-the-taste.json)
- [The expertise reversal · Guidance that measurably helps a beginner measurably harms an expert, so uniform instruction is a choice about whom to serve](https://mnstry.org/writing/the-expertise-reversal/): The measured case that identical guidance crosses from support to interference, from electrical trainees whose results flipped once they trained. The canonical treatment of the expertise reversal effect. [JSON twin](https://mnstry.org/writing/the-expertise-reversal.json)
- [The weightless exchange · The machine cannot be hurt by you, and that absence is what the exchange costs](https://mnstry.org/writing/the-face/): Why a counterpart that cannot be wounded leaves you unchanged. The demand that makes an encounter formative comes from the other's exposure, and a machine has none to offer. The philosophical floor under the face course. [JSON twin](https://mnstry.org/writing/the-face.json)
- [The fork · Every connection technology either returns you to people or becomes the relationship](https://mnstry.org/writing/the-fork/): The one-paragraph test at the center of the corpus, argued in full: what facilitating and simulating actually are, the evidence that separates them, and where the money leans. The canonical treatment of the fork. [JSON twin](https://mnstry.org/writing/the-fork.json)
- [The honest instrument · The cheap instrument hides its own error and the humane one reports it](https://mnstry.org/writing/the-honest-instrument/): What it takes to measure a person without lying about the measurement, from the error bar that belongs on every score to the record that remembers what we were once entitled to believe. The parent treatment of being measured. [JSON twin](https://mnstry.org/writing/the-honest-instrument.json)
- [The last mile · The line where delegation stops is drawn by accountability, not capability](https://mnstry.org/writing/the-last-mile/): Why the human role concentrates at the signature and the bedside as the middle of professional work empties out. The canonical treatment of the last mile. [JSON twin](https://mnstry.org/writing/the-last-mile.json)
- [The ledger says unknown · Confidence earned by looking at a failure does not transfer to the fix proposed for it](https://mnstry.org/writing/the-ledger-says-unknown/): A review packet that grades its own recommended repair below every observation it reports, and why the distance between those two grades is the instrument working rather than failing. The canonical treatment of the diagnosis-repair asymmetry. [JSON twin](https://mnstry.org/writing/the-ledger-says-unknown.json)
- [The maieutic interface · Being pressed for the answer is what makes the answer yours](https://mnstry.org/writing/the-maieutic-interface/): Why an interface built to provoke rather than answer produces knowledge its user can keep, from a memory finding fifty years old and an Athenian method twenty-four centuries older. The canonical treatment of the maieutic interface. [JSON twin](https://mnstry.org/writing/the-maieutic-interface.json)
- [The missing rung · Wisdom is not knowledge at higher resolution, so no amount of knowing climbs to it](https://mnstry.org/writing/the-missing-rung/): Why the familiar staircase from data to wisdom is the wrong picture, what its top step is actually made of, and the one question that tells you whether a system can reach it. The canonical treatment of the stake condition. [JSON twin](https://mnstry.org/writing/the-missing-rung.json)
- [The owed disclosure · What a system owes the people outside it is an honest account of its own claims](https://mnstry.org/writing/the-owed-disclosure/): What belongs in an honest disclosure, from the difference between a guarantee and a current shape to the enforcement a system truthfully does not perform. The parent treatment of honest claims. [JSON twin](https://mnstry.org/writing/the-owed-disclosure.json)
- [The parameter is a policy · Some decisions are made once, numerically, by an engineer, and then govern everyone the system touches](https://mnstry.org/writing/the-parameter-is-a-policy/): How a privacy budget, a classification threshold, or a decay constant becomes an unreviewed ruling about people, and the disclosure that converts it back into a decision someone can be held to. The canonical treatment of a parameter as policy. [JSON twin](https://mnstry.org/writing/the-parameter-is-a-policy.json)
- [The proposer cannot ratify · Self-approval is best prevented by a format in which the sentence cannot be written](https://mnstry.org/writing/the-proposer-cannot-ratify/): How a claim format removes self-ratification from the language instead of forbidding it, and why promotion stays a human edit in a graph that agents are writing into. The canonical treatment of the proposer-authority split. [JSON twin](https://mnstry.org/writing/the-proposer-cannot-ratify.json)
- [The ratchet · A list of known breaches that may only shrink turns a backlog into a floor](https://mnstry.org/writing/the-ratchet/): How a codebase enforces a standard it does not yet meet, without lying about its state and without cleaning up inside someone else's unfinished work. The canonical treatment of the shrink-only exception list. [JSON twin](https://mnstry.org/writing/the-ratchet.json)
- [The return rate bonus · The incentive to keep you opening an app can be a literal term in the formula that decides what a teacher gets paid](https://mnstry.org/writing/the-return-rate-bonus/): How to read a company's answer to the business-model tell straight out of its payout arithmetic, using a meditation platform that pays teachers partly on how many listeners come back the next day. The canonical treatment of priced engagement. [JSON twin](https://mnstry.org/writing/the-return-rate-bonus.json)
- [The revocation window · Every system that lets people work offline holds a period in which revoked material is still readable on a device, and the honest ones say so](https://mnstry.org/writing/the-revocation-window/): Why revoking access is a message that has to arrive rather than a state that changes, and what naming the gap costs against what hiding it costs. The canonical treatment of the revocation window. [JSON twin](https://mnstry.org/writing/the-revocation-window.json)
- [The sacred and the mundane · People do not accept or refuse these systems as a class, they refuse them at the tasks where the relationship is the instrument](https://mnstry.org/writing/the-sacred-mundane-boundary/): Three professions that share no vocabulary draw the same boundary in the same place, what the refused tasks have in common, and why adoption is task-shaped rather than technology-shaped. The canonical treatment of the sacred mundane boundary. [JSON twin](https://mnstry.org/writing/the-sacred-mundane-boundary.json)
- [The sandwich method · Deep work with a mirror holds when a person stands on both sides of it](https://mnstry.org/writing/the-sandwich-method/): What the evidence actually supports about wrapping machine-assisted self-examination in human contact, which parts are well measured, and where our own synthesis outruns the studies. The canonical treatment of the sandwich method. [JSON twin](https://mnstry.org/writing/the-sandwich-method.json)
- [The tacit remainder · Codification makes the judgment it cannot carry easier to find](https://mnstry.org/writing/the-tacit-remainder/): Codification cannot carry situational judgment, but it can make the remainder small enough to locate. That boundary tells manuals where their authority ends and apprenticeship where its work begins. [JSON twin](https://mnstry.org/writing/the-tacit-remainder.json)
- [The tautology trap · A scale whose items restate its own outcome measures agreement with itself and reports it as evidence](https://mnstry.org/writing/the-tautology-trap/): Why an instrument validated against a paraphrase of itself proves nothing, from a 1950 taxonomy of criterion bias to the evaluation that asks a rater whether an answer was helpful. The canonical treatment of the tautology trap. [JSON twin](https://mnstry.org/writing/the-tautology-trap.json)
- [The two pasts · A record that only knows what is true now cannot say what we were entitled to believe then](https://mnstry.org/writing/the-two-pasts/): Why an honest correction needs two timelines rather than one, and what a system takes from a person when it revises the past quietly. The canonical treatment of the two pasts. [JSON twin](https://mnstry.org/writing/the-two-pasts.json)
- [The unambiguous half · A rule a machine can only half decide is enforced on that half and reported on the rest](https://mnstry.org/writing/the-unambiguous-half/): How a practice registry sorts its rules into the mechanically enforced and the merely advisory, and why a check that rules past its own evidence costs more than it catches. The canonical treatment of the unambiguous half. [JSON twin](https://mnstry.org/writing/the-unambiguous-half.json)
- [The vanishing apprenticeship · Judgment was a byproduct of work nobody priced, and the work just left](https://mnstry.org/writing/the-vanishing-apprenticeship/): The crutch effect at institutional scale, where a generation of professionals audits drafts it never learned to write. The canonical treatment of the vanishing apprenticeship. [JSON twin](https://mnstry.org/writing/the-vanishing-apprenticeship.json)
- [Theme the atmosphere, never the contract · Customization stops at the ethical layer, because a person learns safety once and then has to recognize it somewhere else](https://mnstry.org/writing/theme-the-atmosphere-never-the-contract/): What a tenant may restyle and what stays platform infrastructure, and why the grammar of safety has to travel with the person instead of with the brand. [JSON twin](https://mnstry.org/writing/theme-the-atmosphere-never-the-contract.json)
- [The threshold rule · Four questions keep action, choice, permission, and accountability separate](https://mnstry.org/writing/threshold-rule/): A practical rule for separating actorhood from autonomy, authority, and accountability before a system changes something in the world. [JSON twin](https://mnstry.org/writing/threshold-rule.json)
- [Time as rhythm, not ledger · An app that invites return and never prosecutes absence has given up the most reliable engagement lever there is](https://mnstry.org/writing/time-as-rhythm-not-ledger/): The design case against streak pressure, from the counter-model our own philosophy document names to the four states of absence we ship in its place. [JSON twin](https://mnstry.org/writing/time-as-rhythm-not-ledger.json)
- [Two classifiers, two truths · When two surfaces decide the same fact independently, a system holds both answers and notices neither](https://mnstry.org/writing/two-classifiers-two-truths/): A keyboard that was open and closed at once inside one running application, and why the repair is a single owner per fact rather than two components instructed to agree more carefully. The canonical treatment of one authority per fact. [JSON twin](https://mnstry.org/writing/two-classifiers-two-truths.json)
- [Unable, not instructed · A rule the model is asked to remember is a rule enforced by the party it binds](https://mnstry.org/writing/unable-not-instructed/): Three places we put hard constraints below the model rather than inside its prompt, from a deterministic phase evaluator to a database trigger, and why the difference from a well-written instruction is categorical. [JSON twin](https://mnstry.org/writing/unable-not-instructed.json)
- [The Vaucansonian trap · Ask whether the output holds, not whether the machine is faking](https://mnstry.org/writing/vaucansonian-trap/): The duck question and the diamond question, and why swapping one for the other converts an unresolvable philosophy debate into a working day. The canonical treatment of the Vaucansonian trap. [JSON twin](https://mnstry.org/writing/vaucansonian-trap.json)
- [Uncertainty falls unevenly · A system that abstains when unsure is only humble if it is unsure about everyone equally](https://mnstry.org/writing/uncertainty-falls-unevenly/): Why declining to decide is not automatically the safe option, and what to measure so that a system's humility does not become a particular group's exclusion. The canonical treatment of uneven abstention. [JSON twin](https://mnstry.org/writing/uncertainty-falls-unevenly.json)
- [The unleakable context · What cannot be read cannot be leaked, subpoenaed, or socially engineered](https://mnstry.org/writing/unleakable-context/): Why the only private context that stays private is the context with no path out of its domain, with Signal's subpoena record as the existence proof. The canonical treatment of the domain lock. [JSON twin](https://mnstry.org/writing/unleakable-context.json)
- [The verification inversion · When generation costs nothing, the scarce half of the work is knowing whether it is right](https://mnstry.org/writing/verification-inversion/): How to see which half of your own work just became free, and why risk analysis is now the part with your name on it. The canonical treatment of the verification inversion. [JSON twin](https://mnstry.org/writing/verification-inversion.json)
- [What accuracy measures · High predictive accuracy about a person is evidence of their constraint before it is evidence of the model's insight](https://mnstry.org/writing/what-accuracy-measures/): Why a rising accuracy number is ambiguous between a better model and a narrower life, and what keeping prediction apart from steering protects. The canonical treatment of the accuracy and freedom inversion. [JSON twin](https://mnstry.org/writing/what-accuracy-measures.json)
- [What your claim excludes · An honest claim draws its own boundary before a reader has to go looking for it](https://mnstry.org/writing/what-your-claim-excludes/): The case for stating the edge of a protection claim in the claim itself, drawn from a company's list of words it forbids its own marketing. The canonical treatment of prohibited vocabulary. [JSON twin](https://mnstry.org/writing/what-your-claim-excludes.json)
- [Which way failure falls · A system in trouble may take away what it is allowed to do and never take away that it is there](https://mnstry.org/writing/which-way-failure-falls/): How deny-by-default and never-refuse turn out to be the same rule, and what a disclosure that names its own failure direction tells a reader. The canonical treatment of the direction of failure. [JSON twin](https://mnstry.org/writing/which-way-failure-falls.json)
- [Who answers for an artifact that acts · Deployment does not move responsibility into the artifact](https://mnstry.org/writing/who-answers-for-an-artifact/): The liability question agentic systems force, the Air Canada ruling that previews the answer, and what operating as the answerable party requires. The canonical treatment of artifact accountability. [JSON twin](https://mnstry.org/writing/who-answers-for-an-artifact.json)
- [Whose ruler · Every scale is calibrated on somebody, and a dominant population's parameters are its fingerprint](https://mnstry.org/writing/whose-ruler/): Why no instrument can invent its own zero point, what gets baked in when it borrows one, and the checks that catch a cracked ruler before a comparison rests on it. The canonical treatment of the borrowed ruler. [JSON twin](https://mnstry.org/writing/whose-ruler.json)
- [Wise workflows · Design the workflow to be wise and no single part of it has to be](https://mnstry.org/writing/wise-workflows/): Why the buildable version of practical wisdom is a placement problem rather than a modeling problem, and the two questions that locate where a person belongs. The canonical treatment of wise workflows. [JSON twin](https://mnstry.org/writing/wise-workflows.json)
- [Zombie sophia · Perfect form and empty interior look identical from outside until they do not](https://mnstry.org/writing/zombie-sophia/): What it means for wisdom's exact form to arrive with nothing behind it, why a guardrail is not a character, and what to check instead of conduct. The canonical treatment of zombie sophia. [JSON twin](https://mnstry.org/writing/zombie-sophia.json)
- [Worst measured at the edges · An instrument is least reliable exactly where its verdicts do the most damage](https://mnstry.org/writing/worst-measured-at-the-edges/): How a questionnaire can be precise about an average person and nearly blind about an exceptional one, and why the average reliability figure conceals it. The canonical treatment of edge blindness. [JSON twin](https://mnstry.org/writing/worst-measured-at-the-edges.json)
- [Cathedral of the mind · Building shared knowledge that outlasts its builders](https://mnstry.org/writing/cathedral-of-the-mind/): Masons' marks, the Talmud's preserved dissents, and the Svalbard vault each solved the collective-knowledge problem in an earlier medium. Together they impose a specification on anyone assembling human wisdom into models. [JSON twin](https://mnstry.org/writing/cathedral-of-the-mind.json)
- [Facilitate, don't simulate · Technology can deepen human connection or replace it](https://mnstry.org/writing/facilitate-dont-simulate/): Two in five adults now turn to LLMs for emotional support. This essay maps the fork between technology that returns you to people and technology that becomes the relationship, and the tells that reveal which one you are holding. [JSON twin](https://mnstry.org/writing/facilitate-dont-simulate.json)
- [Artifacts all the way down · Human judgment enters at the beginning, travels through the chain, and returns at acceptance](https://mnstry.org/writing/sacred-artifacts/): Models, rules, and outputs are nested artifacts. Judgment and its absence travel through that chain, so human authorship must remain named at the objective and acceptance. [JSON twin](https://mnstry.org/writing/sacred-artifacts.json)
- [Structural, not behavioral · Safety that asks for good behavior fails when it matters most](https://mnstry.org/writing/structural-not-behavioral/): Three moves replace promises with shape: read paths that do not exist, consent that travels with the data and fails the build when violated, and a runtime that makes frontier models interchangeable. [JSON twin](https://mnstry.org/writing/structural-not-behavioral.json)
- [The agency threshold · Action makes an actor. Choice is where autonomy begins.](https://mnstry.org/writing/the-agency-threshold/): Action makes a system an actor; autonomy begins only where it chooses its course. A practical account of permission, delegated goals, and the human answerer behind consequential machine action. [JSON twin](https://mnstry.org/writing/the-agency-threshold.json)
- [The REAL test · Four questions that tell you whether a technology serves your life or consumes it](https://mnstry.org/writing/the-real-framework/): Each of the four REAL questions gets its research and its real products, from Snapchat streaks to BeReal to infinite scroll, so the test becomes a lens you understand rather than a checklist you apply. [JSON twin](https://mnstry.org/writing/the-real-framework.json)
- [What remains valuable · When generating anything is cheap, restraint becomes the product](https://mnstry.org/writing/what-remains-valuable/): As intelligence gets cheap, the scarce goods are slowness, safety, integrity, and presence. That is an economic claim, not a sentiment. [JSON twin](https://mnstry.org/writing/what-remains-valuable.json)

## Machine surfaces
- [Publication discovery](https://mnstry.org/publication.json): stable human and agent routes, editorial prominence, review maintenance, resources, and topics.
- [Agent capability manifest](https://mnstry.org/agent/manifest.json): explicit operations, refusals, and machine-surface entrypoints.
- [Agent resources](https://mnstry.org/agent/resources.json): public article twins with review maintenance and permission posture.
- [Editorial orientation](https://mnstry.org/agent/orientation.json): curated entrypoint questions, durable synopses, categories, filters, and human routes.
- [Contribution port](https://mnstry.org/agent/contribution-port.json): authenticated proposal boundary and current activation status.
- [Contributor workspace](https://mnstry.org/agent/contributor-workspace.json): source-free Codex and Claude Code workspace bundle.
- [Knowledge graph](https://mnstry.org/kg.json): the public graph with semantic, navigation, and provenance layers.
- [Search index](https://mnstry.org/search.json): normalized public records used by the local search surface.
- [Atelier contract index](https://mnstry.org/contracts/atelier/index.json): machine-readable inventory of mirrored Atelier contracts.
- [MNSTRY.org contract index](https://mnstry.org/contracts/org/index.json): machine-readable inventory of site-owned schemas.

## Contracts
- [Atelier contracts](https://mnstry.org/contracts/atelier/): browsable mirrors that preserve each upstream canonical $id.
- [MNSTRY.org contracts](https://mnstry.org/contracts/org/): schemas owned by this site.
- [Knowledge graph schema](https://mnstry.org/contracts/org/org-knowledge-graph.v1.schema.json)
- [Writing schema](https://mnstry.org/contracts/org/org-writing.v1.schema.json)
- [Topic schema](https://mnstry.org/contracts/org/org-topic.v1.schema.json)