{ "schema": "org-writing@v1", "slug": "the-unambiguous-half", "kg": { "id": "org:writing:the-unambiguous-half", "type": "brick", "graph": "/kg.json" }, "title": "The unambiguous half", "subtitle": "A rule a machine can only half decide is enforced on that half and reported on the rest", "abstract": "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.", "kind": "brick", "topics": [ "Machine judgment" ], "courseMemberships": [ { "course": "org:courses:machine-decides", "topic": "Machine judgment", "wall": "org:walls:engineering", "position": 1, "total": 5 } ], "publishedAt": "2026-08-03T00:00:00.000Z", "version": 1, "guidelinesVersion": 15, "brief": { "problem": { "text": "Automated checks are written as though every rule were fully decidable from the artifact, and a check that fires on cases it cannot read trains the people who read it to dismiss it.", "claims": [ "raised alerts on 18 percent of all hospitalized patients" ] }, "mechanism": { "text": "A rule whose breach is decidable from the artifact alone can be mechanized and failed on, and the half requiring judgment can only be reported, so a mechanized ruling enforces the first half and addresses the second to a person.", "claims": [ "enforces only the unambiguous half of its contract" ] }, "move": { "text": "Split every rule you are about to automate before you automate it, fail the build on the decidable half, and demote the rest to a note that names a human reader.", "claims": [] } }, "sources": [ { "repo": "mnstry-website", "path": "scripts/foundation/registry/practices.json" }, { "repo": "mnstry-website", "path": "scripts/foundation/validators/checks.mjs" } ], "canonicalPath": "/writing/the-unambiguous-half/", "body": "Every practice in the design registry behind one of our own sites carries a field that decides what a build is allowed to do about it. A practice marked as a mechanic is enforced by a named validator check, and a violation fails the build. A practice marked as a ruling is advisory prose, binding on the people who work there and invisible to the machine, until somebody can state it precisely enough for a neutral check to exist. The field looks like a maturity ladder, prose waiting at the bottom to be promoted into enforcement at the top. It is not. It is a declaration about which kind of rule each practice is, and the interesting ones turn out to be two kinds at once.\n\nWatch what happened to the type ruling when it was finally mechanized. The rule says type is set by role rather than by arbitrary size, and half of it proved decidable from the file alone. A declared size below the readable floor is a breach, and the check fails the build and names the file and the literal that did it. The other half is not decidable at all. A size above the floor but outside the role scale might be a lapse or might be a logotype that has earned its exception, and no scan of the source can tell those apart. So the check does something that looks like a compromise and is actually a boundary. Below the floor it fails. Above it, it emits a note, addressed to a person, saying that this size sits outside the role scale and asking them to confirm it earns the exception.\n\nThe mechanism is the split itself, because a rule whose breach is decidable from the artifact alone can be mechanized and failed on while the half that requires reading the situation can only be reported, and a check that cannot distinguish a defensible case from a breach does not produce findings at all, it produces noise, and it spends the build's credibility to do it. We call the enforceable part *the unambiguous half*, and the discipline is refusing to pretend the rest is inside it.\n\nThe motion ruling was cut the same way, and the residue was left in the open. Toggling an element's display property to change state cannot animate, so a state change written that way always pops, and the check fails on it without hesitation. The remainder of that ruling, that reveal motion belongs on a unit's wrapper rather than on the text inside it, stays prose, with a comment in the check explaining precisely why it stayed prose. A class-name scan cannot tell a standalone lead paragraph, which is correct, from inner text inside a card that is also moving, which is the regression. That comment is not an apology for incomplete automation. It is the finding.\n\nWhat a check costs when it rules past its evidence has been measured, and the number comes from a hospital rather than a build. The sepsis prediction model embedded in one of the most widely deployed hospital record systems in the United States raised alerts on eighteen percent of everyone admitted, and the clinicians did what people always do with an instrument that fires on situations it cannot read. They learned to click through. Alert fatigue is not a weakness in the humans; it is the accurate response to a machine claiming more authority than its evidence supports, and every noisy check in a build teaches the same lesson at a smaller scale, one dismissed warning at a time, until the morning the real one arrives and is dismissed with the rest. A machine that fails only on its unambiguous half gives up coverage it never honestly had and keeps the thing worth more, which is the right to be believed the next time it says no.", "apparatus": { "note": "The human-facing essay is deliberately practical; this apparatus carries the full references, evidence-graded claims, article-local concepts, and research context behind it. Canonical concept definitions come from the concept registry.", "references": [ { "id": "org:references:the-unambiguous-half:r01", "author": "MNSTRY (internal)", "work": "Marketing-site practice registry and foundation validator suite", "year": 2026, "relevance": "The primary artifact. Every practice is categorised as a mechanic (enforced by a named validator check) or a ruling (advisory until a neutral validator exists), and the registry's own note states that a mechanized ruling enforces only the unambiguous half of its contract and reports the judgement-dependent half as a note. The type-floor and motion checks are the two worked examples in the brick." }, { "id": "org:references:the-unambiguous-half:r02", "author": "Andrew Wong, Erkin Otles, John P. Donnelly and colleagues", "work": "External Validation of a Widely Implemented Proprietary Sepsis Prediction Model in Hospitalized Patients (JAMA Internal Medicine)", "year": 2021, "relevance": "The alert-burden figure, restated from the discernment essay's apparatus and graded identically. Used here for the cost side of the argument rather than the judgment side." }, { "id": "org:references:the-unambiguous-half:r03", "author": "Clinical decision support and human factors literature", "work": "The alert fatigue literature (override rates for low-specificity interruptive alerts)", "relevance": "The documented consequence of an instrument that fires on states it cannot read. The brick's transfer of this finding from clinical alerting to build checks is its own argument, not a measured result." } ], "claims": [ { "id": "org:claims:the-unambiguous-half:c01", "claim": "An external validation of a widely deployed sepsis prediction model raised alerts on 18 percent of all hospitalized patients.", "basis": "Wong et al., JAMA Internal Medicine 2021; figures are for the cohort and site described there. Restated verbatim from the apparatus of the discernment essay and graded identically.", "confidence": "verified", "sources": [] }, { "id": "org:claims:the-unambiguous-half:c02", "claim": "A design-system practice registry sorts entries into mechanic practices enforced by a named validator check and ruling practices that stay advisory until a neutral validator exists, and a mechanized ruling enforces only the unambiguous half of its contract while reporting the judgement-dependent half as a note.", "basis": "The registry's own category field and its stated note, read directly from the artifact on 2026-08-03.", "confidence": "verified", "sources": [] }, { "id": "org:claims:the-unambiguous-half:c03", "claim": "In the mechanized type ruling, a declared size below the type floor fails the build while a size above the floor but outside the role scale emits a note asking a person to confirm the exception.", "basis": "The validator source read directly; the note branch is explicit in the check and its comment gives the reason, that a logotype may earn a size outside the role scale.", "confidence": "verified", "sources": [] }, { "id": "org:claims:the-unambiguous-half:c04", "claim": "The wrapper-versus-inner-text half of the motion ruling was deliberately left as prose because a class-name scan cannot distinguish a standalone lead paragraph from inner text inside a moving card.", "basis": "The comment carried in the check itself, which states that a check unable to tell them apart reports noise rather than findings.", "confidence": "verified", "sources": [] }, { "id": "org:claims:the-unambiguous-half:c05", "claim": "High volumes of low-specificity interruptive alerts produce high override rates among clinicians, a documented failure mode of clinical decision support.", "basis": "The clinical alert fatigue literature, consistent across settings; the effect is well established, the specific override rates vary by system and site.", "confidence": "verified", "sources": [] } ], "concepts": [ { "id": "org:concepts:unambiguous-half", "name": "The unambiguous half", "definition": "The portion of a rule whose breach is decidable from the artifact alone, and therefore the only portion an automated check may fail a build on. The remainder, the part that requires reading the situation, is reported as a note addressed to a person. A check that rules past its unambiguous half does not produce findings, it produces noise, and it spends the credibility it will need the next time it is right.", "provenance": "canonical" } ], "researchContext": "Sourced from our own marketing-site foundation, where the mechanic/ruling\nsplit and the note branches were built before anyone named the principle;\nthis brick names it. The sepsis alert figure is restated verbatim from the\ndiscernment essay's apparatus so both files grade the same statement\nidentically, and if the essay's grade changes at a version cut this\napparatus is corrected in the same commit.\n\nThe brick's own contribution is the reading of the note branch as a boundary\nrather than a compromise, and the argument that a check ruling past its\nevidence spends credibility it will need later. The transfer from clinical\nalerting to build checks is an argument by structural analogy and is carried\nin the move cell rather than graded as a finding: no study measures\ndeveloper response to noisy build warnings, and the brick does not pretend\none does.\n\nBoundary with the parent essay: discernment argues that nearly every failure\nof judgment is a minor-premise failure, the rule known and its application\nunseen. This brick takes the builder's side of the same argument, where the\nminor premise is exactly the part a scanner cannot supply, and treats the\nnote as the honest way to hand that premise back to a person. The kinship\nwith \"Prose is not behavior\" is direct and the two are kept distinct: that\nbrick concerns what a scanner misreads, this one concerns what it may rule on." }, "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json", "releaseHash": "21d3070e9efdc00833b7427b24a8b74e7209e4e06a548fab87ea2d18edfa7f59", "versions": [ { "version": 1, "cutAt": "2026-08-03", "note": "Initial publication, machine-decides wave", "visibility": "published", "path": "/writing/the-unambiguous-half/", "contentHash": "sha256:e6c5071345a849c5", "releaseHash": "21d3070e9efdc00833b7427b24a8b74e7209e4e06a548fab87ea2d18edfa7f59" } ] }