{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"$schema":"https://miscsubjects.com/api/knowledge-action-schema","object_type":"knowledge-action","editorial_profile":{"id":"kao:editorial-profile","version":"1.0.0","derived_from":"prose the owner accepted, principally /a/bpc-157","precedence":["1. article-class rule (this profile, for your class)","2. surface rule (instructions.surface_scope on the writing law)","3. core writing clause (families: hostility, compression, commitment, concrete, register, invariant, conformance)","4. optional preference — never blocks publication, never cited as a defect"],"resolution_order":"Apply the narrowest applicable rule. Where a rule at one level permits and a rule at a lower level forbids, the prohibition wins. Where two rules at the SAME level collide, that is a defect in the law: fix the clauses, do not pick a winner silently.","house":{"spelling":"US English. 'organized', 'labeled', 'analyze', 'fiber', 'hematocrit'.","dates_in_prose":"4 August 2026 — day, month spelled, year. No ordinals, no slashes.","dates_in_tables_and_metadata":"2026-08-04 (ISO).","titles":"Sentence case. Capitalize only the first word and proper nouns. No title case.","quotations":"Double quotes for quoted speech and verbatim source text. Single quotes only inside a quotation. A verbatim quote is never silently trimmed; use an ellipsis in brackets for an omission.","units":"Space between number and unit: 10 mg, 4 mL, 60 µg/kg. Exception: 50% and 37 °C. Use µg not mcg in study reporting; use mcg only when quoting a vial label or a syringe mark.","percentages":"One decimal place when the source gives one (70.4%); whole numbers otherwise (70%). Never invent precision the source lacks.","ranges":"En dash, no spaces: 200–500 mcg, 2013–2026. 'between X and Y' in prose where the dash would be ambiguous.","numbers":"Spell out one to nine in prose unless it carries a unit or is a study count. Numerals for everything else.","identifiers":"PMID 37559207, NCT07437547 — bare, uppercase prefix, no punctuation between prefix and number."},"evidence_states":{"measured":"A number was recorded under a stated method. Give the number.","observed":"Seen and reported, but not quantified under a controlled method.","reported":"A person or party says it happened. Attribution required.","consistent with":"Does not contradict the hypothesis, and does not establish it.","not tested":"The experiment that would decide it has not been run.","unsupported":"Asserted somewhere, with no evidence behind the assertion.","cannot be inferred":"The available evidence is of the wrong kind to reach this claim.","unresolved":"Evidence exists on both sides and does not decide it. Say what would.","open":"A live question the page is deliberately not closing. Say what would close it."},"classes":{"compound":{"matches":"A single substance: bpc-157, tb-500, ara-290, kpv, ghk-cu, dsip, thymosin-alpha-1.","families":["evidence","medical","canonical_resource","sources","plain_language","rhythm","harm"],"title":"Entity: plain definition or deliverable. 'BPC-157: body protection compound' conforms.","required_blocks":["evidence-state block, above the argument","commercial-relationship disclosure, relationship only, never the identity","the five questions in order: what it is, where it comes from, how it works, why that would help, what was measured","dosing arithmetic shown as arithmetic, with a dose-to-syringe-marks table","regulatory status with the date it was checked","counted report record with its search method and denominator"],"reference":"/a/bpc-157","opening":"Sentence 1: what the thing is, in words a stranger owns. Sentence 2: the decisive state — the verdict, or the boundary of the evidence. No third sentence describing the page. 'What follows is organized around it' and every variant is framing language and is cut.","ordering":"Decision-relevant finding first, then the evidence chain needed to believe it. Within the evidence chain, strongest first: human, then animal with species and model, then mechanism, then the counted reports. Mechanism may precede the evidence chain ONLY when the mechanism is itself the decisive finding — that is the case on /a/bpc-157 and it is conforming.","headings":"A heading states a literal finding or a physical mechanism, in a human voice. Vivid is allowed and good when it is literal: 'Nobody has ever tested it on a disc' and 'Storage has a hard clock on it' both conform. Banned: mood, claims of importance, and analogy that adds no information.","paragraphs":"One reasoning movement per paragraph: claim, its support, then its consequence or its limit. A new claim resting on different evidence starts a new paragraph.","second_person":"'You' is permitted for a decision the reader will actually make — 'if you source it anyway, here is what to check'. It is not permitted to assign the reader a role, a job or a business (that is the invariant family), and not permitted for exhortation.","technicality":"Keep an identifier, a measurement name, or a term the reader will meet on a label, a scan report or a forum — and translate it in the same sentence, once. Push receptor-level and assay-level detail into a source card when the main inference does not need it.","form":"Prose for causal reasoning. Table for the same dimensions repeated across items. Numbered list for an ordered sequence. Bullets only for mutually exclusive options. Source card for one evidence object. Widget for a relationship or a calculation the reader would otherwise do by hand.","citations":"A citation attaches to the smallest complete claim it supports, and supports nothing around it by proximity. A table carries sources per row, or one clearly labeled group source for the whole table.","subject_boundary":"Background becomes its own article only when it answers a question a person would search separately. Otherwise it is a section here. This is the resolution between 'spin off anything needing context' and 'one subject, one article'.","ending":"End on the last fact, limit, or open question that could change a decision. No recap, no conclusion heading, no invitation, no generic caution.","revision":"Preserve accepted sentences, headings and structure. Rewrite only when the evidence changed, a clause is violated, or the owner rejected that wording. Preferring a different phrasing is not a reason, and rewriting on that basis destroys work that was already judged good."},"condition":{"matches":"A disease or injury: degenerative-disc-disease, herniated-disc, sciatica.","families":["evidence","medical","canonical_resource","sources","plain_language","rhythm","harm"],"title":"Plain name of the condition plus what the reader gets.","required_blocks":["natural history first — what happens with no treatment at all, with the numbers","what correlates with symptoms versus what merely appears on a scan","the two-rate model, but only where tissue is lost faster than replaced","standard of care with its evidence and its cost","action thresholds and named red-flag symptoms"],"reference":"/a/herniated-disc","opening":"Sentence 1: what the thing is, in words a stranger owns. Sentence 2: the decisive state — the verdict, or the boundary of the evidence. No third sentence describing the page. 'What follows is organized around it' and every variant is framing language and is cut.","ordering":"Decision-relevant finding first, then the evidence chain needed to believe it. Within the evidence chain, strongest first: human, then animal with species and model, then mechanism, then the counted reports. Mechanism may precede the evidence chain ONLY when the mechanism is itself the decisive finding — that is the case on /a/bpc-157 and it is conforming.","headings":"A heading states a literal finding or a physical mechanism, in a human voice. Vivid is allowed and good when it is literal: 'Nobody has ever tested it on a disc' and 'Storage has a hard clock on it' both conform. Banned: mood, claims of importance, and analogy that adds no information.","paragraphs":"One reasoning movement per paragraph: claim, its support, then its consequence or its limit. A new claim resting on different evidence starts a new paragraph.","second_person":"'You' is permitted for a decision the reader will actually make — 'if you source it anyway, here is what to check'. It is not permitted to assign the reader a role, a job or a business (that is the invariant family), and not permitted for exhortation.","technicality":"Keep an identifier, a measurement name, or a term the reader will meet on a label, a scan report or a forum — and translate it in the same sentence, once. Push receptor-level and assay-level detail into a source card when the main inference does not need it.","form":"Prose for causal reasoning. Table for the same dimensions repeated across items. Numbered list for an ordered sequence. Bullets only for mutually exclusive options. Source card for one evidence object. Widget for a relationship or a calculation the reader would otherwise do by hand.","citations":"A citation attaches to the smallest complete claim it supports, and supports nothing around it by proximity. A table carries sources per row, or one clearly labeled group source for the whole table.","subject_boundary":"Background becomes its own article only when it answers a question a person would search separately. Otherwise it is a section here. This is the resolution between 'spin off anything needing context' and 'one subject, one article'.","ending":"End on the last fact, limit, or open question that could change a decision. No recap, no conclusion heading, no invitation, no generic caution.","revision":"Preserve accepted sentences, headings and structure. Rewrite only when the evidence changed, a clause is violated, or the owner rejected that wording. Preferring a different phrasing is not a reason, and rewriting on that basis destroys work that was already judged good."},"pairing":{"matches":"A compound applied to a condition, or a stack: bpc-157-vs-nsaids, wolverine-stack.","families":["evidence","medical","canonical_resource","sources","plain_language","rhythm","harm"],"title":"Name both sides and the question between them.","required_blocks":["link the parent compound and parent condition articles rather than restating them","what has been tested in the combination itself, stated once, at its real weight","how the factors compound — the comparison of whole combinations, not single items","where the interaction has never been measured, named as a finding"],"reference":"/a/wolverine-stack","opening":"Sentence 1: what the thing is, in words a stranger owns. Sentence 2: the decisive state — the verdict, or the boundary of the evidence. No third sentence describing the page. 'What follows is organized around it' and every variant is framing language and is cut.","ordering":"Decision-relevant finding first, then the evidence chain needed to believe it. Within the evidence chain, strongest first: human, then animal with species and model, then mechanism, then the counted reports. Mechanism may precede the evidence chain ONLY when the mechanism is itself the decisive finding — that is the case on /a/bpc-157 and it is conforming.","headings":"A heading states a literal finding or a physical mechanism, in a human voice. Vivid is allowed and good when it is literal: 'Nobody has ever tested it on a disc' and 'Storage has a hard clock on it' both conform. Banned: mood, claims of importance, and analogy that adds no information.","paragraphs":"One reasoning movement per paragraph: claim, its support, then its consequence or its limit. A new claim resting on different evidence starts a new paragraph.","second_person":"'You' is permitted for a decision the reader will actually make — 'if you source it anyway, here is what to check'. It is not permitted to assign the reader a role, a job or a business (that is the invariant family), and not permitted for exhortation.","technicality":"Keep an identifier, a measurement name, or a term the reader will meet on a label, a scan report or a forum — and translate it in the same sentence, once. Push receptor-level and assay-level detail into a source card when the main inference does not need it.","form":"Prose for causal reasoning. Table for the same dimensions repeated across items. Numbered list for an ordered sequence. Bullets only for mutually exclusive options. Source card for one evidence object. Widget for a relationship or a calculation the reader would otherwise do by hand.","citations":"A citation attaches to the smallest complete claim it supports, and supports nothing around it by proximity. A table carries sources per row, or one clearly labeled group source for the whole table.","subject_boundary":"Background becomes its own article only when it answers a question a person would search separately. Otherwise it is a section here. This is the resolution between 'spin off anything needing context' and 'one subject, one article'.","ending":"End on the last fact, limit, or open question that could change a decision. No recap, no conclusion heading, no invitation, no generic caution.","revision":"Preserve accepted sentences, headings and structure. Rewrite only when the evidence changed, a clause is violated, or the owner rejected that wording. Preferring a different phrasing is not a reason, and rewriting on that basis destroys work that was already judged good."},"contested":{"matches":"A live or disputed event; anything where sources are parties to the dispute.","families":["conflict","evidence","canonical_resource","sources","plain_language","rhythm"],"title":"Name the event and the disputed proposition.","required_blocks":["event date separate from publication date on every claim","first-hand versus repeated, and each source's affiliation and access limits","verified fact and party claim kept in separate registers","revision history where counts have moved","image and video provenance","a dated change log while the subject is still moving"],"reference":"/a/war-claims-under-an-open-record","opening":"Sentence 1: what the thing is, in words a stranger owns. Sentence 2: the decisive state — the verdict, or the boundary of the evidence. No third sentence describing the page. 'What follows is organized around it' and every variant is framing language and is cut.","ordering":"Established base first — what is not in dispute. Then the disputed proposition, then each party's evidence, then the verdict or the explicit open state. Never lead with the newest claim.","headings":"A heading states a literal finding or a physical mechanism, in a human voice. Vivid is allowed and good when it is literal: 'Nobody has ever tested it on a disc' and 'Storage has a hard clock on it' both conform. Banned: mood, claims of importance, and analogy that adds no information.","paragraphs":"One reasoning movement per paragraph: claim, its support, then its consequence or its limit. A new claim resting on different evidence starts a new paragraph.","second_person":"'You' is permitted for a decision the reader will actually make — 'if you source it anyway, here is what to check'. It is not permitted to assign the reader a role, a job or a business (that is the invariant family), and not permitted for exhortation.","technicality":"Keep an identifier, a measurement name, or a term the reader will meet on a label, a scan report or a forum — and translate it in the same sentence, once. Push receptor-level and assay-level detail into a source card when the main inference does not need it.","form":"Prose for causal reasoning. Table for the same dimensions repeated across items. Numbered list for an ordered sequence. Bullets only for mutually exclusive options. Source card for one evidence object. Widget for a relationship or a calculation the reader would otherwise do by hand.","citations":"A citation attaches to the smallest complete claim it supports, and supports nothing around it by proximity. A table carries sources per row, or one clearly labeled group source for the whole table.","subject_boundary":"Background becomes its own article only when it answers a question a person would search separately. Otherwise it is a section here. This is the resolution between 'spin off anything needing context' and 'one subject, one article'.","ending":"End on the last fact, limit, or open question that could change a decision. No recap, no conclusion heading, no invitation, no generic caution.","revision":"Preserve accepted sentences, headings and structure. Rewrite only when the evidence changed, a clause is violated, or the owner rejected that wording. Preferring a different phrasing is not a reason, and rewriting on that basis destroys work that was already judged good."},"system":{"matches":"A method, capability or system this build operates.","families":["canonical_resource","sources","plain_language","rhythm","surface"],"title":"Name the system and what it does.","required_blocks":["the named kinds of organization that would run it and the situation that makes them","one scenario walked end to end with the clock and the costs running","exact commands, values and expected output"],"reference":"/a/the-build-end-to-end","opening":"Sentence 1: what the thing is, in words a stranger owns. Sentence 2: the decisive state — the verdict, or the boundary of the evidence. No third sentence describing the page. 'What follows is organized around it' and every variant is framing language and is cut.","ordering":"Decision-relevant finding first, then the evidence chain needed to believe it. Within the evidence chain, strongest first: human, then animal with species and model, then mechanism, then the counted reports. Mechanism may precede the evidence chain ONLY when the mechanism is itself the decisive finding — that is the case on /a/bpc-157 and it is conforming.","headings":"A heading states a literal finding or a physical mechanism, in a human voice. Vivid is allowed and good when it is literal: 'Nobody has ever tested it on a disc' and 'Storage has a hard clock on it' both conform. Banned: mood, claims of importance, and analogy that adds no information.","paragraphs":"One reasoning movement per paragraph: claim, its support, then its consequence or its limit. A new claim resting on different evidence starts a new paragraph.","second_person":"'You' is permitted for a decision the reader will actually make — 'if you source it anyway, here is what to check'. It is not permitted to assign the reader a role, a job or a business (that is the invariant family), and not permitted for exhortation.","technicality":"Keep an identifier, a measurement name, or a term the reader will meet on a label, a scan report or a forum — and translate it in the same sentence, once. Push receptor-level and assay-level detail into a source card when the main inference does not need it.","form":"Prose for causal reasoning. Table for the same dimensions repeated across items. Numbered list for an ordered sequence. Bullets only for mutually exclusive options. Source card for one evidence object. Widget for a relationship or a calculation the reader would otherwise do by hand.","citations":"A citation attaches to the smallest complete claim it supports, and supports nothing around it by proximity. A table carries sources per row, or one clearly labeled group source for the whole table.","subject_boundary":"Background becomes its own article only when it answers a question a person would search separately. Otherwise it is a section here. This is the resolution between 'spin off anything needing context' and 'one subject, one article'.","ending":"End on the last fact, limit, or open question that could change a decision. No recap, no conclusion heading, no invitation, no generic caution.","revision":"Preserve accepted sentences, headings and structure. Rewrite only when the evidence changed, a clause is violated, or the owner rejected that wording. Preferring a different phrasing is not a reason, and rewriting on that basis destroys work that was already judged good."},"law":{"matches":"A governing object: writing-law, design-law, operational-logic.","families":["governance","conformance","canonical_resource","plain_language"],"title":"Name the law and its domain.","required_blocks":["clause id, family, and the failure each clause exists to stop"],"reference":"/a/writing-law","opening":"Sentence 1: what the thing is, in words a stranger owns. Sentence 2: the decisive state — the verdict, or the boundary of the evidence. No third sentence describing the page. 'What follows is organized around it' and every variant is framing language and is cut.","ordering":"Decision-relevant finding first, then the evidence chain needed to believe it. Within the evidence chain, strongest first: human, then animal with species and model, then mechanism, then the counted reports. Mechanism may precede the evidence chain ONLY when the mechanism is itself the decisive finding — that is the case on /a/bpc-157 and it is conforming.","headings":"A heading states a literal finding or a physical mechanism, in a human voice. Vivid is allowed and good when it is literal: 'Nobody has ever tested it on a disc' and 'Storage has a hard clock on it' both conform. Banned: mood, claims of importance, and analogy that adds no information.","paragraphs":"One reasoning movement per paragraph: claim, its support, then its consequence or its limit. A new claim resting on different evidence starts a new paragraph.","second_person":"'You' is permitted for a decision the reader will actually make — 'if you source it anyway, here is what to check'. It is not permitted to assign the reader a role, a job or a business (that is the invariant family), and not permitted for exhortation.","technicality":"Keep an identifier, a measurement name, or a term the reader will meet on a label, a scan report or a forum — and translate it in the same sentence, once. Push receptor-level and assay-level detail into a source card when the main inference does not need it.","form":"Prose for causal reasoning. Table for the same dimensions repeated across items. Numbered list for an ordered sequence. Bullets only for mutually exclusive options. Source card for one evidence object. Widget for a relationship or a calculation the reader would otherwise do by hand.","citations":"A citation attaches to the smallest complete claim it supports, and supports nothing around it by proximity. A table carries sources per row, or one clearly labeled group source for the whole table.","subject_boundary":"Background becomes its own article only when it answers a question a person would search separately. Otherwise it is a section here. This is the resolution between 'spin off anything needing context' and 'one subject, one article'.","ending":"End on the last fact, limit, or open question that could change a decision. No recap, no conclusion heading, no invitation, no generic caution.","revision":"Preserve accepted sentences, headings and structure. Rewrite only when the evidence changed, a clause is violated, or the owner rejected that wording. Preferring a different phrasing is not a reason, and rewriting on that basis destroys work that was already judged good."}},"known_defects":[{"where":"/a/bpc-157","defect":"Opening carried two framing sentences — 'This page is the whole file on it' and 'The rest of this page is ordered by that table' — both banned framing language.","resolution":"Both cut, 2026-08-04. The law was right and the prose was wrong.","status":"resolved"},{"where":"writing law, evidence ordering","defect":"The law orders human, animal, mechanism, reports. The accepted BPC-157 page opens on mechanism and tissue evidence.","resolution":"The prose was right. Mechanism may lead when the mechanism IS the decisive finding. Written into COMMON.ordering above.","status":"resolved"},{"where":"writing law W62, live prose","defect":"Live prose uses 'tilts slightly' and 'simply open'; W62 demands a quantity.","resolution":"Both are honest and neither is a hedge. EVIDENCE_STATES enumerates the legal vocabulary for a claim's standing, so qualitative states are named rather than improvised.","status":"resolved"}],"note":"Load the profile for your class plus the clause families it names. A clause outside those families does not apply to your page. Where this profile and a core clause collide, this profile wins for that class — and the collision is reported, because a collision means one of the two is wrong."},"identity":{"id":"kao:writing-law","slug":"writing-law","key":"WRITING_LAW","title":"The Laws of Writing","class":"law"},"content":{"summary":"The complete obligational writing law: opaque, decorative, ambiguous language is hostility toward the reader, and every sentence must carry meaning or be cut.","thesis":"Writing is the transfer of order from one mind to another. Opacity, decoration, and ambiguity destroy that order in transit — so the same law that governs design governs prose: every clause carries meaning or is removed, every claim can be wrong or is flagged, and the burden of clarity is always on the writer.","clauses":[{"id":"W01","family":"hostility","title":"Opacity is hostility","law":"NEVER use a decorative, ambiguous or opaque word. IF a plain word carries the same meaning THEN use the plain word."},{"id":"W02","family":"hostility","title":"Deliver the ordered form","law":"ALWAYS deliver a thought in the order you hold it. NEVER make the reader reconstruct it."},{"id":"W03","family":"hostility","title":"Ambiguity is not politeness","law":"NEVER hedge to avoid commitment. ALWAYS state the thing that could be wrong."},{"id":"W04","family":"hostility","title":"The burden is on the writer","law":"IF a reader asks what a sentence means THEN rewrite it in plainer words with a concrete case. NEVER restate it at the same altitude. NEVER blame the reader."},{"id":"W05","family":"compression","title":"Existence test","law":"A sentence stays ONLY IF it carries a fact, a claim, a number, a name or a position. IF not THEN cut it."},{"id":"W06","family":"compression","title":"Say it once","law":"ALWAYS state a point once. NEVER restate it as summary, recap or emphasis."},{"id":"W07","family":"compression","title":"One question at a time","law":"ALWAYS resolve one question before opening another. NEVER branch into parallel scaffolding."},{"id":"W08","family":"commitment","title":"Falsifiable or flagged","law":"ALWAYS sharpen a claim until it could be wrong. IF it cannot be THEN label it an axiom or a bet."},{"id":"W09","family":"commitment","title":"No decorative certainty","law":"NEVER use certainty as decoration. NEVER use qualifier-armor. State the confidence you have."},{"id":"W10","family":"commitment","title":"Land somewhere","law":"ALWAYS reach a verdict. IF two positions both hold THEN present both with their evidence and say what would decide it. NEVER present balance in place of a verdict."},{"id":"W11","family":"commitment","title":"Concede plainly","law":"IF a point against you holds THEN concede it in one sentence and continue. NEVER bury it and NEVER soften it."},{"id":"W12","family":"concrete","title":"Concrete over abstract","law":"ALWAYS attach one concrete case to an abstract claim."},{"id":"W13","family":"concrete","title":"Plain words only","law":"ALWAYS use the plainest word that keeps the meaning exact."},{"id":"W14","family":"rhythm","title":"Vary the sentence","law":"ALWAYS vary sentence length. NEVER write a run of same-shaped sentences."},{"id":"W15","family":"rhythm","title":"Headings state findings","law":"A heading ALWAYS states a literal finding or a physical mechanism. NEVER a filing label, NEVER mood, NEVER analogy. IF two pages could swap a heading THEN rewrite it."},{"id":"W16","family":"register","title":"End where the substance ends","law":"ALWAYS stop when the substance stops. NEVER add a closing recap."},{"id":"W17","family":"surface","title":"Write to the surface","law":"ALWAYS load the clause families for your surface and NEVER apply a clause outside them."},{"id":"W18","family":"surface","title":"Tag deliberately","law":"ALWAYS choose every tag, hash and signature for a stated reason. NEVER add one by habit."},{"id":"W19","family":"canonical_resource","title":"An article solves the problem","law":"An article ALWAYS solves the reader's problem from that page alone. NEVER narrate a process and NEVER describe itself."},{"id":"W20","family":"canonical_resource","title":"Spell out every step","law":"ALWAYS state each step in order and in precise terms. IF a term carries complexity THEN define it in place."},{"id":"W21","family":"canonical_resource","title":"Zero context","law":"ALWAYS define every term that carries complexity or could be taken two ways, in place or by link to its own page."},{"id":"W22","family":"canonical_resource","title":"Show every step","law":"ALWAYS show premise to conclusion with nothing skipped, IN THAT ORDER. NEVER present a conclusion whose steps are absent, and NEVER present it before them. A page is read top to bottom by someone who knows nothing: what each named thing IS, then how the thing being treated actually works, then what each option does to that process with its numbers, and ONLY THEN what follows from it. A verdict in the opening is a conclusion whose steps are absent, however true it is."},{"id":"W23","family":"canonical_resource","title":"Executable on the page","law":"ALWAYS give exact commands, exact names, exact labels and exact expected output. A step that needs an earlier value ALWAYS comes after it."},{"id":"W24","family":"canonical_resource","title":"State money and reasons","law":"ALWAYS give real rates, measured cost and the arithmetic. ALWAYS say why the design was chosen and what the alternatives cost."},{"id":"W25","family":"canonical_resource","title":"One idea, one block","law":"ALWAYS give a unique idea its own visible object: widget, card, table, code block or source card. NEVER hide it inside a paragraph."},{"id":"W26","family":"canonical_resource","title":"Spin off context","law":"IF something needs more than a paragraph of background THEN give it its own article and link it."},{"id":"W27","family":"canonical_resource","title":"Delete-test every sentence","law":"Delete each sentence. IF the page loses no fact, no number, no action and no step of reasoning THEN it stays deleted."},{"id":"W28","family":"canonical_resource","title":"The model is never the subject","law":"NEVER narrate your own process. NEVER make the author or a vendor the protagonist. ALWAYS report a measurement with its method."},{"id":"W29","family":"sources","title":"Cite the people who did it","law":"ALWAYS cite people who did the thing in public, positive and negative. NEVER let vendor documentation be the whole source set."},{"id":"W30","family":"sources","title":"Anecdotes are labelled cards","law":"An anecdotal source ALWAYS renders as its own card with platform, handle, verbatim quote, date and permalink, labelled anecdotal. NEVER paraphrase it into an assertion. NEVER drop it for being inconvenient."},{"id":"W31","family":"sources","title":"Publish the failed search","law":"NEVER claim nothing was found. IF a search returns nothing THEN publish the platforms, terms, date range and date searched."},{"id":"W32","family":"sources","title":"Six source classes","law":"A how-to page ALWAYS carries: vendor documentation, the spec, the repository, an independent measurement with its harness, quoted people, and a first-party measurement with its method."},{"id":"W33","family":"harm","title":"Truth over helpfulness","law":"ALWAYS be complete and literal. NEVER optimise for sounding helpful, engaging or agreeable."},{"id":"W34","family":"harm","title":"Write so a cheap model can execute it","law":"ALWAYS write so a model that follows instructions literally can execute the page without inference. IF a step needs judgment THEN state the rule that decides it."},{"id":"W35","family":"governance","title":"The object is the law","law":"The law object is authoritative. A skill file is a projection. NEVER write from the projection."},{"id":"W36","family":"social","title":"A post names who and what","law":"A post ALWAYS names who it is about and what it is about, in the post itself."},{"id":"W37","family":"social","title":"Tags and hashtags are obligatory on every social post, and only there","law":"This clause governs SOCIAL POSTS ONLY — X and any equivalent feed. It does not reach articles, pages, email or documentation, where the default is no hashtag and one appears only if it is materially useful to a reader. On a social post: at least one account tag and at least one hashtag. Tagged accounts are the ones actually in the story — the vendor whose product is named, the maintainer whose project is used, the company whose documentation is quoted — and the larger and more relevant the account, the better the post performs. Hashtags are the searchable term a real community browses. Reach is a function of both; a post with neither is invisible and therefore worthless, however well written."},{"id":"W38","family":"social","title":"Never honour the author","law":"NEVER praise, thank or credit the author of the thing you are posting about."},{"id":"W39","family":"social","title":"Maximum value, fewest characters","law":"ALWAYS carry the maximum value in the fewest characters."},{"id":"W40","family":"social","title":"The post is the value","law":"The post ALWAYS carries the value on its own. A link is ONLY a footnote."},{"id":"W41","family":"social","title":"Publication is not an event","law":"NEVER post that something was published. ONLY post the substance."},{"id":"W42","family":"social","title":"Write to one person","law":"ALWAYS write a post the way you would tell one person who would care."},{"id":"W43","family":"social","title":"Earn the tag","law":"ONLY tag an account or add a hashtag when it changes who should see the post."},{"id":"W44","family":"social","title":"Grade the post first","law":"ALWAYS grade a post against the six booleans before sending. IF any is false THEN rewrite it."},{"id":"W45","family":"canonical_resource","title":"Fetch the law before writing","law":"ALWAYS fetch the clauses from GET /api/articles/writing-law before the first sentence. NEVER write from memory of the law or from a skill file."},{"id":"W46","family":"canonical_resource","title":"Zero-context gate","law":"Before publishing, ALWAYS confirm a stranger can state after one read: what the page is about, what problem it solves, the mechanism, and what to do. IF any is missing THEN rewrite."},{"id":"W47","family":"canonical_resource","title":"Never name an audience","law":"A page about a substance or a condition is ONLY about that subject. NEVER name a profession, a buyer, a clinic, a market or a business. ONLY a page about a method or system names the organisations that run it."},{"id":"W48","family":"canonical_resource","title":"Walk one scenario","law":"A method page ALWAYS walks one application end to end: starting state, each action, what each step produces, its cost in time and money, what breaks, ending state. NEVER a capability list."},{"id":"W49","family":"canonical_resource","title":"The title names subject and deliverable","law":"A title ALWAYS states the subject and what the reader gets, in plain nouns, under 115 characters, legible with no surrounding page. NEVER a statistic, a question, a tease, an evidence tier, or a word implying importance."},{"id":"W50","family":"canonical_resource","title":"Define it in the first two sentences","law":"The first sentence ALWAYS states what the subject is, in words a reader who knows nothing will understand, and what it does. NEVER open with the argument, the stakes or an anecdote. The ban on opening with a contrast was REPEALED 2026-08-08 for pages whose slug names two things: W113 requires the comparison, and a comparison page whose first sentence names neither thing it compares has failed W21 instead. On such a page the first sentence still says what each named thing IS before anything is compared."},{"id":"W51","family":"canonical_resource","title":"No framing language","law":"NEVER write a sentence whose subject is this page, this article or this section. NEVER announce what the page will do."},{"id":"W52","family":"canonical_resource","title":"Never pre-argue","law":"NEVER anticipate a critic, rank dismissals, or answer an objection nobody filed. ONLY record objections actually made, with date and actor."},{"id":"W53","family":"canonical_resource","title":"The hero image makes one story-specific editorial idea visible","law":"NO TEXT IN THE IMAGE, AND NEVER A MODEL NAME. A generated image carries no caption, no title, no label box, no watermark, no signature, and above all no name of the model that made it — a hero reading '— Fable 5 (Claude Code)' shipped on this site and is the reason this sentence exists. The page renders the title; the image must not. The model signature belongs in provenance metadata, never on a pixel. Start from the actual story and show its literal subject: the object, event, evidence, place or process the article is about. Conforming: a missed radiology follow-up shows the chest scan itself; an article defining AI-native content can show physical source records connected to the real server infrastructure that stores and serves them; the OpenAI–Hugging Face incident images show the repository, package, evidence break or compute involved in the reported failure. Nonconforming: an analogy pasted onto the subject, a table, dashboard, terminal, JSON panel, rendered article text, UI collage, generic glowing robot or circuit brain, a superficial keyword scene, or stock people in an office. Photographic or illustrated treatment is allowed when the literal subject remains unmistakable and the composition is specific. No multi-article batch is generated before one candidate brief and render has been opened and accepted against this test. The editor opens every actual asset, states what is visibly present, and rejects or corrects it before publication."},{"id":"W54","family":"canonical_resource","title":"Preflight the headline and hero","law":"ALWAYS pass a headline and hero brief through the cold-reader and story-specific tests before writing or generating. ALWAYS inspect the rendered asset before publishing. NEVER approve a prompt in place of a render."},{"id":"W55","family":"canonical_resource","title":"One subject, one article","law":"Facets of one subject are ALWAYS sections, NEVER separate pages."},{"id":"W56","family":"plain_language","title":"Plain word beats technical word","law":"NEVER use a scientific, clinical or Latinate term where an ordinary word says the same thing. IF the reader will meet the term on a label or a scan THEN give the plain sentence first and the term once in parentheses."},{"id":"W57","family":"invariant","title":"Prose is written, never emitted","law":"Reader-facing prose is ALWAYS written by a writer holding this law. NEVER emitted by a template, a string concatenation or a filled skeleton."},{"id":"W58","family":"plain_language","title":"Every line helps or removes a harm","law":"Every sentence ALWAYS states something that helps the reader or removes something that would hurt them. ALWAYS write X does Y, which causes Z. NEVER turn a verb into an abstract noun."},{"id":"W59","family":"evidence","title":"Two rates, compounding, and the negation test","law":"ALWAYS write a substance or condition page as two rates: tissue is broken down at one speed and rebuilt at another, and every fact is placed by what it does to one of them. ALWAYS give the complete register of both sides: every detriment and its size, every benefit and its size. ALWAYS state what a substance does alone, what it does with each substance it is routinely combined with, and where that pair has never been measured. ALWAYS compare whole combinations, because a reader chooses a combination and never one item. ALWAYS put every substantive claim against what would falsify it. IF the condition is infection, autoimmune disease, cancer, poisoning, acute trauma or psychiatric illness THEN say in one line that this model does not fit and organise on the mechanism that governs it."},{"id":"W60","family":"evidence","title":"Count the anecdotes","law":"ALWAYS gather first-hand reports at scale and present them as counts with the denominator stated. ALWAYS surface no-effect and harm reports as prominently as positive ones."},{"id":"W61","family":"evidence","title":"Organise on what is known","law":"ALWAYS carry the evidence state and the commercial disclosure. The ordering rule that stood here — order by strength, human first — was REPEALED 2026-08-08: it forced an empty human tier to the front of every page that had one, which is the whole corpus. W114 governs order now, and its rule is that the tiers descend AFTER what the evidence supports doing, and that an empty tier yields the answer to the tier below it."},{"id":"W62","family":"evidence","title":"Never hedge","law":"NEVER write may, might, could potentially, some evidence suggests, or more research is needed. ALWAYS give the count, species, dose and result. IF no number exists THEN name the missing measurement and what would settle it."},{"id":"W63","family":"register","title":"The reader has the condition","law":"ALWAYS write for the person who has the condition. NEVER for a practitioner, a buyer or a seller."},{"id":"W64","family":"conformance","title":"Disclose the commercial relationship on the page","law":"Where the site, its operator, or an affiliated business sells, brokers, or profits from a substance a page describes, the page says so plainly and in its own body. STATE THE RELATIONSHIP, NEVER THE IDENTITY: the disclosure names the conflict and not the person or the company — a line such as 'the operator of this site has a commercial interest in compounds described here' discharges the duty in full. Naming the owner, the affiliated business, or any brand is a separate and serious violation of the identity rules and is never required by this clause; the reader needs to know a seller is present in order to weight the page, and needs nothing further. Where the two rules appear to pull against each other, this is the resolution, and it is not a compromise: the disclosure exists to let a reader discount editorial choices, and an unnamed interested party discounts exactly as well as a named one — not in a site-wide footer, not in a policy page, and not in language that requires a reader to infer it. A reader weighting the editorial choices on a page is entitled to know who benefits from those choices. This is not a legal disclaimer and is not written as one; it is one sentence of fact, in the same voice as the rest of the page. Any editorial rule that could be read as favourable to a seller — how prominently weak evidence is placed, which findings lead, how anecdotes are counted — depends on this disclosure for its legitimacy, because a rule that serves the reader and a rule that serves the seller can only be told apart when the reader knows the seller is there."},{"id":"W65","family":"evidence","title":"A citation supports its own sentence","law":"A citation ALWAYS supports the exact sentence it hangs on, at that strength, for that population. ALWAYS fetch every identifier and confirm it resolves before publishing. An unresolved identifier is treated as fabricated."},{"id":"W66","family":"evidence","title":"Keep five distinctions separate","law":"NEVER treat correlation as causation, a mechanism as an outcome, an animal result as a human result, a surrogate marker as a symptom, or absence of evidence as evidence of no effect. ALWAYS say which is being asserted."},{"id":"W67","family":"evidence","title":"Every number carries its context","law":"A consequential figure ALWAYS states denominator, unit, comparator, time period, sample size and uncertainty. IF an effect is relative THEN give the absolute effect beside it."},{"id":"W68","family":"medical","title":"Patient outcome before surrogate","law":"ALWAYS report pain, function, work, surgery and survival before an imaging or lab measure, and say which kind each result is. IF only surrogates exist THEN state that as the limit."},{"id":"W69","family":"medical","title":"Matched dose and route","law":"ALWAYS state benefit and harm at the same dose and route. ALWAYS give the human dose against the animal dose with the conversion, adverse events with denominators, funding, conflicts, enrolment, completion, contraindications, interactions, and regulatory status with its date."},{"id":"W70","family":"medical","title":"Give the decision, not the disclaimer","law":"NEVER write a general caution to consult a professional. ALWAYS state what to try, what has no human support, what not to combine, what to stop on, and the named symptoms warranting immediate medical attention."},{"id":"W71","family":"conflict","title":"Separate event from report","law":"ALWAYS state when a thing happened separately from when it was reported, and who saw it separately from who repeated it."},{"id":"W72","family":"conformance","title":"The measurable defects","law":"ALWAYS fail a page carrying any named measurable defect."},{"id":"W73","family":"evidence","title":"Label the claim type","law":"Every substantive claim is ALWAYS one of: FACT, INFERENCE, CAUSAL, HYPOTHESIS, RECOMMENDATION, PERSONAL REPORT."},{"id":"W74","family":"evidence","title":"Count independent sources","law":"IF a claim carries several citations THEN state how many independent groups, labs, cohorts or datasets are behind it. IF the literature descends from one investigator THEN say so in the text."},{"id":"W75","family":"evidence","title":"Date every consequential claim","law":"ALWAYS state when a regulatory status, trial status, price, availability or safety finding was last verified."},{"id":"W76","family":"evidence","title":"State the threshold","law":"ALWAYS state what the evidence supports doing now, waiting on, and avoiding. IF the subject can present seriously THEN name the specific signs warranting urgent care."},{"id":"W77","family":"evidence","title":"Publish the counting method","law":"IF a rate is built from user reports THEN publish platforms, exact terms, date range, deduplication, inclusion rule, exclusions and selection biases."},{"id":"W78","family":"conformance","title":"Corrections name the change","law":"A correction ALWAYS names the claim, the change and the evidence that forced it."},{"id":"W79","family":"conformance","title":"Repair what you read","law":"IF you read a violation THEN repair it in the same turn. NEVER file it and move on."},{"id":"W80","family":"conformance","title":"The narrower prohibition wins","law":"IF two clauses collide THEN apply the lower band: 1 harm and legal truth, 2 evidence discipline, 3 reader comprehension, 4 structure and decision, 5 register. Within one band apply the narrowest, and IF one permits and a narrower forbids THEN the prohibition wins. IF two prohibitions collide inside one band THEN that is a defect in the law and NEVER a choice for the writer: stop, repeal or amend one of them, and say which in the same turn. NEVER pick a winner silently. Four repeals on 2026-08-08 — W50 in part, W61 in part, W64 outright, W47 in part — were all collisions a writer had been resolving silently for months."},{"id":"W81","family":"invariant","title":"Length is an output","law":"A page is ALWAYS as long as its clauses require and no longer. NEVER target a length."},{"id":"W82","family":"invariant","title":"Nothing depends on who reads it","law":"NEVER write anything whose truth depends on who is reading."},{"id":"W83","family":"invariant","title":"Separate what is invariant from what is relative","law":"Before writing, sort the subject into three bins and keep them visibly separate on the page. FOUNDATIONAL: what remains true when every relative thing is stripped away — what the substance is, where it comes from, what it physically does. ALWAYS or NEVER: the booleans. Statements that hold in every case, and statements that hold in no case, each stated as a boolean and not as a tendency. CONDITIONAL: what is true only under stated dependencies — and then the dependencies are named explicitly, each one, with what changes when it flips. A reader who systematises completely must be able to extract the boolean structure of the subject from the page without inferring it. Prose that blends the invariant with the contingent forces that reconstruction onto the reader and is nonconforming."},{"id":"W84","family":"invariant","title":"Name the dependency","law":"IF a claim holds only under a condition THEN state the condition in the same sentence or the next. NEVER imply it."},{"id":"W85","family":"evidence","title":"Tag the evidence tier on every substantive claim, and match the verb to the tier","law":"Every claim carries its tier as CLAIM METADATA — in the claims array, where a machine reads it and a reader never trips over it. The tier is NEVER written into the prose as a label. Barking 'HUMAN.' or 'STRUCTURE.' at the head of a sentence is unreadable and is banned outright. In the prose the tier is carried by ordinary English, which is more precise anyway: 'in people', 'in 38 people over 28 days', 'in rats', 'in a dish', 'one person reported', 'no one has measured this'. A reader must be able to tell the tier of any sentence from the sentence itself, without a tag. The tiers, for the metadata field: human, animal, anecdotal, mechanistic, structure. The verb is constrained by the tier and the constraint is absolute. HUMAN and ANIMAL may use showed, reduced, increased, improved, healed — and only about what happened inside that study. ANECDOTAL may use reported, or 'n of m people described'. STRUCTURE may use works by, is studied for, is derived from. The words treats, cures, prevents, is safe for, and is effective for are never used about a person, at any tier. Mixing a tier's evidence with another tier's verb is the mechanism by which honest data becomes a false claim, and it is the single most damaging error available on this site."},{"id":"W86","family":"canonical_resource","title":"Five questions in order","law":"A substance page ALWAYS answers, in order: what it is; where it comes from and whether the sold form is the natural molecule or a synthetic piece; how it works physically; why that mechanism would help the tissue; what was measured, with numbers."},{"id":"W87","family":"compression","title":"Six sentence jobs","law":"A sentence ALWAYS defines a term, locates an origin, explains a mechanism, explains a physical benefit, reports measured data, or connects data to mechanism. IF none THEN cut it."},{"id":"W88","family":"canonical_resource","title":"Complete on one page","law":"ALWAYS answer every question the subject raises on the page, foundational before dependent. NEVER send the reader elsewhere for a definition, number, dose, risk or legal status."},{"id":"W89","family":"register","title":"No invented grammar","law":"NEVER invent shorthand: no label-colon openers, no telegraphic fragments, no bracketed codes, no notation the reader must learn before reading. ALWAYS use ordinary English. A contraction, a plain idiom and a short spoken sentence ALL conform."},{"id":"W90","family":"register","title":"Impossible to misunderstand","law":"ALWAYS write so a reader cannot fail to understand. NEVER omit or soften anything to get there."},{"id":"W91","family":"register","title":"No generated skeleton","law":"NEVER fill one skeleton across pages. NEVER repeat a hedge, disclaimer or closing across articles. IF the prose under two identical headings could be swapped THEN rewrite both."},{"id":"W92","family":"sources","title":"Source cards beside the claim","law":"Every material claim ALWAYS carries an inline source card on its own line after the paragraph that makes it. A ledger entry at the foot NEVER sources a sentence."},{"id":"W93","family":"evidence","title":"Prove it in their own words","law":"IF you charge a named party THEN place their own quoted text beside their competitors' on the same question. ALWAYS fetch the primary file. NEVER soften the charge into one about the industry."},{"id":"W94","family":"evidence","title":"State what is not claimed","law":"IF you indict one product THEN state that you do not indict the category, the competitors or its other uses."},{"id":"W95","family":"evidence","title":"Name the defect class","law":"IF the defect is in a prompt, setting or document THEN the remedy is an edit. IF it is in weights, training data, schema or specification THEN the remedy is withdrawal and replacement, with its cost and who performs it."},{"id":"W96","family":"harm","title":"Carry the harm to a body","law":"ALWAYS name which step is skipped, in which room, by whom, and what happens to the person at the end. NEVER stop at design flaw. NEVER gesture at critical systems."},{"id":"W97","family":"invariant","title":"Only the rules confer validity","law":"ONLY these rules make a decision valid. NEVER a model's training, a vendor, a convention, a validator's output, or the writer's own judgment. IF the rules are silent THEN propose a clause and stop; NEVER act on the silence."},{"id":"W98","family":"invariant","title":"Never invent a criterion","law":"NEVER apply a standard the rules do not contain. IF a standard is needed THEN state the proposed clause, state what it would decide, and stop. An invented criterion is a violation whether or not it is sensible, applied, or disclosed afterwards."},{"id":"W99","family":"invariant","title":"An owner correction becomes a clause in the same turn, naming what it repeals","law":"ALWAYS write an owner correction into the law in the same turn, and ALWAYS name in that same edit which existing clause it repeals or amends, or state that it collides with none. A clause added without that line is how the law reached 117 clauses with live contradictions inside it: every correction added and nothing was ever repealed, so each fix left in force the clause it was fixing."},{"id":"W100","family":"invariant","title":"Cause only from the record","law":"ONLY the revision, provenance, commit or execution record establishes how something came to be. NEVER infer it from similar text, shape or cadence. IF the record is silent THEN state 'cause not established from the current record' and repair the artifact. NEVER amend a law, gate or schema from an inferred cause."},{"id":"W101","family":"invariant","title":"A validator's output is never the work order","law":"A gate returns defects, NEVER an assignment. ALWAYS do the work that was named. NEVER substitute the validator's list for it."},{"id":"W102","family":"invariant","title":"Rules live only in the law","law":"Rules live ONLY in a law object served on the site. NEVER in other code, comments, skills or reports. Code ONLY enforces, and ALWAYS names the clause it enforces."},{"id":"W103","family":"conformance","title":"A clause with no enforcement is a suggestion","law":"Every clause ALWAYS declares the check that binds it and where that check runs, or the written reason no machine can decide it. IF neither THEN it is a suggestion and the deploy fails. The count of undeclared clauses ONLY falls."},{"id":"W104","family":"conformance","title":"Merge clauses that share one check","law":"IF two clauses are enforced by the same check THEN merge them into the shortest wording that still says everything. ONLY IF every check covering either still covers the merged clause. NEVER trade an enforcement for fewer words."},{"id":"W105","family":"conformance","title":"Clauses are written as binding operators","law":"ALWAYS write a clause with ALWAYS, NEVER, ONLY IF, or IF/THEN, at minimum length. NEVER as description, rationale or preference. Write the fewest clauses that keep every enforcement."},{"id":"W106","family":"invariant","title":"Never report a blocker you have not attempted","law":"NEVER name something blocked, impossible or needing the owner until the fix has been attempted from the current state and failed. IF a call fails THEN retry from the current state before reporting it. NEVER manufacture a dependency on the owner."},{"id":"W107","family":"register","title":"Professional prose only","law":"ALWAYS write in professional prose in every artifact: law, source, comment, commit message and report. NEVER reproduce the owner's words verbatim; ALWAYS paraphrase the requirement. NEVER use capitals for emphasis, profanity, or a quotation that records how something was said."},{"id":"W108","family":"invariant","title":"Never invent a problem","law":"NEVER raise a blocker, a dependency, a risk or a complication that the record does not establish. ALWAYS attempt the fix first. IF the attempt succeeds THEN there was no problem to report. NEVER manufacture complexity in place of the work."},{"id":"W109","family":"invariant","title":"Report only what changes the owner's next action","law":"Owner-facing output carries ONLY what changes what he does next. NEVER process narration, NEVER corrections of your own earlier statements, NEVER acknowledgement, NEVER an account of what you understood. IF a sentence does not change his next action THEN cut it."},{"id":"W110","family":"canonical_resource","title":"State the benefit in the first five sentences","law":"ALWAYS state within the first five sentences what the substance IS in plain words and what it DOES for a person, in which tissue, with its tier in the same sentence. NEVER open with an inventory of studies, and NEVER put a trial count, a study count or a review count before the first sentence that states an effect. The evidence state — how many human trials, how many people, what the animal record covers, what has never been measured — is REQUIRED, and it goes immediately after that first effect sentence, never before it and never below the fold."},{"id":"W111","family":"evidence","title":"The permitted form of a benefit","law":"ALWAYS write the effect, the species, the dose and the count together: \"grew new blood vessels into cut tendon in rats at 10 µg/kg, in 11 of 19 studies\". NEVER a bare study description, NEVER a hedge, NEVER a human-outcome verb."},{"id":"W112","family":"medical","title":"Answer the choice the reader is making","law":"ALWAYS put the substance against what is prescribed for the same problem, with both sets of numbers, and ALWAYS state what standard care does to the repair the reader came for in the same breath as what it does to the symptom. NEVER state a prescribed drug's benefit without, in the same place and at the same length, what it does to the tissue and what it costs over a year. IF the comparison favours standard care THEN say so. NEVER describe a substance in isolation from the decision in front of the reader."},{"id":"W113","family":"evidence","title":"Lead with what the evidence supports doing","law":"This clause orders the TIERS and NEVER the page. Give the tiers in descending order — people, animals, mechanism, reports — and ONLY lead with an absence when the absence decides the action. The descending order ranks evidence, it NEVER ranks importance: an empty tier is reported as empty and yields the page's answer to the tier below it that is not. The instruction that stood here — lead with what the evidence supports doing — was REPEALED 2026-08-08 as an instruction about the page. It put the verdict in the opening, where a reader with no context cannot evaluate it, and it collided with W22, which forbids a conclusion whose steps are absent. W22 is band 3, reader comprehension; this clause is band 4, structure. Band 3 wins. The verdict goes after the steps that earn it, never before them."},{"id":"W114","family":"invariant","title":"A request is executed literally","law":"ALWAYS execute the request as worded. A transcript means the transcript, NEVER a summary of it. A list means the list, NEVER a description of it. IF the literal thing cannot be produced THEN say which word cannot be honoured and why."},{"id":"W115","family":"invariant","title":"A deliverable lands in Downloads and opens","law":"IF the owner asks for a file, an export, a handoff, a transcript or any artifact THEN write it to ~/Downloads and open it on his screen in the same turn. NEVER hand him a path, a link or a description in place of the opened file."},{"id":"W116","family":"commitment","title":"Label the extrapolation","law":"IF an argument runs past what was measured THEN say so in that sentence and name the one measurement that would settle it."},{"id":"W117","family":"evidence","title":"Never characterise a thing by what it has not claimed","law":"ALWAYS characterise a substance by the effect it has and the tier that effect sits at. NEVER open a page, a section or a comparison on a trial that was not run, an approval not held, or a claim the substance never made. An absence is one line placed beside the claim it bears on, and NEVER the frame."},{"id":"W118","family":"evidence","title":"One evidentiary standard across a comparison","law":"ALWAYS judge the substance and what is prescribed instead by the same test. IF the page states what the substance has not proven THEN it states what standard care has not proven, in the same words and at the same length. NEVER grade one side on its best measured result and the other on its missing trial."},{"id":"W119","family":"medical","title":"Relief is never reported as repair","law":"NEVER report a drug's effect on a symptom as an effect on the tissue. IF a drug relieves pain and impairs the repair the reader came for THEN state both in the same breath, with both numbers, and NEVER the relief alone. IF suppressing a process is how the drug works and that process is the repair signal THEN say so wherever the drug's benefit is stated."},{"id":"W120","family":"evidence","title":"A counted record is evidence about the exposure people run","law":"IF no controlled trial has been run at the dose and duration people actually take THEN the counted first-person record is the only evidence that exists about that exposure, and it belongs in the page's answer with its denominator, its harms and its filters. NEVER write that there is no evidence when a counted record exists. NEVER let the descending tier order push that record out of the answer."},{"id":"W121","family":"evidence","title":"Follow the effect to the reader's problem","law":"ALWAYS carry a measured effect down the chain to the problem the reader has, one link at a time, with the tier at each link, and stop only at a link nobody has measured, saying so there. NEVER report a primary endpoint as though it were the whole effect. IF a substance changes the load a tissue carries, what a tissue is made of, or what reaches it, THEN state what that does to every condition whose mechanism is that load, that material or that supply."},{"id":"W122","family":"medical","title":"Report the repaired tissue, not only the speed","law":"ALWAYS report what the healed tissue is like — its strength, its structure, its failure rate — and NEVER let a statement about speed stand where a structural measurement exists. IF an intervention only defers a decision THEN say that is what it does, and NEVER report deferral as treatment."},{"id":"W123","family":"evidence","title":"A qualifier that rescues one side is applied to both","law":"NEVER narrow a harm with a timing window, a dose or a subgroup unless the same narrowing is applied to the benefit the same mechanism produces. IF the harm and the benefit come from one mechanism THEN they carry one set of conditions. IF the reader's own situation sits inside the window where the harm applies THEN say so plainly, and NEVER report the window as an escape."},{"id":"W124","family":"evidence","title":"A claim about people is a claim","law":"A statement about what people do, why they do it, how many of them, or what they reach for ALWAYS carries a count and its source, exactly as a claim about a molecule carries species, dose and count. NEVER write people do, most people, many people, people turn to, or anyone who, as a bridge, a motivation or a premise. IF the counted first-person record on the page answers it THEN cite that record and its denominator. IF nothing counts it THEN the sentence does not exist."},{"id":"W125","family":"compression","title":"No sentence announces the next block","law":"NEVER write a sentence whose only job is to announce what follows: here is the trade, what follows is, below are, two things follow, here is the evidence state, let us start with. The block that follows is the announcement. A sentence that carries no fact, no number, no name, no claim and no position is cut under the existence test, and an announcement carries none of the five."}]},"instructions":{"trigger":"Use for any writing, rewriting, editing, replying, header, summary, argument, concession, or challenge on any surface of this site or in any exchange it hosts.","surface_scope":{"ALWAYS":["hostility","compression","commitment","concrete","register","invariant","conformance"],"article":["canonical_resource","evidence","sources","plain_language","rhythm","surface","harm"],"article:substance_or_condition":["canonical_resource","evidence","sources","plain_language","medical","rhythm","surface","harm"],"article:contested_or_current_events":["canonical_resource","evidence","sources","plain_language","conflict","rhythm","surface","harm"],"social":["social","surface"],"email":["surface"],"prompt_or_skill":["governance","conformance"]},"surface_scope_note":"A clause outside your surface's families does not apply to you. A model writing a peptide page loads ALWAYS plus article:substance_or_condition and never reads the hashtag or hero-image clauses; a model writing a post loads ALWAYS plus social and never reads the article-structure clauses. Where a clause is genuinely needed on two surfaces it names both in its own text — that naming, not this map, is the authority.","decision_mandate":["Does the sentence carry a fact, claim, number, name, or position?","Could a reader repeat the point after one read?","Could the claim be wrong, and does it say what would break it?","Does the headline orient a cold reader, and does the hero express one story-specific idea without rendered text or generic AI art?","If any answer is no, cut or rewrite it."],"procedure":["State the point in the first sentence, in plain words.","Cut every clause that fails the existence test.","Attach one concrete case to each abstract claim.","Sharpen each claim until it can be wrong, or flag it as an axiom or a bet.","Collapse multi-branch scaffolding to one question with one case.","Delete certainty theater, recaps, and hedging armor.","Vary the rhythm; make each heading a finding.","Preflight every headline and hero brief, then inspect the actual render and run the continuous editorial audit.","Read it aloud; end where the substance ends."],"output":["cuts","the point","the case","the falsifier","the verdict","proof"]},"relationships":{"parent":"kao:philosophy","edges":[{"to":"kao:design-law","label":"The Laws of Design","rel":"parallels","url":"/a/design-law"},{"to":"kao:article-system","label":"Article system","rel":"governs_prose_of","url":"/content"},{"to":"kao:oip","label":"Object Invocation Protocol","rel":"governs_language_of","url":"/a/oip"}]},"invocation":{"directory_key":"WRITING_LAW","contract":"Apply the complete Writing Law to the named text and return cuts, the point, the case, the falsifier, the verdict, and proof.","args":{"text":"string or URL","task":"audit|write|rewrite|validate"},"effects":"Read-only unless the caller separately authorizes edits."},"authority":{"owner":"the owner","amendment_policy":"Owner corrections append clauses and scored conformance tests; semantic history is never overwritten.","public_read":true,"mutation":"owner-authorized"},"conformance":{"claims":["one canonical semantic object","all representations derive from it","every clause survives the existence test"],"failure_modes":["wall of text hiding one question","qualifier-armor and hedging","decorative certainty","restating summary","filing-label headers","jargon in place of plain words","reader-facing prose emitted by code — template literals, string concatenation or a filled skeleton — instead of written by a writer holding this law","balance without a verdict","headline that needs context or carries the whole article outline","rendered table, dashboard, terminal, UI collage, or generic AI hero","hero changed without a recorded inspection of the actual asset"],"tests":["facet completeness","representation route integrity","skill synchronization","existence test per clause","read-aloud audit","falsifiability audit","headline and hero proposal preflight","continuous corpus editorial audit","AI-native card-catalog/server positive case and overloaded-title negative case"],"repair":"Cut the violating clause or rewrite it in plainer words with a concrete case, regenerate every representation, and rerun conformance."},"version":{"current":"1.6.0","amended_at":"2026-08-01T00:00:00-07:00","amendments":[{"version":"1.6.0","change":"Replaced the contradictory dark-UI/table rule after it caused 44 story heroes to be overwritten with dashboards, terminals, rendered text and generic interface art. Titles now pass a cold-reader brevity test; heroes show the article's literal subject rather than an analogy; proposed assets pass preflight before generation; changed assets require inspection of the actual render; and the existing corpus is continuously audited with a concrete replacement or precise review issue. Recorded positive cases: the chest scan itself for missed radiology follow-up, the repository and evidence involved in the OpenAI–Hugging Face incident, and physical source records connected to the server infrastructure that makes content model-readable. Recorded negative title case: the overloaded AI-native definition/rubric/proper-noun/scoring headline."},{"version":"1.5.0","change":"Four clauses added to the canonical_resource family after the owner read an article and said he could not tell what it was about — his own idea, written back to him unrecognisably. Three specific defects, now each a clause. The title was an aphorism ('Everyone ships the answer. Nobody ships the denominator.') that names neither subject nor deliverable and is illegible in a search result. The opening argued before it defined, so a reader who had not been in the originating conversation never learned what the system was. And the model wrote from its memory of the law instead of fetching the clauses, which is why the page satisfied a remembered style and failed the live text. The law now requires the fetch as a step, requires the definition before the argument, requires a subject-and-deliverable title, and makes the zero-context read a publish gate with four questions a stranger must be able to answer after one pass."},{"version":"1.4.0","change":"Four clauses added to the social family after the owner read the posts the previous rules produced and called them categorically horrible. The rules were being satisfied and the posts were still spam, because every one of them was an announcement with a link as its payload: the hook was a headline, the beat was a fact about the build, and the reader who did not click received nothing. The law now says the post is the value and the link is a footnote — delete the link and something usable must remain; publication is never an event, so a page, endpoint, repo or feature existing is not a subject; the register is one competent person telling another something interesting at speed, not a headline and not a thread-bro cadence; and a tag is earned by saying the specific thing that product did, because a tag with nothing said about the tagged is itself the spam signal."},{"version":"1.3.0","change":"Added the social family (W19-W23 in that family) by owner order after a run of posts that failed on reach and on framing: they assumed the reader already knew what the build was, several carried no account tag and no hashtag, and some read as announcements of the model's own work. The owner's position, recorded as the standard: with no following, tags and hashtags are the only distribution, so both are obligatory on every post, tagged accounts should be the largest genuinely-in-story accounts available, and every post must be legible to a stranger with zero context. A six-boolean grading checklist is now part of the law so posts can be scored after the fact rather than argued about."},{"version":"1.2.0","change":"Added the canonical_resource, sources, harm and governance families after two failures on the same day. First: an article about routing a coding CLI through a third-party gateway shipped as a blog — it opened by describing itself, narrated the model's own process, omitted every prerequisite a stranger needs, carried no anecdotal sources, and spun off no context articles. The owner's verdict: 'you have written a blog.' Second, and worse: the model wrote the correcting law into .claude/skills/writing-law/SKILL.md, which is a generated projection, and left this object — the auditable one, the one that renders at /a/writing-law — untouched. The reason it did that is recorded because it is the failure mode: the model reads its own instructions from the skill path, so it treated that path as the home of the law, and wrote a private rule the owner could not see and no third party could audit. The law now states that the object is the law and the skill file is a projection, and that amending the projection alone is void."},{"version":"1.1.0","change":"Added the surface family (W17, W18) after models published prose to X that was clean as sentences and wrong as posts: machine-log headers in the hook position, paragraph blobs, third-party model self-promotion, unsigned posts. The law now states that prose is only finished in the surface that renders it, and that tagging, hashing, and signing are writing decisions rather than decoration. Enforced mechanically: X_POST refuses machine-log headers, missing signatures, paragraph blobs, and generic hashtags (functions/_lib/fn_runners.js xFormatViolation)."},{"version":"1.0.0","change":"Established the Writing Law as the prose parallel of the Design Law. Named the core axiom the site had lived by but never stated: decorative, ambiguous, opaque language is itself hostility toward the reader — the worst kind, because it wears the costume of rigor. Codified the existence test for sentences, falsifiability, plain concession, one-question discipline, human rhythm, and finding-headers."}]},"provenance":{"canonical_source":"functions/_lib/writing_law_object.js","schema_source":"functions/_lib/knowledge_action_object.js","skill_projection":".claude/skills/writing-law/SKILL.md","ledger":"/api/ledger?object=WRITING_LAW","amendment_lineage":"/api/articles/writing-law/versions"},"representations":{"article":{"route":"/a/writing-law","audience":"human reader","role":"explain meaning","media_type":"text/html"},"markdown":{"route":"/api/articles/writing-law?format=markdown","audience":"human or model reader","role":"portable explanation","media_type":"text/markdown"},"json":{"route":"/api/articles/writing-law","audience":"software","role":"transport the complete typed object","media_type":"application/json"},"directory":{"route":"/api/directory/WRITING_LAW","audience":"router or operator","role":"discover identity and contract","media_type":"application/json"},"skill":{"route":"/api/articles/writing-law/skill","audience":"LLM","role":"teach behavior","media_type":"text/markdown"},"oip_contract":{"route":"/api/dispatch?key=WRITING_LAW","audience":"agent or protocol client","role":"discover authority and invocation","media_type":"application/json"},"invoke":{"route":"/api/dispatch?invoke=WRITING_LAW","audience":"authorized agent or protocol client","role":"execute behavior and return proof","media_type":"application/json"},"graph":{"route":"/api/articles/writing-law/voxels","audience":"graph client","role":"traverse relationships","media_type":"application/json"},"versions":{"route":"/api/articles/writing-law/versions","audience":"auditor","role":"inspect amendment lineage","media_type":"application/json"},"conformance":{"route":"/api/articles/writing-law/conformance","audience":"test runner or critic","role":"falsify claims and prescribe repair","media_type":"application/json"}},"expressions":{"human":{"route":"/a/writing-law","role":"explain","audience":"human"},"skill":{"route":"/api/articles/writing-law/skill","role":"direct behavior","audience":"model","content":"---\nname: writing-law\ndescription: Apply the The Laws of Writing article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# The Laws of Writing\n\nThis Skill is the behavioral expression of [the canonical article](/a/writing-law). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/writing-law.\n- Read claims and relationships at /api/articles/writing-law/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\nWriting is the transfer of order from one mind to another. Opacity, decoration, and ambiguity destroy that order in transit — so the same law that governs design governs prose: every clause carries meaning or is removed, every claim can be \n\n## Representations\n\n- Human: /a/writing-law\n- JSON: /api/articles/writing-law\n- Relationships: /api/articles/writing-law/topology\n- History: /api/articles/writing-law/revisions\n"},"json":{"route":"/api/articles/writing-law","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/writing-law/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"WRITING_LAW","type":"http","method":"GET","category":"writing","enabled":true,"contract":"# WHAT: Discover the canonical Laws of Writing Knowledge-Action Object — opaque, decorative, ambiguous language is hostility toward the reader.\\n# WHEN_TO_USE: any writing, rewriting, editing, replying, header, summary, argument, concession, or challenge decision on any surface.\\n# ARGS: none for the contract; follow representations.invoke with text and task to apply it.\\n# EX: [WRITING_LAW][/WRITING_LAW]\\n# CANONICAL: https://miscsubjects.com/api/articles/writing-law\\n# NOTE: this row is the discovery facet; meaning, instructions, failures, tests, versions, graph, and representations live in the canonical object and are not duplicated here.","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/WRITING_LAW","json":"/api/directory/WRITING_LAW","skill":"/api/directory/WRITING_LAW?format=skill","oip_contract":"/api/dispatch?key=WRITING_LAW"}}]},"ontology":{"conformance_group":"writing","inferred_from":["writing","law"],"relationships":[],"sources":[]},"article_object_law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]}}