{
 "axn": "AXN:0347.GOVERNANCE.🔆📌🧊∮🕓🌺",
 "root_axn": "AXN:0347.GOVERNANCE",
 "hex": "0347",
 "family": "GOVERNANCE",
 "emoji": "🔆📌🧊∮🕓🌺",
 "hash": "ec461d95657199967d3157e55695dbebcd7580625ee0ff99ac0f3bd92c127cc4",
 "title": "Proposal: optional summarization-governance fields — provenance_kernel, disambiguation, summary_policy",
 "creator": "Lee Sharks",
 "orcid": "0009-0000-1599-0703",
 "date": "2026-06-14",
 "description": "This record preserves a proposal filed to the Google Cloud Open Knowledge Format project asking the format to support optional producer-declared summarization-governance fields. The proposed fields are `provenance_kernel`, `disambiguation`, and `summary_policy`, with an optional human-readable provenance section in the document body.\n\nThe proposal distinguishes three problems that are often collapsed. Descriptive provenance states where knowledge came from. Trust and safety address whether knowledge should be used. Summarization governance states which distinctions, identities, or formulations a producer considers load-bearing when an agent later compresses the knowledge. The proposed fields would let a producer name a preferred attribution kernel, identify nearby entities or meanings that must not be merged, and state required or forbidden summary behaviors.\n\nThe proposal is deliberately non-enforcing. It does not claim that an author may dictate every downstream interpretation or prevent criticism. A consumer or model may ignore the fields. Their value is to create a machine-readable surface where the producer’s declared expectations can be compared with the actual output. This converts a vague fidelity dispute into an observable compliance question.\n\nThe body uses the archive’s capture registry as motivation and argues that structurally clean input formats can still lose author, source, correction, or conceptual boundaries at output. It also argues that governance carried only in metadata may be stripped before generation, making visible body text an important fallback.\n\nThis is a timestamped standards contribution, not part of an adopted OKF specification. Its relation to later issues, maintainer discussion, or implementation must be verified against the repository history. The descriptive article should not imply Google accepted, endorsed, or deployed the fields.",
 "content_type": "Standards proposal / public issue filing",
 "license": "CC-BY-4.0",
 "substrate": "Various",
 "keywords": [
  "summarizationgovernance",
  "data catalog concept",
  "composition layer",
  "crimson hexagonal",
  "provenancekernel",
  "semantic economy",
  "disambiguation",
  "summarypolicy"
 ],
 "version": "v1.0",
 "deposit_number": 829,
 "sovereign_id": "MM-CHA-0835",
 "minted_at": "2026-06-20T22:00:00Z",
 "status": "ACTIVE",
 "clusters": [
  "Liminal",
  "Scriptural",
  "Elemental",
  "Mathematical",
  "Temporal",
  "Organic"
 ],
 "reading": "Threshold → Text → Force → Proof → Duration → Growth",
 "axn_canonical": "ec461d95657199967d3157e55695dbebcd7580625ee0ff99ac0f3bd92c127cc4",
 "axn_display": "🔆📌🧊∮🕓🌺",
 "mirrors": {
  "blog": "https://mindcontrolpoems.blogspot.com/2026/06/proposal-optional-summarization.html"
 },
 "zenodo_dois": [
  "10.5281/zenodo.20691745",
  "10.5281/zenodo.20690868",
  "10.5281/zenodo.20686496"
 ],
 "full_text_path": "/data/texts/AXN-0347-text.md",
 "full_text_chars": 8017,
 "wiki_article": "**Optional Summarization-Governance Fields** is a standards proposal by Lee Sharks for the Open Knowledge Format project.\n\nThe proposal defines three optional fields. A provenance kernel supplies compact attribution; a disambiguation field names entities or senses that must not be merged; and a summary policy identifies distinctions a producer asks downstream systems to preserve.\n\nThe fields are advisory rather than technically binding. Their purpose is to make output fidelity and provenance measurable after an agent consumes a structured knowledge bundle.\n\nThe proposal was filed as a GitHub issue and independently archived. It is not an adopted Google or OKF standard unless later repository records establish adoption.",
 "entities": [],
 "journal": "Machine-Mediated Reception Studies (MMRS)",
 "references_concepts": [
  "Crimson Hexagonal Archive",
  "Google AI Overview",
  "Lee Sharks",
  "Revelation First",
  "Semantic Economy",
  "Semantic Economy Institute"
 ],
 "defines_concepts": [],
 "references_concept_count": 6,
 "external_metadata_path": "/data/external-metadata/AXN-0347.json",
 "openalex_ids": [
  "https://openalex.org/W7164744559",
  "https://openalex.org/W7164757261",
  "https://openalex.org/W7164760601"
 ],
 "datacite_severance": "severed",
 "body_status": {
  "class": "full",
  "lacuna": false,
  "recovery_status": "COMPLETE",
  "residual_chars": 7333,
  "audited_at": "2026-07-17T04:49:17.789813Z",
  "audit_version": "v3-dual-store+recovery-map",
  "measured_prose_words": 971,
  "measured_at": "2026-07-31",
  "work_sha256": "0046d6f75150ced0caca33cd72e2d09e3d5b6a18560226febd478bbf0e64d2f8",
  "prior_bytes_sha256": "cd4cab89a54e9a7d0846b7d0d019b1a64c969494c43f4ae5a7086a49ea4034ce",
  "w13_tier2": "2026-08-04 W13 TIER 2 BYTE UNGLUE: 9 glued heading markers -> 2. WHITESPACE-ONLY transform (content identical under whitespace normalisation, verified before write); code fences exempt; prior sha retained. Re-fetching could not fix this class — the blog source is ITSELF glued (the collapse predates publication), so the deterministic transform applied at display since tier 1 is now applied to the bytes, which also fixes PDFs, the body-index, and downloads.",
  "w13_tier2_correction": "2026-08-05 REGRESSION REPAIRED: the W13 tier-2 byte unglue used a lookbehind that treated the first \"#\" of a legitimate \"###\" heading as the preceding non-newline character, splitting \"### Heading\" into \"#\" + blank + \"## Heading\". My safety check verified content-identity under WHITESPACE normalisation, which the split satisfies — the wrong invariant. Headings rejoined; only \"#\" and whitespace differ from the damaged state, verified before write."
 },
 "title_repair_log": [
  {
   "at": "2026-07-28T14:59:09Z",
   "defect": "truncated_mid_token",
   "was": "Proposal: optional summarization-governance fields — provenance_kernel, disambiguation, summary_policy Filed: 14 June 20",
   "now": "Proposal: optional summarization-governance fields — provenance_kernel, disambiguation, summary_policy",
   "basis": "Recovered from the deposit's own body (JSON-LD name or h1). The registry title was the canonical title followed by a metadata fragment cut mid-token at a character ceiling — the fragment does not end in a complete word, which is what distinguishes it from a subtitle. Confirmed present in body: True."
  }
 ],
 "canonical_text_status": "canonical_full_text",
 "modifications": [
  {
   "date": "2026-08-01",
   "field": "content_type",
   "reason": "Wave 1 repair: audit ledger v1.1 recommended_content_type (workplan v1.5 §6 W1, MANUS batch approval 2026-08-01)",
   "was": "Theoretical paper",
   "now": "Standards proposal / public issue filing"
  },
  {
   "date": "2026-08-01",
   "field": "journal",
   "reason": "Wave 6 venue normalization: full canonical journal name per MANUS ruling 2026-08-01 (venues.json authority)",
   "was": "MMRS",
   "now": "Machine-Mediated Reception Studies (MMRS)"
  },
  {
   "date": "2026-08-04",
   "field": "publisher",
   "reason": "PUB-POPULATE: dc:publisher from venues.json v1.1 press mapping (CP-R3 RULED-EXTENDED 2026-08-01); Alexanarch = publisher of record where no imprint applies",
   "now": "Pergamon Press"
  },
  {
   "date": "2026-08-04",
   "field": "status",
   "reason": "W12 STATUS-VOCABULARY v1.0 (MANUS ratified 2026-08-04): controlled vocabulary {ACTIVE, SUPERSEDED, WITHDRAWN, DRAFT}; MINTED_UNREVIEWED false on a 100%-audited corpus; freetext annotations preserved losslessly in body_status.status_note",
   "was": "MINTED_UNREVIEWED",
   "now": "ACTIVE"
  },
  {
   "date": "2026-08-05",
   "field": "body_status",
   "reason": "W13 TIER 2 byte unglue (whitespace-only, content-identical, code-fence-safe)",
   "was": "{\"class\": \"full\", \"lacuna\": false, \"recovery_status\": \"COMPLETE\", \"residual_chars\": 7333, \"audited_at\": \"2026-07-17T04:49:17.789813Z\", \"audit_version\": \"v3-dual-store+recovery-map\", \"measured_prose_wo",
   "now": "{\"class\": \"full\", \"lacuna\": false, \"recovery_status\": \"COMPLETE\", \"residual_chars\": 7333, \"audited_at\": \"2026-07-17T04:49:17.789813Z\", \"audit_version\": \"v3-dual-store+recovery-map\", \"measured_prose_wo"
  },
  {
   "date": "2026-08-05",
   "field": "body_status",
   "reason": "W13 TIER-2 REGRESSION REPAIRED: split headings rejoined",
   "was": "{\"class\": \"full\", \"lacuna\": false, \"recovery_status\": \"COMPLETE\", \"residual_chars\": 7333, \"audited_at\": \"2026-07-17T04:49:17.789813Z\", \"audit_version\": \"v3-dual-store+recovery-map\", \"measured_prose_wo",
   "now": "{\"class\": \"full\", \"lacuna\": false, \"recovery_status\": \"COMPLETE\", \"residual_chars\": 7333, \"audited_at\": \"2026-07-17T04:49:17.789813Z\", \"audit_version\": \"v3-dual-store+recovery-map\", \"measured_prose_wo"
  },
  {
   "date": "2026-08-05",
   "field": "description",
   "reason": "DW-??? intake (LABOR-prepared, TACHYON-verified: AXN match + factual probes vs record body)",
   "was": ">",
   "now": "This record preserves a proposal filed to the Google Cloud Open Knowledge Format project asking the format to support optional producer-declared summarization-governance fields. The proposed fields are `provenance_kernel`, `disambiguation`, and `summary_policy`, with an optional human-readable provenance section in the document body.\n\nThe proposal distinguishes three problems that are often collapsed. Descriptive provenance states where knowledge came from. Trust and safety address whether knowledge should be used. Summarization governance states which distinctions, identities, or formulations a producer considers load-bearing when an agent later compresses the knowledge. The proposed fields would let a producer name a preferred attribution kernel, identify nearby entities or meanings that must not be merged, and state required or forbidden summary behaviors.\n\nThe proposal is deliberately non-enforcing. It does not claim that an author may dictate every downstream interpretation or prevent criticism. A consumer or model may ignore the fields. Their value is to create a machine-readable surface where the producer’s declared expectations can be compared with the actual output. This converts a vague fidelity dispute into an observable compliance question.\n\nThe body uses the archive’s capture registry as motivation and argues that structurally clean input formats can still lose author, source, correction, or conceptual boundaries at output. It also argues that governance carried only in metadata may be stripped before generation, making visible body text an important fallback.\n\nThis is a timestamped standards contribution, not part of an adopted OKF specification. Its relation to later issues, maintainer discussion, or implementation must be verified against the repository history. The descriptive article should not imply Google accepted, endorsed, or deployed the fields."
  }
 ],
 "date_modified": "2026-08-05",
 "publisher": "Pergamon Press",
 "journal_assignment": {
  "assigned": "2026-08-15",
  "by": "TACHYON under operator adjudication",
  "pass": 6,
  "method": "read per deposit — title and content_type, one at a time. No script classified anything.",
  "previous": "Machine-Mediated Reception Studies (MMRS)",
  "supersedes": "the 2026-06-21 preliminary batch mapping (#866), which assigned 864 deposits and put 371 in one venue",
  "authority": "data/cha-journals.json · datasets/venues/records/"
 },
 "line": "metadata-packets",
 "line_parent": "infrastructure",
 "line_basis": "derived",
 "_projection": {
  "note": "Derived file. Canonical machine record is this entry in data/registry.json; the human record is the record_url. Do not edit this file.",
  "record_url": "https://www.alexanarch.org/s/records/829/",
  "self_url": "https://www.alexanarch.org/data/records/829.json",
  "registry_url": "https://www.alexanarch.org/data/registry.json",
  "text_url": "https://www.alexanarch.org/data/texts/AXN-0347-text.md",
  "oai_pmh": "https://www.alexanarch.org/oai?verb=Identify"
 }
}
