{
  "schema": "org-writing@v1",
  "slug": "theme-the-atmosphere-never-the-contract",
  "kg": {
    "id": "org:writing:theme-the-atmosphere-never-the-contract",
    "type": "brick",
    "graph": "/kg.json"
  },
  "title": "Theme the atmosphere, never the contract",
  "subtitle": "Customization stops at the ethical layer, because a person learns safety once and then has to recognize it somewhere else",
  "abstract": "What a tenant may restyle and what stays platform infrastructure, and why the grammar of safety has to travel with the person instead of with the brand.",
  "kind": "brick",
  "topics": [
    "Incentives"
  ],
  "courseMemberships": [
    {
      "course": "org:courses:incentives",
      "topic": "Incentives",
      "wall": "org:walls:engineering",
      "position": 3,
      "total": 6
    }
  ],
  "publishedAt": "2026-08-03T00:00:00.000Z",
  "version": 1,
  "guidelinesVersion": 15,
  "brief": {
    "problem": {
      "text": "White-label platforms sell the depth of their customization, and the deeper it runs the more of the safety surface becomes a vendor's aesthetic choice.",
      "claims": [
        "standardized radiotelephony phraseology after the 1977 Tenerife runway collision"
      ]
    },
    "mechanism": {
      "text": "Safety is recognized rather than read, and recognition is a property of repetition across contexts, so a safety grammar that varies by vendor has to be relearned at precisely the moment nobody has capacity to learn.",
      "claims": [
        "the safety ladder is platform infrastructure rather than themable surface"
      ]
    },
    "move": {
      "text": "Draw the customization boundary at the contract rather than at the budget, let tenants own vocabulary and atmosphere in full, and validate renamed terms against the safety and consent language they may not touch.",
      "claims": []
    }
  },
  "sources": [
    {
      "repo": "mnstry-monorepo",
      "path": "docs/10-platform/20-features/ux-design-bible.md"
    }
  ],
  "canonicalPath": "/writing/theme-the-atmosphere-never-the-contract/",
  "body": "On 27 March 1977 two Boeing 747s collided on the runway at Tenerife and 583 people died, in an accident whose investigation turned substantially on language. One crew used a phrase about being at takeoff that the tower heard as a position report and the crew meant as an action. Nothing was hidden and nobody was careless. Two competent professionals used ordinary English and each understood the other perfectly, in opposite directions. The industry's response was to take the words away from the airlines. Standardized radiotelephony phraseology, fixed by international convention and taught identically everywhere, means that the word mayday carries one meaning in every accent on earth and that the clearance to take off can be issued in exactly one form. Airlines still own their liveries, their cabin service, and their entire brand. They do not own the sentence that stops a plane.\n\nThat boundary is the one worth copying, and it is not where a platform business naturally draws it. White-label depth is a sales asset, priced and demoed, and the customer asking for it is the customer with the largest deal size, so the pressure runs monotonically toward letting a tenant restyle more. Our design bible sets the line at a different place, and it sets it in the philosophy section rather than in a settings page. Practitioners theme templates and instances, which is to say vocabulary, metaphors, phase names, color temperature, illustration tone, ceremony copy, and the naming of every space in the product. They do not theme the primitives, the consent grammar, the safety semantics, the privacy-state labeling, or the time model. Roughly forty client-facing terms are renameable, each with a character limit and a revert, and the system validates that a renamed term does not collide with the safety or consent language it is forbidden to touch.\n\nThe reason is that safety is recognized rather than read, and recognition is a property of repetition across contexts, which means a safety grammar that varies by vendor has to be relearned at precisely the moment nobody has capacity to learn. A person who has once been through the gentlest rung of the ladder, the narrowing that happens when a conversation is going somewhere it needs to go slowly, has learned something in their body about what that feels like. If the next expert they work with runs on the same platform with a different name over the door, that learning either transfers intact or it was never worth much. Our documents make this an invariant in the strict sense, stating that the safety ladder is platform infrastructure rather than themable surface, that its semantics and interaction shape stay identical everywhere, and that during the deepest intervention the interface goes completely still, with no animation and no indicator, in every studio on the platform.\n\nWhat a tenant gets in exchange is genuinely large. A somatic practitioner can call their space a sanctum and their phases settling and witnessing. A leadership coach can call the same structures a studio and observing and committing. Both experiences feel authored, because the entire semantic layer is theirs, and the identity depth sits around six or seven on a ten-point scale from shallow to bespoke, deep in meaning and light in mechanics. What they cannot do is invent their own consent flow, their own destructive-action confirmation, or their own crisis presentation, and the honest version of that sentence is that we lose deals over it.\n\nThe trade is legible once you say what is actually being sold. Bespoke safety logic is a feature to the buyer and a liability to the person in the room, who did not choose the vendor and cannot audit the difference. So the atmosphere belongs to whoever holds the room, and the contract belongs to everyone who will ever stand in one, which is how a person carries what they learned about being safe from one threshold to the next without having to start over.",
  "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:theme-the-atmosphere-never-the-contract:r01",
        "author": "International Civil Aviation Organization",
        "work": "Standardized radiotelephony phraseology (Annex 10 and the associated procedures documents), revised following the Tenerife accident investigation",
        "year": 1977,
        "relevance": "The braided precedent. An industry that took a specific vocabulary away from its operators while leaving them every other element of their identity, because comprehension had to survive a change of airline, country, and accent."
      },
      {
        "id": "org:references:theme-the-atmosphere-never-the-contract:r02",
        "author": "Spanish Ministry of Transport and Communications, with the Netherlands Aviation Safety Board and the United States National Transportation Safety Board",
        "work": "Reports on the collision of KLM and Pan Am Boeing 747s at Los Rodeos, Tenerife, 27 March 1977",
        "year": 1978,
        "relevance": "The case itself, and specifically the finding that ambiguous non-standard phraseology between two competent crews was a contributing factor rather than any hidden failure or negligence."
      },
      {
        "id": "org:references:theme-the-atmosphere-never-the-contract:r03",
        "author": "MNSTRY platform documentation",
        "work": "Experience design specification (internal record of the theming boundary, the invariant core, and the white-label customization packs)",
        "year": 2026,
        "relevance": "The shipped boundary. What a tenant may rename and restyle, the non-themable invariants, the roughly forty renameable terms with collision validation, and the placement of identity depth on the shallow-to-bespoke spectrum."
      }
    ],
    "claims": [
      {
        "id": "org:claims:theme-the-atmosphere-never-the-contract:c01",
        "claim": "Two Boeing 747s collided on the runway at Los Rodeos, Tenerife, on 27 March 1977, killing 583 people, and the investigation identified ambiguous non-standard radiotelephony phraseology as a contributing factor.",
        "basis": "The official accident reports and the subsequent aviation-safety literature; long-settled rather than contested.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:theme-the-atmosphere-never-the-contract:c02",
        "claim": "The international aviation authorities standardized radiotelephony phraseology after the 1977 Tenerife runway collision, fixing the form of critical transmissions across every operator, country, and language.",
        "basis": "ICAO procedures and phraseology revisions following the accident, taught identically in licensing worldwide.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:theme-the-atmosphere-never-the-contract:c03",
        "claim": "Our experience design specification permits tenants to theme vocabulary, metaphors, phase names, color temperature, illustration tone, ceremony copy, and space naming, and forbids theming of the primitives, the consent grammar, the safety semantics, the privacy-state labeling, and the time model.",
        "basis": "The sixth operational principle of our own experience design document, read from the record before authoring. A statement about what our documents specify, not a measured outcome.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:theme-the-atmosphere-never-the-contract:c04",
        "claim": "The same specification holds as an invariant that the safety ladder is platform infrastructure rather than themable surface, with identical semantics and interaction shape everywhere, and requires the interface to go completely still during the deepest safety state.",
        "basis": "The invariant core of the same document.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:theme-the-atmosphere-never-the-contract:c05",
        "claim": "The specification bounds lexicon replacement at roughly forty client-facing terms, each with a character limit and a revert, and validates that a renamed term does not collide with the safety or consent language.",
        "basis": "The white-label identity depth section of the same document, which also lists the never-themed elements.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:theme-the-atmosphere-never-the-contract:c06",
        "claim": "The same section places identity depth at roughly six or seven on a ten-point scale from shallow to bespoke, deep in semantics, medium in structure, light in mechanics.",
        "basis": "Stated numerically in the same section.",
        "confidence": "verified",
        "sources": []
      }
    ],
    "concepts": [
      {
        "id": "org:concepts:non-themable-contract",
        "name": "Non-themable contract",
        "definition": "The set of interface elements a white-label platform holds as infrastructure rather than as tenant surface, because safety is recognized rather than read and recognition is built by repetition across contexts. The atmosphere belongs to whoever holds the room; the consent grammar, the safety semantics, the privacy labeling, and the time model belong to everyone who will ever stand in one.",
        "provenance": "canonical"
      },
      {
        "name": "Atmosphere and contract",
        "definition": "The distinction between what a tenant may make its own, the vocabulary, metaphors, and feel of a space, and what it may never touch, the grammar by which consent, privacy, and safety are expressed.",
        "provenance": "local"
      },
      {
        "name": "Recognition before reading",
        "definition": "The observation that safety states are apprehended by pattern rather than parsed as text, which makes cross-vendor consistency of shape a functional requirement rather than a branding preference.",
        "provenance": "local"
      }
    ],
    "researchContext": "The structural argument applied to a commercial boundary. The parent essay\nargues that safety belongs in the shape of a system rather than in\npromises about behavior; this brick takes one specific shape decision,\nwhere the white-label boundary is drawn, and shows that the pressure on it\nis revenue rather than engineering. The essay's three moves are not\nrestated. What is new here is the claim that a safety grammar is\ninfrastructure because recognition is built by repetition across contexts,\nwhich makes cross-tenant consistency a property of the person rather than\nof the platform.\n\nThe Tenerife case is braided in rather than cited as authority, and it is\ndoing one job. It shows an industry choosing to take a vocabulary away\nfrom operators who had done nothing wrong, in a domain where the cost of\nambiguity is measured in lives, which establishes that the ordering is a\nsettled answer elsewhere rather than a scruple invented for software. The\nbrick is careful to state that both crews were competent and that nothing\nwas hidden, because the argument is about ambiguity between capable\nparties and not about negligence.\n\nEvery internal claim is graded as a statement about what our documents\nspecify. The brick makes no claim about client outcomes, and the sentence\nabout recognition transferring between practitioners is written as the\ndesign's premise rather than as a measured result.\n\nPer the wave's de-identification ruling, no tenant is named, the\npractitioner appears as the expert holding the room, and the illustrative\nstudios are generic role descriptions rather than any real customer. The\ncost of the position, losing deals to buyers who want bespoke safety\nlogic, is stated in the published body rather than kept back here."
  },
  "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json",
  "releaseHash": "7ee9e602ed3dfadadb89667ebad2f6cfdc244c010ad8c05503018019ac6836c3",
  "versions": [
    {
      "version": 1,
      "cutAt": "2026-08-03",
      "note": "Initial publication, incentives wave",
      "visibility": "published",
      "path": "/writing/theme-the-atmosphere-never-the-contract/",
      "contentHash": "sha256:9c8552e357be293f",
      "releaseHash": "7ee9e602ed3dfadadb89667ebad2f6cfdc244c010ad8c05503018019ac6836c3"
    }
  ]
}