{
  "$schema": "https://ndcodex.com/schemas/object/v1.json",
  "id": "codex://object/the-contract-travels-with-the-claim",
  "archive_id": "the-contract-travels-with-the-claim",
  "slug": "the-contract-travels-with-the-claim",
  "url": "https://ndcodex.com/codex/the-contract-travels-with-the-claim/",
  "type": "codex",
  "object_form": null,
  "title": "The Contract Travels with the Claim",
  "summary": "A claim can survive transformation while losing the conditions that made it responsible. Its evidence, qualifications, authority, and limits must travel too.",
  "content_text": "A claim rarely stays where it began.\n\nIt gets shortened for a page. Pulled into a presentation. Rewritten as a headline. Translated into another medium. Retrieved by an agent. Combined with other claims. Extracted by an answer engine and presented without the argument that once surrounded it.\n\nThe language changes. The obligations do not disappear.\n\nI have been thinking about this as contractual continuity across enactments.\n\nThe contract does not merely govern the claim at its origin. It accompanies the claim wherever the claim is used.\n\nBy contract, I mean the conditions that make an assertion responsible: its evidence, attribution, qualifications, authority, limitations, and the circumstances under which it may be repeated or acted upon.\n\nSome of those conditions are visible in the sentence. Others live in relationships around it.\n\nA number has a reporting period. A recommendation has a scope. A historical description has a source. A promise has someone authorized to make it. A confident sentence may depend on evidence that is current only for a particular place, audience, or version of the work.\n\nWhen a claim moves, those relationships are easy to lose.\n\nThis creates two kinds of inheritance.\n\nSemantic inheritance asks whether the new expression retains the meaning of the original claim.\n\nContractual inheritance asks whether it retains the obligations governing the use of that claim.\n\nBoth matter. Neither guarantees the other.\n\nAn answer can appear to summarize a claim accurately while omitting the qualification that prevents it from being misleading. The recognizable meaning survives, but the permission to use it that way does not.\n\nThis becomes especially important when systems are built to retrieve and recompose knowledge. The useful unit cannot be the sentence alone.\n\nThe agent needs a claim package.\n\nWhat is being asserted? What supports it? Which version of the evidence applies? What context is required? Who has authority? What must be attributed? Which limitations must appear in the resulting expression?\n\nWhen several claims become an argument, their contracts compose too. One source may permit public reuse. Another may require attribution. A third may be accurate only within a narrow timeframe. The system cannot silently discard those differences because the combined paragraph reads smoothly.\n\nCarrying the contract is only the first step. The resulting enactment must be checked at the point of use.\n\nDid the summary retain the essential qualification?\n\nDoes this audience change what needs to be explained?\n\nCan the evidence support this stronger wording?\n\nDoes the chosen medium remove context the claim depended on?\n\nIf the obligations cannot be satisfied, the expression needs to change. The system may need more context, an authorized exception, a narrower claim, or a decision not to publish it.\n\nThis is where provenance becomes operational. It stops being a record we preserve after the work and becomes part of how the work is allowed to move.\n\nExternal systems will not always keep the relationships we provide. A search result or generated answer may separate the statement from its source. That makes the published expression itself responsible for carrying any qualification it cannot safely survive without.\n\nThe practical test is simple to say and difficult to build:\n\nWhat survived the journey, what was transformed, what was lost, and may this enactment proceed?\n\nThe contract is not documentation beside the intelligence.\n\nIt is part of the intelligence.",
  "content_markdown": "# The Contract Travels with the Claim\n\nA claim rarely stays where it began.\n\nIt gets shortened for a page. Pulled into a presentation. Rewritten as a headline. Translated into another medium. Retrieved by an agent. Combined with other claims. Extracted by an answer engine and presented without the argument that once surrounded it.\n\nThe language changes. The obligations do not disappear.\n\nI have been thinking about this as **contractual continuity across enactments**.\n\nThe contract does not merely govern the claim at its origin. It accompanies the claim wherever the claim is used.\n\nBy contract, I mean the conditions that make an assertion responsible: its evidence, attribution, qualifications, authority, limitations, and the circumstances under which it may be repeated or acted upon.\n\nSome of those conditions are visible in the sentence. Others live in relationships around it.\n\nA number has a reporting period. A recommendation has a scope. A historical description has a source. A promise has someone authorized to make it. A confident sentence may depend on evidence that is current only for a particular place, audience, or version of the work.\n\nWhen a claim moves, those relationships are easy to lose.\n\nThis creates two kinds of inheritance.\n\n**Semantic inheritance** asks whether the new expression retains the meaning of the original claim.\n\n**Contractual inheritance** asks whether it retains the obligations governing the use of that claim.\n\nBoth matter. Neither guarantees the other.\n\nAn answer can appear to summarize a claim accurately while omitting the qualification that prevents it from being misleading. The recognizable meaning survives, but the permission to use it that way does not.\n\nThis becomes especially important when systems are built to retrieve and recompose knowledge. The useful unit cannot be the sentence alone.\n\nThe agent needs a claim package.\n\nWhat is being asserted? What supports it? Which version of the evidence applies? What context is required? Who has authority? What must be attributed? Which limitations must appear in the resulting expression?\n\nWhen several claims become an argument, their contracts compose too. One source may permit public reuse. Another may require attribution. A third may be accurate only within a narrow timeframe. The system cannot silently discard those differences because the combined paragraph reads smoothly.\n\nCarrying the contract is only the first step. The resulting enactment must be checked at the point of use.\n\nDid the summary retain the essential qualification?\n\nDoes this audience change what needs to be explained?\n\nCan the evidence support this stronger wording?\n\nDoes the chosen medium remove context the claim depended on?\n\nIf the obligations cannot be satisfied, the expression needs to change. The system may need more context, an authorized exception, a narrower claim, or a decision not to publish it.\n\nThis is where provenance becomes operational. It stops being a record we preserve after the work and becomes part of how the work is allowed to move.\n\nExternal systems will not always keep the relationships we provide. A search result or generated answer may separate the statement from its source. That makes the published expression itself responsible for carrying any qualification it cannot safely survive without.\n\nThe practical test is simple to say and difficult to build:\n\n**What survived the journey, what was transformed, what was lost, and may this enactment proceed?**\n\nThe contract is not documentation beside the intelligence.\n\nIt is part of the intelligence.",
  "author": {
    "id": "nathan-davis",
    "name": "Nathan Davis",
    "designation": "Archive Operator",
    "role": "Archive Operator",
    "handle": "@nathandavis",
    "avatar": "/media/people/nathan-davis.jpg",
    "bio": "Designer, builder, and curator of the Codex Archive."
  },
  "contributors": [
    {
      "id": "nathan-davis",
      "name": "Nathan Davis",
      "designation": "Archive Operator",
      "role": "Archive Operator",
      "handle": "@nathandavis",
      "avatar": "/media/people/nathan-davis.jpg",
      "bio": "Designer, builder, and curator of the Codex Archive."
    }
  ],
  "date_published": "2026-10-20T19:07:39.008Z",
  "date_modified": "2026-10-20T19:07:39.008Z",
  "status": "published",
  "visibility": "public",
  "language": "en-US",
  "axes": {
    "scale": "meso",
    "depth": "recursive",
    "focus": "system",
    "function": "diagnostic"
  },
  "themes": [
    "provenance",
    "human-agent collaboration",
    "publishing"
  ],
  "constellations": [],
  "tags": [
    "claims",
    "provenance",
    "agent systems",
    "publishing",
    "human-agent collaboration"
  ],
  "keywords": [
    "Codex",
    "provenance",
    "human-agent collaboration",
    "publishing",
    "claims",
    "agent systems"
  ],
  "relations": [],
  "media": [],
  "capture": null
}