{
  "title": "Review Receipts",
  "story": [
    {
      "id": "01389e980b9bf8b8",
      "type": "markdown",
      "text": "\n# review receipts\n\nResolve the current draft body, title, destination, proverb, ledger reference, prerequisites and relevant upstream snapshot before review. Bind acknowledgment to that exact revision; any change invalidates the acknowledgment. Export the reviewed body and revision identifier in a receipt.\n\nTrack review, copying, reported publication and independently checked publication separately. A supplied publication URL is reported evidence until checked against the exact repository, target thread and comment anchor. Preserve immutable approval snapshots; do not reconstruct an absent historical snapshot from today's ledger.\n\nVerify generated specification prose by regenerating and comparing the actual marked sections as well as the source digest. Retain successful per-repository watermarks when a refresh fails. Test changed content, changed destination, incorrect publication URLs and historical snapshot stability.\n\nAn acknowledgment means the person reviewed this version. It does not establish comprehension, a bilateral MyTerms agreement, credential issuance or permission to publish. Read the installed DTG reader's board/review.test.mjs and conformance/test.mjs before adapting its contract; implementation paths vary by checkout.\n\nRelated: [Consent infrastructure](../agentprivacy-consent-infrastructure/SKILL.md), [Policy governance](../agentprivacy-policy-governance/SKILL.md).\n\n\n## Related operating practices\n\n\n\n[[City and Star Skills]]"
    }
  ],
  "journal": [
    {
      "type": "create",
      "date": 1788831114845,
      "item": {
        "title": "Review Receipts",
        "story": []
      }
    },
    {
      "type": "add",
      "id": "01389e980b9bf8b8",
      "item": {
        "id": "01389e980b9bf8b8",
        "type": "markdown",
        "text": "\n# review receipts\n\nResolve the current draft body, title, destination, proverb, ledger reference, prerequisites and relevant upstream snapshot before review. Bind acknowledgment to that exact revision; any change invalidates the acknowledgment. Export the reviewed body and revision identifier in a receipt.\n\nTrack review, copying, reported publication and independently checked publication separately. A supplied publication URL is reported evidence until checked against the exact repository, target thread and comment anchor. Preserve immutable approval snapshots; do not reconstruct an absent historical snapshot from today's ledger.\n\nVerify generated specification prose by regenerating and comparing the actual marked sections as well as the source digest. Retain successful per-repository watermarks when a refresh fails. Test changed content, changed destination, incorrect publication URLs and historical snapshot stability.\n\nAn acknowledgment means the person reviewed this version. It does not establish comprehension, a bilateral MyTerms agreement, credential issuance or permission to publish. Read the installed DTG reader's board/review.test.mjs and conformance/test.mjs before adapting its contract; implementation paths vary by checkout.\n\nRelated: [Consent infrastructure](../agentprivacy-consent-infrastructure/SKILL.md), [Policy governance](../agentprivacy-policy-governance/SKILL.md).\n\n\n## Related operating practices\n\n\n\n[[City and Star Skills]]"
      },
      "date": 1788831114845
    }
  ],
  "cityStarDigest": "f2b1fbeaf54c72a5a1409523609751c1183184ce414df25f9ca2688824e93c35",
  "cityStarSource": {
    "path": "role/agentprivacy-review-receipts/SKILL.md",
    "sha256": "aab60393b69381d7a4fd1f1cabf0b19915c4aec9c58793fb210743ee8a772fd2"
  }
}