Skip to content

Boundary Disclosure Card

Prime #
667
Origin domain
Information Communication
Subdomain
standards and disclosure → Information Communication

Core Idea

A boundary disclosure card is a small, schematized, standardized disclosure physically or digitally attached to an artifact at its boundary of reuse, surfacing the conditions of proper use to every downstream consumer who encounters the artifact. The structural commitment has four parts. The artifact is reused across consumers who do not see how it was produced and cannot easily inspect it before use. A small set of load-bearing facts about proper use — contents, limits, hazards, provenance, expiry, dependencies — is selected from a much larger background of possible facts. Those facts are schematized, encoded against a stable, agreed template so consumers can read them without learning the producer's idiom.[1] And the schematized disclosure is attached at the boundary — physically affixed, structurally embedded, or contractually shipped — so that consuming the artifact and encountering the card are the same event.

The prime turns documentation-that-might-be-read into a disclosure-that-cannot-be-missed. The structural force is the indissoluble linkage between artifact and card: documentation that lives in a separate manual, on a website, or in producer memory does not clear the bar, while documentation that travels stapled to the boundary of every instance does. Detachment of card from artifact is the characteristic failure mode, and when a use-failure traces to a missing or stale card, the structural diagnosis is interface rather than content.

What changes in a reader's view of a system is that the schema itself becomes a distinct coordination object, separate from any individual card. Agreeing the template across producers is the heaviest design move and largely determines what consumers can ask; the card is the per-instance instantiation of that schema. The disclosure is also not the artifact's contents but a small projection onto a load-bearing fact set, and the compression is structural rather than incidental, because readability at the moment of consumption requires the projection to be small.

How would you explain it like I'm…

The Stuck-On Label

When you get medicine, there's a little label stuck right on the bottle that tells you how much to take. You can't grab the bottle without seeing the label. A Boundary Disclosure Card is like that label that goes wherever the thing goes, so you always learn the important stuff right when you use it.

Can't-Miss Label

Imagine someone makes a thing and other people use it later, but those people never watched it being made and can't easily check inside it. A Boundary Disclosure Card is a small standard tag stuck onto the thing that lists the few facts you really need: what it is, its limits, dangers, where it came from, and when it expires. The trick is that the card is attached to the thing itself, so using the thing and reading the card happen at the same moment. A manual sitting on a far-away website doesn't count, because you might never open it.

Disclosure You Can't Miss

A Boundary Disclosure Card is a small, standardized summary physically or digitally attached to an artifact right at the edge where someone else will reuse it. It picks a handful of load-bearing facts about proper use, contents, limits, hazards, source, expiry, dependencies, out of a huge background of possible facts. Those facts are written against a shared template so any consumer can read them without learning the maker's private style. Its whole power comes from being inseparable from the artifact: a manual on a website is documentation-that-might-be-read, while a card stapled to every instance is disclosure-that-cannot-be-missed. When something goes wrong because the card was missing or stale, the problem is the interface, not the content.

 

A Boundary Disclosure Card is a small, schematized, standardized disclosure attached to an artifact at its boundary of reuse, surfacing the conditions of proper use to every downstream consumer. It rests on four structural commitments: the artifact is reused by consumers who didn't see it produced and can't easily inspect it; a small set of load-bearing facts (contents, limits, hazards, provenance, expiry, dependencies) is selected from a vast background of possible facts; those facts are schematized against a stable shared template so they're readable without learning the producer's idiom; and the disclosure is attached at the boundary, so consuming the artifact and encountering the card are one event. The force of the prime is the indissoluble linkage between artifact and card, which is what separates it from documentation living in a separate manual or website. Detachment is the characteristic failure mode, and a use-failure traced to a missing or stale card is diagnosed as an interface problem, not a content problem. The schema itself becomes a distinct coordination object: agreeing the template across producers is the heaviest design move and determines what consumers can even ask. The card is just the per-instance instantiation of that schema. The disclosure is a deliberately small projection onto a load-bearing fact set, not the artifact's full contents, and the compression is structural because readability at the moment of consumption demands the projection stay small.

Structural Signature

an opaque reusable artifact — a reuse boundary crossed by consumers who cannot inspect the production — a selected set of load-bearing use-facts projected from a larger background — a shared schema (template) standardizing those facts — a per-instance card instantiating the schema — an indissoluble attachment fusing card to artifact at the boundary — detachment as the characteristic failure mode

The pattern is present when each of the following holds:

  • An opaque reusable artifact. A thing consumed across many users who do not see how it was produced and cannot easily inspect it before use — a food, a drug, a component, a dataset, a beam.
  • A reuse boundary. A point at which the artifact passes from producer to consumer, impersonally and at scale, so trust and shared context are unavailable.
  • A selected fact set. A small set of load-bearing facts about proper use — contents, limits, hazards, provenance, expiry, dependencies — projected out of a much larger background. The smallness is required for readability at consumption time.
  • A shared schema. The facts are encoded against a stable, agreed template, so consumers read them without learning each producer's idiom. The schema, not the individual card, is the heavy coordination object.
  • A per-instance card. Each artifact instance carries its own instantiation of the schema.
  • Indissoluble attachment. The card is affixed, embedded, or contractually shipped so that consuming the artifact and encountering the card are the same event — distinguishing disclosure from mere documentation.
  • Detachment as failure mode. When card and artifact separate, or the card goes stale, the diagnosis is interface failure, not content failure.

These compose into a substitute for inspection and trust at impersonal reuse: agree the schema, attach it to every instance, and audit detachment.

What It Is Not

  • Not provenance. provenance (the embedding nearest neighbor) is the record of origin and chain of custody — where an artifact came from and how it changed hands. A boundary disclosure card may include a provenance slot, but its defining feature is the attached, schematized, standardized disclosure of use-conditions at the reuse boundary, of which origin is one fact among five.
  • Not an interface. interface is the boundary-and-contract across which components interact functionally. The card is disclosure attached at a reuse boundary, not the operative contract governing interaction; a nutrition label tells you what is inside, it does not define how the food plugs into anything.
  • Not containment. containment is keeping something inside a boundary (or out). The card does the opposite — it exposes selected facts across the boundary so consumers can read them; its concern is disclosure and readability, not confinement of contents.
  • Not versioning. versioning is the discipline of tracking successive states of an artifact. A lifecycle/version marker is one slot on the card, but the card is the standardized disclosure surface, not the version-control mechanism; versioning answers "which state is this?", the card answers "what must I know to use it safely?"
  • Not conflict of interest. conflict_of_interest is a structural misalignment of incentives. The card's "claims-not-truth" caveat touches this — a producer discloses self-servingly — but the prime is the disclosure artifact and its schema, not the incentive misalignment that an audit regime, not the card, addresses.
  • Common misclassification. Calling any documentation a boundary disclosure card. The tell: ask whether a consumer can complete the use without passing through the disclosure. If the facts live in a separate manual, a website, or producer memory, it is documentation; only an indissoluble attachment that makes consuming the artifact and reading the card the same event clears the bar.

Broad Use

In food, the nutrition-facts label, allergen disclosure, and dating marks are a standardized schema printed on every package by regulation, identical across producers.[2] In pharmaceuticals, package inserts carry indications, dosage, contraindications, and interactions in every box.[3] In electronics, datasheets ship with every component, their industry-stable schema letting engineers read across vendors. In hazardous materials, safety data sheets travel with every shipment under an internationally agreed sixteen-section schema.[4] In buildings, occupancy plaques and capacity placards are affixed at the point of use.[5] In software, API documentation and machine-readable interface schemas ship with the endpoint, and dependency manifests travel with the package. In machine learning, data cards and model cards — explicitly borrowing the nutrition-label idea — travel with datasets and models, carrying composition, intended use, and known limitations.[6] In consumer goods, care labels and energy-rating stickers attach the disclosure to the item. In materials engineering, load and pressure ratings are stamped onto the part itself.[7] Across these substrates the structural force is the same: when the producer-consumer interface is wide and reuse is impersonal, a standardized disclosure attached to the boundary substitutes for the trust, inspection, or shared context the consumer cannot otherwise obtain — and the fact that ML data cards explicitly borrowed the food-label pattern is direct evidence of the structure's portability.[8]

Clarity

Naming the pattern surfaces a sharp distinction: documentation, which the consumer must seek out and may or may not read, versus boundary disclosure, which the consumer cannot encounter the artifact without also encountering. The two are routinely conflated in everyday speech — "it's all in the docs" — but their operational properties differ sharply. Documentation is a universal fallback; boundary disclosure is a structural property of the artifact-consumer interaction, and only the latter guarantees the disclosure is seen at the decision point.

A second clarification separates the schema from the card. The schema — the nutrition-facts template, the safety-data-sheet sections, the model-card structure — is a small standards object that producers and consumers agree to honor, and the card's value comes mostly from the schema being shared; an idiosyncratic per-producer disclosure does not clear the bar even if attached. A third clarification distinguishes the card from the artifact's contents: a nutrition label is a small projection of the food onto a small fact set, and the compression is required for readability rather than being a limitation. By holding these three distinctions — disclosure versus documentation, schema versus card, card versus contents — the prime makes precise what would otherwise be lumped together as "having good documentation."

Manages Complexity

A boundary disclosure card lets a consumer make a use-or-not-use decision and a usage-parameters decision without inspecting the artifact's internals. The card carries exactly the load-bearing facts; the artifact carries everything else. This collapses the consumer's decision problem from "understand the artifact" to "read the card and check the intended use against the declared limits," a far smaller task that scales across impersonal reuse.

Across the candidate domains the same accounting recurs in a small recognizable schema: an intended-use envelope, the conditions under which the producer warrants behavior; hazards and limits, the failure modes outside the envelope; composition and provenance, what the artifact is made of and where it came from; dependencies and interactions, what else must be present; and lifecycle markers — expiry, deprecation, version. Whether the artifact is a drug, a dataset, or a steel beam, this five-slot accounting is recognizable, which is what lets a single design discipline — agree the schema, attach it to every instance, audit detachment — serve domains as different as pharmaceuticals and machine learning. The compression is in reducing an open-ended "what do I need to know to use this safely?" to a fixed, shared set of slots.

Abstract Reasoning

The prime supports several inferences. The schema is the coordination object, so agreeing it across producers is the heaviest design move and largely determines what consumers can ask. Detachment is the characteristic failure mode, so a use-failure traced to a missing or stale card is diagnosed as an interface failure rather than a content failure. Schema gaps make harms invisible: a known harm with no slot in the schema — environmental impact absent from early food labels, demographic-bias breakdowns absent from early model cards — is structurally hidden until a slot is added.

Two further inferences concern dynamics and limits. Schemas evolve under incident pressure: new slots are added when a class of incidents reveals a previously absent disclosure, as allergen lists expanded after fatal incidents and model-card sections expanded after bias incidents.[9] And cards establish only that the producer claims the disclosed facts, not that they are true — a separate audit or certification regime validates content, while the card itself is the exposed surface for liability, since what a producer discloses is what they can be held to. These inferences follow from the attached-schematized-standardized structure alone, so they apply to any reuse boundary regardless of whether the artifact is physical, digital, or informational, and they tell a designer where the system's blind spots and liabilities will fall.

Knowledge Transfer

The transferable content is the four-commitment structure — selection, schematization, attachment, standardization — together with the five-slot accounting and the schema-as-coordination-object insight. Because the structure is substrate-portable, the moves carry across domains, and the historical record shows the transfer happening explicitly: food-labeling discipline was deliberately borrowed into machine learning as data cards and "nutrition labels for ML," solving the same coordination problem with the same small-schema-attached-at- reuse move.[8] Component datasheets port to API contracts, with recommended operating conditions and max ratings becoming rate limits, auth schemes, and error codes, and machine-readable interface specifications as the schematized form. Pharmacology package inserts port to AI system cards — indications and contraindications becoming intended and out-of-scope uses. Safety data sheets port to software dependency manifests, the bill-of-materials that travels with every package as the analogue of the sheet that travels with every regulated substance.

These transfers work because the structural roles are stable across substrates: an opaque reusable artifact, a reuse boundary, a shared schema, a per-instance card, an indissoluble attachment, a declared use-envelope, and a detachment failure mode. A food regulator, an API designer, a model-card author, and a materials engineer are all running the same move: select the load-bearing facts, schematize them against a shared template, and attach them so the consumer cannot use the artifact without seeing them. The portable intervention is uniform — agree the schema, attach it to every instance, and audit detachment as a failure — and the empirical observation that a substrate which standardizes its disclosure schema enjoys lower per-instance disclosure cost and better cross-vendor comparison than one that has not gives the transfer a predictive edge. The portable lesson is that safe impersonal reuse depends not on better documentation but on a small shared disclosure fused to the artifact's boundary, a lesson that travels intact from a cereal box to a trained model, and that, once held, reframes governance of reused artifacts around the schema and its attachment rather than around hoping the manual gets read.

Examples

Formal/abstract

The hazardous-materials Safety Data Sheet (SDS) is the disclosure card in its most formally specified form, and tracing its structure shows the prime's commitments operating as a designed protocol. The opaque reusable artifact is a regulated chemical substance, consumed across countless downstream handlers who cannot inspect its composition or hazards by looking. The reuse boundary is each shipment crossing from producer to handler, impersonally and at scale. The selected fact set is a small projection from the vast space of chemical facts onto exactly what governs safe handling — and the shared schema is the heavy coordination object: the Globally Harmonized System fixes sixteen numbered sections in a mandated order (identification, hazards, composition, first-aid, firefighting, accidental-release, handling, exposure controls, and so on).[4] Because the schema is internationally agreed, a handler in any country reads section 4 for first-aid without learning each producer's idiom — the standardization that makes the card more than per-producer documentation.[4] The per-instance card is the sheet shipped with each substance; the indissoluble attachment is the regulatory requirement that the SDS travel with the shipment, so receiving the chemical and receiving the sheet are one event. The detachment failure mode is precise and auditable: a shipment whose SDS is missing or stale is a compliance failure located at the interface, not a defect in the chemical itself. The schema-gap inference is visible historically — hazards with no section to live in were structurally invisible until the harmonized template added a slot for them, exactly as the prime predicts.

Mapped back: the SDS instantiates every commitment — selection of a load-bearing fact set, schematization against a sixteen-section template, standardization across producers, and indissoluble attachment to each shipment — with detachment as an auditable interface failure, showing the five-slot accounting as a literal regulatory artifact.

Applied/industry

Machine-learning model cards are the same structure deliberately borrowed into a new substrate, which is itself the prime's portability claim made concrete. The opaque reusable artifact is a trained model, consumed by downstream developers who integrate it without seeing its training data or knowing its failure modes. The reuse boundary is the model's release on a hub, impersonally and at scale. The selected fact set maps onto the prime's five recognizable slots: an intended-use envelope (what the model is warranted for), hazards and limits (known failure modes, out-of-scope uses), composition and provenance (training data sources, demographics), dependencies (required preprocessing, compute), and lifecycle markers (version, deprecation).[6] The shared schema — the model-card template — is again the coordination object, and the field consciously imported it from the food nutrition label, sometimes literally calling the artifacts "nutrition labels for ML."[8] The indissoluble attachment is the card shipped in the model repository alongside the weights. The prime's schema-evolution-under-incident inference is observable: early model cards lacked demographic-bias breakdowns, so that harm class was structurally hidden until bias incidents pressured the template to add the slot — precisely the dynamic by which allergen lists expanded on food labels after fatal incidents.[6] And the claims-not-truth inference holds: a model card establishes what the producer discloses, defining the surface for accountability, while a separate evaluation regime validates whether the disclosed facts are true.

Mapped back: model cards are boundary disclosure cards — opaque artifact, reuse boundary, five-slot fact set, a borrowed standardized schema, attachment to the release — and the documented borrowing from food labels plus the incident-driven addition of bias slots exhibit the prime's portability and schema-evolution inferences directly.

Structural Tensions

T1 — Disclosure versus Documentation (scopal). The prime's defining line is that a card cannot be missed because consuming the artifact and encountering the card are the same event — unlike documentation, which must be sought. The failure mode is fake compliance: shipping a card that is technically attached but practically un-encountered (buried in a repo, a hyperlink in fine print, a manual no one opens), which has the form of disclosure but the operational properties of documentation. Diagnostic: ask whether a consumer can complete the use without passing through the card. If they can, attachment has failed and the artifact has documentation, not boundary disclosure — and the missed-fact failures will follow exactly as if no card existed.

T2 — Selection versus Completeness (measurement). The card must project a small load-bearing fact set for readability, but every omitted fact is a potential blind spot, and there is no neutral way to decide what is load-bearing — the selection encodes a theory of what matters. The failure mode is a schema gap: a real harm with no slot is structurally invisible (environmental impact absent from early food labels, demographic bias absent from early model cards), so the card's very compression hides the hazard. Diagnostic: ask what known harm classes have no slot in the schema. The prime's readability requirement and its completeness requirement pull against each other; a card small enough to read is a card that has decided, fallibly, what to leave out.

T3 — Schema Stability versus Incident-Driven Evolution (temporal). The schema's value comes from being stable and shared across producers — yet the prime also shows schemas must add slots under incident pressure as new harm classes surface. These pull oppositely: every revision that closes a blind spot also breaks the cross-producer, cross-version comparability that made the schema worth coordinating on. The failure mode is either freezing the schema against needed slots (preserving comparability while harms stay hidden) or churning it so fast that no two cards are comparable. Diagnostic: ask whether the schema has a versioned evolution process that adds slots without invalidating prior cards. Stability and adaptivity are both load-bearing; a schema that optimizes one without managing the other fails on the other axis.

T4 — Claims versus Truth (scopal). A card establishes only what the producer discloses, not that the disclosure is true — validation requires a separate audit or certification regime the card does not provide. The failure mode is consuming the card as verified fact: a model card's "intended use" or a supplement's "contents" treated as warranted when it is merely asserted, so a false or self-serving disclosure passes as safety information. Diagnostic: ask what independent regime checks the card's claims, and whether the consumer can distinguish a disclosed claim from a verified one. The prime hands off here to certification and audit primes; the card is the liability surface (what the producer can be held to), not the truth surface, and conflating the two manufactures false confidence.

T5 — Schema Coordination versus Producer Heterogeneity (scalar). The card's power scales with how universally the schema is shared — an idiosyncratic per-producer disclosure does not clear the bar even if attached. But agreeing one template across a heterogeneous producer population is the heaviest design move, and producers have divergent interests in what the schema reveals. The failure mode is premature or captured standardization: a schema agreed too narrowly (excluding producers who then ship incomparable cards) or shaped by incumbents to omit slots that would expose them. Diagnostic: ask who set the schema and which producers it actually binds. The coordination object's value is proportional to its reach; a schema honored by half the field, or designed by the disclosed-against, delivers a fraction of the comparability the prime promises.

T6 — Card Currency versus Substrate Drift (temporal). Attachment fuses card to artifact at the boundary, but the artifact's properties can change after the card is written — a dataset updated, a model fine-tuned, a component re-sourced — leaving an attached but stale card that discloses the wrong facts with full apparent authority. The failure mode is trusting a current-looking card whose contents lag the substrate: the consumer reads accurate-seeming disclosure for a version that no longer exists. Diagnostic: check whether the card carries lifecycle markers (version, date, deprecation) and whether re-issuing the card is coupled to changing the artifact. Detachment is the prime's named failure, but staleness is its silent twin — a card present and attached can still mislead precisely because its presence signals a currency it no longer has.

Structural–Framed Character

The boundary disclosure card sits well onto the framed side of the structural–framed spectrum, aggregate 0.7. There is a real relational kernel — a standardized, schematized disclosure attached at an artifact's reuse boundary so that consuming and reading are one event — and that attach-at-the-boundary move has demonstrably strong cross-substrate transfer, from food labels to pharmaceutical inserts to hazmat placards to dataset and model cards. But two diagnostics read fully framed, and that is what dominates the score.

The institutional origin is unambiguous and scores full: the card is at bottom a regulatory-and-standards category, the product of human bodies that mandate disclosure at producer-consumer interfaces, and its very existence presupposes a standardization regime. It is fully human-practice-bound as well: a "disclosure to a downstream consumer" requires a consumer who reads and a producer who is accountable — there is no boundary disclosure card in a purely physical or biological system, because the card is a communicative artifact in a human institutional interface, not a pattern that runs in indifferent substrates. Those two full marks are the heart of the framing. The other three diagnostics sit at the midpoint and keep the score at 0.7 rather than higher: the vocabulary half-travels (terms like "label," "card," "disclosure," "intended-use envelope" carry their consumer-product origin but each domain renames the surface — nutrition label, datasheet, model card), the evaluative weight is half-present (a card is framed as a transparency good, carrying mild approval, though the bare structure is neutral about whether disclosure is virtuous), and invoking it half-imports a frame (you bring the standards-and-transparency perspective, but you also genuinely recognize an attach-at-the-boundary delivery mechanism that exists independently). The honest reading is a framed prime resting on a genuinely transferable disclosure-interface kernel — but one that cannot be invoked without importing its regulatory, human-interface frame, which is precisely what the institutional-origin and human-practice full marks, and the 0.7 aggregate, record.

Substrate Independence

The boundary disclosure card is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its domain breadth is wide: a schematized, standardized disclosure attached at the point of reuse recurs across food (nutrition-facts labels, allergen disclosure), pharmaceuticals (package inserts), electronics (datasheets), hazardous materials (safety data sheets under an internationally agreed sixteen-section schema), buildings (occupancy and capacity placards), software (API documentation, machine-readable interface schemas, dependency manifests), machine learning (data cards and model cards), and consumer goods (care labels, energy-rating stickers). What lifts the transfer evidence to a full 5 is that this cross-substrate transfer is not merely structural but historically explicit and documented: ML data cards and model cards were designed by deliberately borrowing the nutrition-label idea, a named, traceable transfer of the pattern from one substrate to another. The structural abstraction sits at 3 — one notch below — because the prime carries real commitments that are not fully medium-neutral: it presupposes a producer-consumer interface, a reuse boundary, and a standardization regime, so the "card" is a sociotechnical artifact rather than a bare relational shape, and its force depends on the impersonal-reuse context. The composite of 4 reflects this honestly: broad reach and exceptionally concrete transfer, tempered by a signature that carries the institutional commitments of standardized disclosure rather than abstracting fully away from them.

  • Composite substrate independence — 4 / 5
  • Domain breadth — 4 / 5
  • Structural abstraction — 3 / 5
  • Transfer evidence — 5 / 5

Relationships to Other Primes

One-hop neighborhood: parents above, mutual partners to the right, children below.BoundaryDisclosure Cardcomposition: InterfaceInterfacedecompose: ProvenanceProvenance

Parents (1) — more general patterns this builds on

  • Boundary Disclosure Card presupposes, typical Interface

    A standardized disclosure ATTACHED at an artifact's reuse boundary; it presupposes a producer-consumer reuse boundary (interface) but is the disclosure surface attached at it, not the operative contract.

Children (1) — more specific cases that build on this

  • Provenance decompose Boundary Disclosure Card

    Origin/lineage is one of ~five fact-slots a card carries (alongside intended-use envelope, hazards, dependencies, lifecycle). Provenance is broader than the card, so part-of, not a reparent of provenance.

Path to root: Boundary Disclosure Card → Interface → Boundary

Neighborhood in Abstraction Space

Boundary Disclosure Card sits in a sparse region of abstraction space (69th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.

Family — Provenance, Integrity & Interoperability (11 primes)

Nearest neighbors

Computed from structural-signature embeddings · 2026-06-14

Not to Be Confused With

The boundary disclosure card's nearest catalog neighbor is provenance, and the two are genuinely entangled because origin-and-history is one of the facts a card typically carries. The distinction is between a fact type and a delivery mechanism. provenance is the content: the record of where an artifact came from, what it is made of, and how it has changed hands — a chain of custody that establishes lineage and authenticity. A boundary disclosure card is the standardized, attached disclosure surface through which a small set of load-bearing use-facts (of which provenance is one of roughly five — alongside intended-use envelope, hazards and limits, dependencies, and lifecycle markers) is delivered to every downstream consumer at the reuse boundary. The card's defining commitments — selection of a small fact set, schematization against a shared template, standardization across producers, and indissoluble attachment so that consuming and reading are one event — are properties of the disclosure interface, not of the lineage record. The two come apart cleanly: an artifact can have rich provenance documented in a separate ledger no consumer ever reads (provenance without a boundary card), or a card can carry an intended-use envelope and hazard list while saying nothing about origin (a boundary card whose fact set omits provenance). The confusion matters because the remedies differ: a provenance failure is fixed by establishing or auditing the origin record, while a boundary-card failure is fixed by agreeing the schema and attaching it to every instance — a coordination-and-interface problem, not a lineage problem. Treating a card as "just provenance" loses the schema-as-coordination-object insight that is the prime's heaviest design move.

A second, subtler confusion is with signaling, because a disclosure card is, in one sense, a producer emitting information about an otherwise-opaque artifact to an audience that cannot inspect it — which is exactly the setup of signaling theory. The difference lies in what makes the communication credible and what it is for. signaling is concerned with how a sender conveys unobservable quality credibly to a receiver despite an incentive to misrepresent, with the credibility resting on the signal being costly to fake (a degree, a warranty, a peacock's tail). The boundary disclosure card is not primarily a credibility device and does not derive its force from costliness-to-fake; the prime explicitly notes its claims-not-truth property — the card establishes only what the producer discloses, not that the disclosure is true, with a separate audit or certification regime doing the verification. The card's value comes instead from standardization and attachment: a consumer can read a hazard or a dosage against a shared template at the moment of use, regardless of whether the producer is trying to look good. Where a signal's purpose is to separate high types from low types through differential cost, a card's purpose is to make a fixed fact set legible at the boundary so that inspection and trust are unnecessary for routine safe use. Conflating them invites the error of treating a disclosure schema as a quality-signaling game — designing for costly-to-fake credibility — when the actual design problem is coordinating a shared template and fusing it to every instance, with credibility delegated to an external audit.

For a practitioner the distinctions route the design. Use provenance when the question is establishing and verifying lineage; use signaling when the question is conveying unobservable quality credibly against an incentive to misrepresent; and use the boundary disclosure card when the question is making a small, standardized fact set unmissable at an impersonal reuse boundary. The card's unique contribution — and what neither neighbor supplies — is the fusion of selection, shared schema, and indissoluble attachment that turns documentation-that-might-be-read into disclosure-that-cannot-be-missed.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.

References

[1] Fröhlich, Xaq. "The Informational Turn in Food Politics: The US FDA's Nutrition Label as Information Infrastructure." Social Studies of Science, vol. 47, no. 2 (2017): 145–171. Traces how the nutrition label became a standardized informational template that lets consumers read product facts against a stable, agreed format rather than each producer's idiom — supporting that boundary disclosures are schematized against a shared template. ↩

[2] U.S. Food and Drug Administration. "Food Labeling: Revision of the Nutrition and Supplement Facts Labels." Federal Register, vol. 81, no. 103 (May 27, 2016): 33741–33999. Codifies the standardized nutrition-facts label printed on every package, identical across producers by regulation. ↩

[3] U.S. Food and Drug Administration. Requirements on Content and Format of Labeling for Human Prescription Drug and Biological Products (Physician Labeling Rule; 21 CFR 201.56–201.57). Final rule, 71 Fed. Reg. 3922 (Jan. 24, 2006). Mandates that prescription-drug labeling (package inserts) carry indications, dosage, contraindications, and interactions in a fixed order in every box. ↩

[4] United Nations. Globally Harmonized System of Classification and Labelling of Chemicals (GHS), 9th revised edition. Geneva: United Nations, 2021. Fixes the sixteen-section Safety Data Sheet format in mandated order that travels with every shipment internationally. ↩

[5] International Code Council. 2021 International Building Code (IBC), Section 1004.9 “Posting of occupant load”. ICC, 2021. Requires occupant-load (capacity) signs of approved permanent design posted conspicuously near the main exit in assembly occupancies. ↩

[6] Mitchell, Margaret, Simone Wu, Andrew Zaldivar, Parker Barnes, Lucy Vasserman, Ben Hutchinson, Elena Spitzer, Inioluwa Deborah Raji, and Timnit Gebru. "Model Cards for Model Reporting." Proceedings of the Conference on Fairness, Accountability, and Transparency (FAT '19)* (2019): 220–229. Introduces the model-card schema carrying intended use, known limitations, and demographic-breakdown evaluation, explicitly motivated by disclosure analogues. ↩

[7] American Society of Mechanical Engineers. ASME Boiler and Pressure Vessel Code, Section VIII, Division 1 (rules for construction of pressure vessels; nameplate marking under UG-118 / UG-119). New York: ASME. Requires the maximum allowable working pressure and design temperatures to be stamped on a nameplate affixed to (or marked directly on) the vessel itself. ↩

[8] Gebru, Timnit, Jamie Morgenstern, Briana Vecchione, Jennifer Wortman Vaughan, Hanna Wallach, Hal Daumé III, and Kate Crawford. "Datasheets for Datasets." Communications of the ACM, vol. 64, no. 12 (2021): 86–92. Proposes dataset documentation explicitly borrowing the electronics-datasheet and consumer-label idea for datasets and models. ↩

[9] U.S. Congress. Food Allergen Labeling and Consumer Protection Act of 2004 (FALCPA), Public Law 108-282, Title II. 2004. Added mandatory plain-language declaration of the major food allergens, an example of a disclosure slot expanded under incident pressure. ↩