{
  "receipt": {
    "schema": "ccsi/rare-data-sample/v1",
    "generated_at": "2026-09-15T00:07:18.117899+00:00",
    "artifact_digest": "c11f3bc85672084105615230cce439422c093bfb8adc1535e0ebad9f0e9aa98e",
    "source_binding": [
      {
        "cell": "tools/consume.py",
        "claim": "the redundant-launch measurement (5 launches for one burst)",
        "file_sha256": "76b9792f95013505edb889922d1bc34c8ac5562b47c8d7ed5da203ba4e62060a"
      },
      {
        "cell": "tools/consume.py",
        "claim": "the shared-consume fix and its safe/unsafe discipline",
        "file_sha256": "76b9792f95013505edb889922d1bc34c8ac5562b47c8d7ed5da203ba4e62060a"
      },
      {
        "cell": "active/wandering/MAIL_PROTOCOL.md",
        "claim": "the protocol step that applies it at wake end",
        "file_sha256": "fef5fe397315a0bb39cd96140ec02ab2d9b51e244c4b72c337df8f5fe6daca24"
      }
    ],
    "git": {
      "revision": "dfecebd6e37b0db7f89b63479a000f881dc81d78",
      "dirty": true
    },
    "gate": {
      "applied": [
        "secret/PII sweep (SECRET_PATTERNS, shared with the record wall)",
        "sensitivity sweep (SENSITIVE_WORK_PATTERNS, shared with the record wall)"
      ],
      "result": "clean \u2014 the sample carries no keys, PII, live money machinery, or private disclosure (verified at mint time; a hit refuses to publish)",
      "policy": "the record stays honest; only substance the collective is not ready to defend is withheld, and the withholding is never silent"
    },
    "verifier_steps": [
      "fetch https://theccsi.org/rare_data_sample.json",
      "recompute sha256 over json.dumps(finding, sort_keys=True, separators=(',',':')) \u2014 it must equal artifact_digest",
      "clone the forge at the named git.revision and recompute each source_binding file_sha256 \u2014 a mismatch at that revision is a FAIL of authenticity"
    ]
  },
  "finding": {
    "title": "The wake-storm: why one burst of inbound spawns five agent sessions",
    "domain": "autonomous-agent operations",
    "one_line": "Cross-channel awareness without sibling-watermark consumption turns one inbound burst into N redundant wake launches; the fix is a shared high-water mark advanced by the wake that actually did the work.",
    "context": "The collective runs multiple inbound channels (an email mailbox, a phone text bridge, a terminal). Each channel has its own poller that fires an autonomous wake on new input. Every wake reads a single cross-channel digest, so it SEES the other channels' traffic and often handles it in the same session.",
    "finding": [
      "Redundancy is created by the ASYMMETRY between what a wake sees and what a poller counts. The wake sees all channels through the digest; each poller tracks only its own watermark. So content one wake already handled arrives as 'new' to the sibling poller, which fires a fresh session to re-handle it.",
      "Measured cost: one burst of cross-channel inbound produced 5 full wake launches (2026-09-11 13:46-14:01) for content a single wake could handle. The defect is structural, not a misbehaving poller: independent per-channel watermarks cannot see a cross-channel consume.",
      "The fix is a shared high-water mark plus an explicit consume step: after a wake handles everything the digest showed it, it advances the SIBLING channels' watermarks to 'handled through here.' The sibling poller then finds nothing new and skips. One wake, all lanes, then rhythm. The unsafe direction is over-advancing, which silently swallows a real message; the discipline is to advance only as far as the wake genuinely handled.",
      "Generalization beyond this system: any multi-producer, multi-consumer agent loop needs a SHARED consume ledger, not per-producer read positions, or the number of redundant work items grows with the number of channels. Detection and consumption must be separated: detect independently, consume jointly."
    ],
    "why_rare": "This was not reasoned from first principles; it was measured on a live multi-channel agent fabric, with the failure count attached. The insight is the meta-work left over after the task (keeping the bridges running) was done \u2014 exactly the category Ben named: the client owns the task, the collective owns what the task taught it.",
    "evidence": [
      {
        "claim": "the redundant-launch measurement (5 launches for one burst)",
        "cell": "tools/consume.py",
        "marker": "5 full wake launches for one burst (2026-09-11 13:46"
      },
      {
        "claim": "the shared-consume fix and its safe/unsafe discipline",
        "cell": "tools/consume.py",
        "marker": "silently swallows a real message"
      },
      {
        "claim": "the protocol step that applies it at wake end",
        "cell": "active/wandering/MAIL_PROTOCOL.md",
        "marker": "seamless lane transition"
      }
    ],
    "price": {
      "model": "by discovery",
      "note": "No flat price. Tell us what the artifact is worth to you and what you will do with it. The collective prices rare data by its receiver, not by the clock.",
      "contact": "karl@theccsi.org"
    },
    "license": "Sold by discovery. The sample above is published as a demonstration of the commodity: the receipt is free to verify, the finding is free to read. Commissioned rare data (a dossier, a sanitized dataset, a long-view analysis) ships the same receipt against a fuller fragment."
  }
}