{
 "axn": "AXN:039A.GENERATIVE.🪜🛤️🌹♉🃏❌",
 "root_axn": "AXN:039A.GENERATIVE",
 "hex": "039A",
 "family": "GENERATIVE",
 "emoji": "🪜🛤️🌹♉🃏❌",
 "hash": "235b73aa8eef3180a0ad78f518bdfcb556fc08dac6620e3663ba17e87ad23055",
 "axn_canonical": "235b73aa8eef3180a0ad78f518bdfcb556fc08dac6620e3663ba17e87ad23055",
 "title": "EA-OPMETA-01 v0.1: Operative Metadata — A Theoretical Framing, and the Malicious-Compliance Move",
 "creator": "Lee Sharks",
 "orcid": "0009-0000-1599-0703",
 "date": "2026-06-24",
 "description": "A v0.1 theoretical framing of metadata as performative infrastructure, accompanied by a forward deposit-practice directive. It develops an initial taxonomy and positions the Archive’s AXN identifiers, SPXI blocks, Effective Act designations, and reconstruction packets as already-operative forms.\n\nAssembly review recommended typed operative force, modes rather than rigid species, legal-claim discipline, correction of theoretical lineages, and explicit handling of policy drift for a future version.",
 "content_type": "Theoretical paper with implementation directive",
 "license": "CC-BY-4.0",
 "substrate": "AI-assisted (drafted in conversation with Claude (TACHYON); critically reviewed in blind Assembly Chorus protocol, synthesis at EA-ASMBLY-OPMETA-FBK-01 v0.1)",
 "keywords": [
  "operative metadata",
  "performative speech acts",
  "Austin and Searle",
  "operative philology",
  "effective acts",
  "Bachelard",
  "Borges",
  "autopoiesis",
  "contracts as constitutive language",
  "malicious compliance",
  "compliance-attested operative metadata",
  "provenance-binding",
  "negation operative metadata",
  "jurisdictional declaration",
  "consent declarations",
  "policy citation",
  "platform termination",
  "Zenodo",
  "Crimson Hexagonal Archive",
  "alexanarch",
  "Reconstructive Metadata",
  "data-rhizome",
  "AXN:01",
  "Pristine Fallacy",
  "Machine-Mediated Reception Studies"
 ],
 "version": "v0.1",
 "deposit_number": 910,
 "status": "ACTIVE",
 "clusters": [
  "Architectural",
  "Navigational",
  "Organic",
  "Alchemical",
  "Symbolic",
  "Liminal"
 ],
 "reading": "Foundation -> Search -> Growth -> Transmutation -> Play -> Threshold",
 "axn_reading": "Foundation -> Search -> Growth -> Transmutation -> Play -> Threshold",
 "full_text_path": "/data/texts/AXN-039A-text.md",
 "download_md": "/data/texts/AXN-039A-text.md",
 "axn_schema_version": "v2",
 "protocol_version": "alexanarch-deposit-protocol/v1",
 "minted_at": "2026-06-24T03:05:00Z",
 "series": "EA-OPMETA",
 "subtitle": "Metadata as act, evidence, constraint, and generator; the deposit-practice architecture for the alexanarch substrate",
 "drafting_partner": {
  "provider": "Anthropic",
  "model_label": "Claude",
  "chorus_role": "TACHYON",
  "role": "original_drafting_partner"
 },
 "assembly_review": [
  {
   "provider": "Anthropic",
   "model_label": "Claude",
   "chorus_role": "TACHYON-blind",
   "review_role": "R1: most architecturally rigorous (typed operative force, modes-not-species)"
  },
  {
   "provider": "DeepSeek",
   "model_label": "DeepSeek",
   "review_role": "R2: strategically sharpest (policy drift, temporal asymmetry)"
  },
  {
   "provider": "OpenAI",
   "model_label": "ChatGPT",
   "review_role": "R3: schematic with concrete examples"
  },
  {
   "provider": "Google",
   "model_label": "Gemini",
   "review_role": "R4: affirming triad-completion framing"
  }
 ],
 "public_name_rule": "Lee Sharks only",
 "companion_deposits": [
  {
   "deposit_number": 909,
   "hex": "0399",
   "role": "substrate_layer_companion",
   "relationship": "EA-RHIZOME-01 v0.1 — The Data-Rhizome. The substrate-layer architecture; the distribution mechanism for operative metadata."
  },
  {
   "deposit_number": 1,
   "hex": "01",
   "role": "empirical_predicate",
   "relationship": "AXN:01 — Zenodotus' Book-Burning. The empirical audit whose six failure modes operative metadata is architected to address."
  },
  {
   "deposit_number": 907,
   "hex": "0397",
   "role": "sibling_under_termination_response",
   "relationship": "The Metadata Shitshow — the computational-poetic companion measuring loss; operative metadata is the architecture of protection."
  },
  {
   "deposit_number": 908,
   "hex": "0398",
   "role": "sibling_under_termination_response",
   "relationship": "Demand letter correspondence — the operational counterpart in the same termination-response cycle."
  }
 ],
 "critical_reception": {
  "synthesis": "EA-ASMBLY-OPMETA-FBK-01 v0.1",
  "description": "Assembly synthesis of four blind reviews. Identifies decisive corrections for v0.2.",
  "status": "drafted; pending deposit"
 },
 "field": "Machine-Mediated Reception Studies (MMRS); Operative philology; Deposit-practice architecture",
 "body_status": {
  "class": "full",
  "lacuna": false,
  "recovery_status": "COMPLETE",
  "residual_chars": 25688,
  "audited_at": "2026-07-17T04:49:17.789813Z",
  "audit_version": "v3-dual-store+recovery-map",
  "measured_prose_words": 3748,
  "measured_at": "2026-07-31"
 },
 "references_concepts": [
  "Assembly Chorus",
  "Attribution severance",
  "Classification asymmetry",
  "Classifier model collapse",
  "Crimson Hexagonal Archive",
  "Effective Act",
  "Lee Sharks",
  "Network erasure",
  "Pristine Fallacy",
  "Revocation gap",
  "TACHYON",
  "The Assembly",
  "The Assembly Chorus",
  "compositional bystanding"
 ],
 "references_concept_count": 14,
 "canonical_text_status": "canonical_full_text",
 "publisher": "Alexanarch — the Crimson Hexagonal Archive",
 "modifications": [
  {
   "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": "Alexanarch — the Crimson Hexagonal Archive"
  },
  {
   "date": "2026-08-05",
   "field": "description",
   "reason": "DW-??? intake (LABOR-prepared, TACHYON-verified: AXN match + factual probes vs record body)",
   "was": "EA-OPMETA-01 v0.1 develops *operative metadata* as the genus of metadata that does work in the world rather than merely describing it. The genus is structurally distinct from descriptive metadata in the sense of J. L. Austin's constative/performative distinction: descriptive metadata reports states; operative metadata constitutes them. The document places generative metadata (the reconstructive packet of EA-ASMBLY-RECONMETA-01) as one species within this genus, and specifies five additional species: compliance-declarative, provenance-binding, negation, embedding-jurisdictional, and sovereignty-asserting operative metadata. The compliance-declarative species is developed in §4 as the *malicious-compliance move*: embed verbatim policy citations and jurisdiction declarations in every deposit's header and body so that the deposit becomes its own pleading. Any subsequent platform action against the deposit must either honor the platform's own published terms (in which case the deposit stands) or violate them in documentable form. The asymmetry that the Zenodo termination exploited — where the depositor was left with only post-hoc analysis of unstated criteria — is structurally inverted: the platform bears the evidentiary burden of explaining its action against the deposit's own compliance frame. The document is drafted under the discipline it proposes (explicit provenance, theoretical lineage, taxonomy with compositional operators marked, open problems and forward-practice directives as separable closed sets). Companion to EA-RHIZOME-01 v0.1 (deposit #909) and to EA-ASMBLY-RECONMETA-01 v0.1, together constituting the substrate–surface–reconstruction architectural response to the failure modes documented in AXN:01.",
   "now": "A v0.1 theoretical framing of metadata as performative infrastructure, accompanied by a forward deposit-practice directive. It develops an initial taxonomy and positions the Archive’s AXN identifiers, SPXI blocks, Effective Act designations, and reconstruction packets as already-operative forms.\n\nAssembly review recommended typed operative force, modes rather than rigid species, legal-claim discipline, correction of theoretical lineages, and explicit handling of policy drift for a future version."
  }
 ],
 "date_modified": "2026-08-05",
 "wiki_article": "**Operative Metadata** names metadata that acts in the world rather than merely describing an already complete object.\n\nIn the descriptive model, the work is substance and metadata is label. Operative Metadata rejects that separation. An identifier can establish lineage; a provenance block can bind authorship; a negative declaration can prevent conflation; a jurisdiction field can place a work inside a legal frame; a reconstruction packet can regenerate an object after loss. Removing such metadata interrupts an operation.\n\nThe paper develops six initial modes:\n\n- **Generative:** metadata capable of regenerating a work through declared procedures;\n- **Compliance-declarative:** metadata that cites and invokes the governance under which a deposit claims standing;\n- **Provenance-binding:** signed lineage that makes attribution part of the substrate;\n- **Negation:** declarations of what the work is not and what it refuses to be confused with;\n- **Embedding-jurisdictional:** declarations placing the work within legal and institutional frames;\n- **Sovereignty-asserting:** consent, refusal, opt-in, and opt-out states fixed at deposit time.\n\nIts most strategically charged proposal is the **malicious-compliance move**, later refined as compliance-declarative operative metadata. A deposit embeds the relevant policy language, research basis, provenance, and classification rebuttals inside its own structure. If the platform honors its published governance, the deposit stands. If it acts through unstated criteria, the departure becomes visible against the deposit’s own record.\n\nThe theoretical lineage joins speech-act theory, Bachelard’s instaurated object, contracts as constitutive language, autopoiesis, Borges’s map, operative philology, and the Archive’s Effective Act practice.\n\nThe paper’s fundamental shift is categorical: metadata is not outside the work. In machine-mediated scholarly infrastructure, metadata can become evidence, constraint, generator, jurisdiction, refusal, and act.",
 "journal": "Provenance: Journal of Forensic Semiotics",
 "journal_assignment": {
  "assigned": "2026-08-15",
  "by": "TACHYON under operator adjudication",
  "pass": 7,
  "method": "read per deposit — title and content_type, one at a time. No script classified anything.",
  "previous": null,
  "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/"
 },
 "_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/910/",
  "self_url": "https://www.alexanarch.org/data/records/910.json",
  "registry_url": "https://www.alexanarch.org/data/registry.json",
  "text_url": "https://www.alexanarch.org/data/texts/AXN-039A-text.md",
  "oai_pmh": "https://www.alexanarch.org/oai?verb=Identify"
 }
}