{
  "schema": "org-writing@v1",
  "slug": "surfacing-at-need",
  "kg": {
    "id": "org:writing:surfacing-at-need",
    "type": "brick",
    "graph": "/kg.json"
  },
  "title": "Surfacing at need",
  "subtitle": "A kept thing that cannot find its moment was never really kept",
  "abstract": "Why the second virtue of a fired artifact is arrival rather than storage, from half a million recorded conversations waiting in a national archive to a product surface required to be absent when it has nothing true to say. The canonical treatment of surfacing at need.",
  "kind": "brick",
  "topics": [
    "Practice"
  ],
  "courseMemberships": [
    {
      "course": "org:courses:practitioner",
      "topic": "Practice",
      "wall": "org:walls:engineering",
      "position": 4,
      "total": 5
    }
  ],
  "publishedAt": "2026-08-03T00:00:00.000Z",
  "version": 1,
  "guidelinesVersion": 15,
  "brief": {
    "problem": {
      "text": "Archives are built to answer a request, and the counsel most worth keeping arrives for someone who has the need and not the name for it, so it waits perfectly preserved and never comes.",
      "claims": [
        "StoryCorps has recorded conversations with more than half a million participants"
      ]
    },
    "mechanism": {
      "text": "Findability by a person who does not know what they are looking for runs from the other end, where the structure reads the moment and holds the fixed thing against it, which makes the capacity to stay silent the thing that makes surfacing legible at all.",
      "claims": [
        "absent when it has nothing true to say"
      ]
    },
    "move": {
      "text": "Design the surfacing alongside the storing, and give the surface the standing to say nothing, because a thing that speaks on every occasion carries no information about the occasion.",
      "claims": []
    }
  },
  "sources": [
    {
      "repo": "mnstry-org",
      "path": "src/content/writing/cathedral-of-the-mind.md"
    },
    {
      "repo": "mnstry-monorepo",
      "path": "docs/30-design-system/DESIGN.md"
    }
  ],
  "canonicalPath": "/writing/surfacing-at-need/",
  "body": "Since 2003 StoryCorps has sat more than half a million people down in pairs, one microphone between them, and recorded the conversation, and the collection is preserved at the American Folklife Center at the Library of Congress. Every one of those recordings is a fired artifact in the sense this corpus means. Fixed, attributed, dated, no longer being generated and therefore no longer able to drift, which is a property settled elsewhere and is only half of what firing is for. The other half is harder, and almost nobody designs for it. A grandmother's counsel recorded in a booth in 2011 is worth what it is worth on one morning in some future year, to a grandchild who is not searching an archive and does not know the recording exists.\n\nThat morning has a specific shape, and it is not the shape archives are built for. An archive answers a query. Somebody knows what they lost, comes to the door, and asks for it by name, which is the seed vault's case exactly, catastrophe followed by a request, and the discipline that case demands is a rehearsed withdrawal. Surfacing is the other case entirely. The person has the need and not the name for it. They are having a hard week with a teenager, or standing in a hospital corridor, or about to do something they will regret, and nothing in that state produces a search term. Waiting for them to ask is a design decision that guarantees the good material stays dark.\n\nSo the problem inverts. Findability by a person who knows what they want is an indexing problem, solved competently for decades. Findability by a person who does not know has to run from the other end, where the structure reads the moment, holds the fixed things against it, and speaks only when the two genuinely meet, which makes the capacity to stay silent the thing that makes any of it legible. A system that offers something at every moment has told you nothing about this one.\n\nOur own design canon states that requirement as a rule about a surface rather than a rule about an archive. The contextual band in the product carries no more than two items and is required to be absent when it has nothing true to say, and a band that always shows the same items is retired on sight, because it has stopped being a moment and become a second navigation bar. Read as layout discipline that is a small thing. Read properly it is the whole dormancy argument compressed into a component. The silence is not restraint about clutter. It is what buys the appearance its meaning, since an artifact that arrives unbidden is making a claim about your situation, and a surface that makes that claim constantly is not making it at all.\n\nSo the requirement on anyone keeping knowledge for the long horizon is to build the surfacing with the same seriousness as the storing, and to accept the harder measure that follows. Not how much was preserved, and not how quickly it can be retrieved by someone who asks. Whether it arrived. Half a million conversations held in a national collection are not yet counsel, and they do not become counsel in bulk. They become counsel one morning at a time, when the right one reaches somebody who never knew to look for it, and a structure that can do that is no longer an archive. It is an inheritance.",
  "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:surfacing-at-need:r01",
        "author": "StoryCorps and the American Folklife Center, Library of Congress",
        "work": "The StoryCorps archive (recording since 2003; the full collection preserved at the American Folklife Center)",
        "year": 2003,
        "relevance": "The brick's scale case and the parent essay's own example, used here for the dormancy property rather than the oral-history one. Conversations recorded in pairs, fixed at the moment of recording, deposited against needs nobody could name at deposit time."
      },
      {
        "id": "org:references:surfacing-at-need:r02",
        "author": "MNSTRY design system",
        "work": "Places doctrine, the island rule (0 to 2 items, absent when it has nothing true to say; a surface that always shows the same items is retired on sight)",
        "year": 2026,
        "relevance": "Second-citer evidence from the product. The design rule that a contextual surface must be able to say nothing is the surfacing mechanism implemented as a component constraint, arrived at independently of this argument."
      }
    ],
    "claims": [
      {
        "id": "org:claims:surfacing-at-need:c01",
        "claim": "StoryCorps has recorded conversations with more than half a million participants since 2003, and the collection is preserved at the American Folklife Center at the Library of Congress.",
        "basis": "StoryCorps' own published figures and the Library of Congress announcement of the archive's home at the American Folklife Center. The participant count is the organization's reported figure and rises over time; the archival relationship is documented by the Library.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:surfacing-at-need:c02",
        "claim": "The MNSTRY design doctrine requires the contextual surface to be absent when it has nothing true to say, and retires any such surface that always shows the same items.",
        "basis": "The design system's places doctrine, an internal design document of record, quoted at its own wording.",
        "confidence": "verified",
        "sources": []
      }
    ],
    "concepts": [
      {
        "id": "org:concepts:contextual-dormancy",
        "name": "Contextual dormancy",
        "definition": "A fixed artifact can sit dark for years and surface at the moment of need; a time capsule delivered at a fluid moment.",
        "provenance": "canonical"
      },
      {
        "name": "Surfacing at need",
        "definition": "The design requirement that a kept artifact reach a person who has the need and not the name for it, which makes arrival rather than storage the measure of an archive.",
        "provenance": "local"
      }
    ],
    "researchContext": "Authored for the surfacing half only. The parent essay names contextual\ndormancy in passing and spends its argument on the long horizon; this brick\ntakes the arrival problem and leaves the two adjacent arguments where they\nalready live. The no-longer-generating mechanism belongs to\nfixity-requirement and is referenced here in a single clause as settled\nelsewhere, deliberately without restating its case. The rehearsed-withdrawal\ndiscipline belongs to seed-vault-withdrawal, and the distinction between the\ntwo is load-bearing rather than decorative: a withdrawal is requested by\nsomeone who knows what they lost, and surfacing serves someone who cannot\nform the request, so they are different design problems with different tests.\nThe island rule is quoted at its own wording because the paraphrase loses the\npart that does the work, which is the requirement of absence rather than the\nlimit on item count."
  },
  "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json",
  "releaseHash": "fd812e4bce9677643a5f952bb6f835e2428056327cb7a018c9024eefc5bd0b03",
  "versions": [
    {
      "version": 1,
      "cutAt": "2026-08-03",
      "note": "Initial publication, practitioner wave",
      "visibility": "published",
      "path": "/writing/surfacing-at-need/",
      "contentHash": "sha256:200202dd93c73d8d",
      "releaseHash": "fd812e4bce9677643a5f952bb6f835e2428056327cb7a018c9024eefc5bd0b03"
    }
  ]
}