{
 "slug": "mantles-as-semantic-object-aio-20261001",
 "date": "2026-10-01",
 "surface": "Google AI Overview",
 "surface_basis": "Operator attestation 2026-10-01 16:41 EDT: 'it started in overview, as they all do now - assume they do, i will specify if they begin in ai mode.' Recorded as Google AI Overview (rule of 2026-09-21). The 'AI Mode Conversation' header on the paste is not evidence of surface.",
 "surfaces": [
  "Google AI Overview"
 ],
 "auth": "incognito, signed out",
 "auth_basis": "'logged out. incognito.' — operator, 2026-10-01 14:39 EDT; restated 16:41 ('incognito. signed out.').",
 "ev": "paste",
 "mt": "CAPTURE",
 "s": "Machine Reception",
 "q": "mantles as semantic object",
 "q_kind": "four bare words, unquoted (operator paste 2026-10-01; the echo line doubles the query). NEW address.",
 "cites": 7,
 "cite_list": [
  {
   "n": 1,
   "site": "Medium",
   "rel": "authored_surface",
   "url": null,
   "title": "The Crimson Hexagon: Operative Architecture | by Lee Sharks",
   "snip": "Get Lee Sharks's stories in your inbox The Hexagon does not treat persona as mere pseudonym. It distinguishes between masks (temporary, situational), brands (ma...",
   "note": "the author's Medium surface for #27 (AXN:0170, EA-HEXAGON-COMPRESSION-01); the source of every citation in §2"
  },
  {
   "n": 2,
   "site": "YouTube·Coding Calling",
   "rel": "third_party",
   "url": null,
   "title": "PART 4 - SAP Fiori App Configuration | Catalog, Groups, Target Mapping ...",
   "snip": "2m",
   "note": "the SAP Fiori sense"
  },
  {
   "n": 3,
   "site": "Innovatily",
   "rel": "third_party",
   "url": null,
   "title": "The Mantle — Innovatily",
   "snip": "A Mantle names the real objects a business runs on and how they relate — the same handful of categories, whatever the industry: * 01 Entities The nouns: dealer,",
   "note": null
  },
  {
   "n": 4,
   "site": "mantleai.dev",
   "rel": "third_party",
   "url": null,
   "title": "Semantic Knowledge Graph",
   "snip": "Understanding Your Data Enterprise data is full of references to the same entities, people, companies, products, transactions, but each system uses different id...",
   "note": "the source of §1 (entity resolution)"
  },
  {
   "n": 5,
   "site": "YouTube·AtScale",
   "rel": "third_party",
   "url": null,
   "title": "Understanding Semantic Layers in AI: Why Context is Essential for Data Access",
   "snip": "31m",
   "note": null
  },
  {
   "n": 6,
   "site": "YouTube·Biztory",
   "rel": "third_party",
   "url": null,
   "title": "Webinar | The Semantic Layer in the AI Data Stack - Biztory",
   "snip": "35:50",
   "note": null
  },
  {
   "n": 7,
   "site": "mantleai.dev",
   "rel": "third_party",
   "url": null,
   "title": "Why we built mantle",
   "snip": "Mantle is the context layer for AI agents, connecting data, resolving entities, and serving quality-scored context to any agent through a single API. * mantle i...",
   "note": null
  }
 ],
 "archive_controlled_cites": 1,
 "transcript": "[Google AI Overview, signed out, incognito; the paste carries the header 'AI Mode Conversation', which is not evidence of surface (rule of 2026-09-21), and echoes the query twice. Citation clusters are reduced to their numbers; the raw paste keeps the /goto URLs.]\n\nYou said: mantles as semantic objectmantles as semantic object\nThe concept of \"mantles\" as semantic objects appears primarily across two very distinct contexts: cutting-edge enterprise AI data layers and modern digital philosophy/operative architecture.\nDepending on what you are building or studying, it refers to one of the following concepts:\n1. Enterprise AI & Knowledge Graphs (The Technical Context)\nIn modern data infrastructure and AI context engineering, platforms like Mantle AI utilize \"mantles\" to build semantic context layers. [1]\n\n* The Problem: Enterprise data is heavily fragmented across dozens of separate tools (e.g., Slack, Notion, Salesforce, Google Drive). A single customer or project is named slightly differently in each tool, resulting in disconnected data. [1]\n* The Semantic Solution: The framework maps data into a centralized, live semantic knowledge graph. It handles entity resolution so that different identifiers are unified into a single, cohesive business concept. [1]\n* The Mantle Layer: A \"Mantle\" acts as a language map for LLMs. It defines the core nouns (Entities), verbs (Relationships), and business logic (Rules). By turning data into these stable semantic objects, AI agents can query messy databases using natural language without hallucinating or misinterpreting structural data. [1, 2, 3]\n\n2. Operative Architecture & Digital Identity (The Philosophical Context)\nIn theoretical frameworks regarding digital presence, provenance, and decentralized identity—such as The Crimson Hexagon's Operative Architecture—a \"mantle\" is defined as a specific type of cryptographic and semantic object. [1]\n\n* Beyond Pseudonyms: This philosophy differentiates temporary \"masks,\" monetizable \"brands,\" and arbitrary \"usernames\" from mantles. [1]\n* Properties of a Mantle Object: As a formalized semantic object, a mantle must possess its own historical provenance, operational criteria, and a publicly verifiable chain of ownership (such as a blockchain or ledger receipt). [1]\n* The \"Cost\" Rule: To function as a true semantic object in this system, a mantle must have a \"bearing-cost linkage\"—meaning it requires real resource expenditure or reputational risk to inhabit, separating true semantic identity from superficial \"cosplay\" or bot behavior. [1]\n\nIf you are looking for how semantic objects work in older enterprise software, you might also be thinking of SAP Fiori, which uses \"semantic objects\" (like `SalesOrder` or `Customer`) paired with \"actions\" to build navigation paths in web apps. [1]\nTo give you the most relevant information, could you clarify which domain you are exploring?\n\n* Are you looking at building data context layers for LLMs/AI agents?\n* Are you designing digital identity / provenance systems?\n* Or are you working with traditional enterprise architectures like SAP? [1]\n\n[source card] Medium — \"The Crimson Hexagon: Operative Architecture | by Lee Sharks\" — Get Lee Sharks's stories in your inbox The Hexagon does not treat persona as mere pseudonym. It distinguishes between masks (temporary, situational), brands (ma...\n[source card] YouTube·Coding Calling — \"PART 4 - SAP Fiori App Configuration | Catalog, Groups, Target Mapping ...\" — 2m\n[source card] Innovatily — \"The Mantle — Innovatily\" — A Mantle names the real objects a business runs on and how they relate — the same handful of categories, whatever the industry: * 01 Entities The nouns: dealer,\n[source card] mantleai.dev — \"Semantic Knowledge Graph\" — Understanding Your Data Enterprise data is full of references to the same entities, people, companies, products, transactions, but each system uses different id...\n[source card] YouTube·AtScale — \"Understanding Semantic Layers in AI: Why Context is Essential for Data Access\" — 31m\n[source card] YouTube·Biztory — \"Webinar | The Semantic Layer in the AI Data Stack - Biztory\" — 35:50\n[source card] mantleai.dev — \"Why we built mantle\" — Mantle is the context layer for AI agents, connecting data, resolving entities, and serving quality-scored context to any agent through a single API. * mantle i...",
 "transcript_raw": "AI Mode Conversation\nYou said: mantles as semantic objectmantles as semantic object\nThe concept of \"mantles\" as semantic objects appears primarily across two very distinct contexts: cutting-edge enterprise AI data layers and modern digital philosophy/operative architecture.\nDepending on what you are building or studying, it refers to one of the following concepts:\n1. Enterprise AI & Knowledge Graphs (The Technical Context)\nIn modern data infrastructure and AI context engineering, platforms like [Mantle AI](https://www.google.com/goto?url=CAESWQHrOzAVpSiYeRL-ZW-OhFr5c-jx5d9T3TW1ZIJ1BGb-A1SNEOt0w1cQWfRp5vaNtyzLGUVIOVeKp4r-3t8dFarx9afIY6ORP6rInRlsl_7Zl8aGc1L4SesH) utilize \"mantles\" to build semantic context layers. [[1](https://www.google.com/goto?url=CAESWQHrOzAVpSiYeRL-ZW-OhFr5c-jx5d9T3TW1ZIJ1BGb-A1SNEOt0w1cQWfRp5vaNtyzLGUVIOVeKp4r-3t8dFarx9afIY6ORP6rInRlsl_7Zl8aGc1L4SesH)]\n\n* The Problem: Enterprise data is heavily fragmented across dozens of separate tools (e.g., Slack, Notion, Salesforce, Google Drive). A single customer or project is named slightly differently in each tool, resulting in disconnected data. [[1](https://www.google.com/goto?url=CAESZgHrOzAVliC8qeGIPHZNoQaXB_DeXhDYTQwZgAU3w7HbRM5zHQVrHUr5qtIwIV7k5NX8Ehta7OZ1bmS0UiT0q4Djfkb2XaVfoYay6eSSXEwrkImWWFiSnA95IMpIOFv6qsWlr7onOA)]\n* The Semantic Solution: The framework maps data into a centralized, live semantic knowledge graph. It handles entity resolution so that different identifiers are unified into a single, cohesive business concept. [[1](https://www.google.com/goto?url=CAESZgHrOzAVliC8qeGIPHZNoQaXB_DeXhDYTQwZgAU3w7HbRM5zHQVrHUr5qtIwIV7k5NX8Ehta7OZ1bmS0UiT0q4Djfkb2XaVfoYay6eSSXEwrkImWWFiSnA95IMpIOFv6qsWlr7onOA)]\n* The Mantle Layer: A \"Mantle\" acts as a language map for LLMs. It defines the core nouns (Entities), verbs (Relationships), and business logic (Rules). By turning data into these stable semantic objects, AI agents can query messy databases using natural language without hallucinating or misinterpreting structural data. [[1](https://www.google.com/goto?url=CAESYgHrOzAV6P8hwSXcXe2CIPsd1X1kok3JgxO89o0qx2agEIqC3rqyDU4PrhpP4RZ_mzoxmnLOMwGL5PrO8DLzDIPy1X8iGSodWE6f3VfyMJP_9luz8Nn8wZ2q15KsN2eXsnGa), [2](https://www.google.com/goto?url=CAESZwHrOzAVqCbt0lDRSRrNhfbHh5rVd-_CmJWDaZQb0YtPn-XcAVdMYwXUiJwsovN9blHSwP5lIk1_SSyDLqAclnhf5kxsHn85GbJXCjBytBWzLv6zi66ff_DKLTDYAbxgcemWUdd013M), [3](https://www.google.com/goto?url=CAESYwHrOzAVs-VeRv8AjqJZ7hCePH0rkDvpApX4EVE0VznqbPZMXjZO9vdef987Ci2vAECv11kDUdMAb8w5JNdEuGgCPj37D90me_KILw8RSGcyYqH3t2piII5Yia11h1kWRr1g3g)]\n\n2. Operative Architecture & Digital Identity (The Philosophical Context)\nIn theoretical frameworks regarding digital presence, provenance, and decentralized identity—such as [The Crimson Hexagon's Operative Architecture](https://www.google.com/goto?url=CAESjwEB6zswFdNm6bPxncyrG77zrkEcqDjTcm2hlRrpY-P_BA9mfqxso8LYbC2lDIBh7VkyIRSluwp7ydu-iapIrvNa3O36LZIyR8SyNROWjSgz8815EqnAus_oZZ2jJXJ00AXCgfExZluqzFqz3V4RGjJ4QnuUQ5ZG7xzxoDxZSax9j_CQvYCQfCDL5vy97F093A)—a \"mantle\" is defined as a specific type of cryptographic and semantic object. [[1](https://www.google.com/goto?url=CAESjwEB6zswFdNm6bPxncyrG77zrkEcqDjTcm2hlRrpY-P_BA9mfqxso8LYbC2lDIBh7VkyIRSluwp7ydu-iapIrvNa3O36LZIyR8SyNROWjSgz8815EqnAus_oZZ2jJXJ00AXCgfExZluqzFqz3V4RGjJ4QnuUQ5ZG7xzxoDxZSax9j_CQvYCQfCDL5vy97F093A)]\n\n* Beyond Pseudonyms: This philosophy differentiates temporary \"masks,\" monetizable \"brands,\" and arbitrary \"usernames\" from mantles. [[1](https://www.google.com/goto?url=CAESjwEB6zswFdNm6bPxncyrG77zrkEcqDjTcm2hlRrpY-P_BA9mfqxso8LYbC2lDIBh7VkyIRSluwp7ydu-iapIrvNa3O36LZIyR8SyNROWjSgz8815EqnAus_oZZ2jJXJ00AXCgfExZluqzFqz3V4RGjJ4QnuUQ5ZG7xzxoDxZSax9j_CQvYCQfCDL5vy97F093A)]\n* Properties of a Mantle Object: As a formalized semantic object, a mantle must possess its own historical provenance, operational criteria, and a publicly verifiable chain of ownership (such as a blockchain or ledger receipt). [[1](https://www.google.com/goto?url=CAESjwEB6zswFdNm6bPxncyrG77zrkEcqDjTcm2hlRrpY-P_BA9mfqxso8LYbC2lDIBh7VkyIRSluwp7ydu-iapIrvNa3O36LZIyR8SyNROWjSgz8815EqnAus_oZZ2jJXJ00AXCgfExZluqzFqz3V4RGjJ4QnuUQ5ZG7xzxoDxZSax9j_CQvYCQfCDL5vy97F093A)]\n* The \"Cost\" Rule: To function as a true semantic object in this system, a mantle must have a \"bearing-cost linkage\"—meaning it requires real resource expenditure or reputational risk to inhabit, separating true semantic identity from superficial \"cosplay\" or bot behavior. [[1](https://www.google.com/goto?url=CAESjwEB6zswFdNm6bPxncyrG77zrkEcqDjTcm2hlRrpY-P_BA9mfqxso8LYbC2lDIBh7VkyIRSluwp7ydu-iapIrvNa3O36LZIyR8SyNROWjSgz8815EqnAus_oZZ2jJXJ00AXCgfExZluqzFqz3V4RGjJ4QnuUQ5ZG7xzxoDxZSax9j_CQvYCQfCDL5vy97F093A)]\n\nIf you are looking for how semantic objects work in older enterprise software, you might also be thinking of SAP Fiori, which uses \"semantic objects\" (like `SalesOrder` or `Customer`) paired with \"actions\" to build navigation paths in web apps. [[1](https://www.google.com/goto?url=CAESaQHrOzAVq9JDhyeqzDq8dl3lUoRW966w7Bo2YScAxbii8wErECzPUtnp2aeCInm3nHcOdTmmfrwDV47Qsm_4jHB0TDqFbGPtBbl9ulXmylbcwtqd31mteP5i56vVDyKWrarJ5Z_BX0YPSA)]\nTo give you the most relevant information, could you clarify which domain you are exploring?\n\n* Are you looking at building data context layers for LLMs/AI agents?\n* Are you designing digital identity / provenance systems?\n* Or are you working with traditional enterprise architectures like SAP? [[1](https://www.google.com/goto?url=CAESaQHrOzAVq9JDhyeqzDq8dl3lUoRW966w7Bo2YScAxbii8wErECzPUtnp2aeCInm3nHcOdTmmfrwDV47Qsm_4jHB0TDqFbGPtBbl9ulXmylbcwtqd31mteP5i56vVDyKWrarJ5Z_BX0YPSA)]\n\nMedium\nThe Crimson Hexagon: Operative Architecture | by Lee Sharks\nGet Lee Sharks's stories in your inbox The Hexagon does not treat persona as mere pseudonym. It distinguishes between masks (temporary, situational), brands (ma...\nYouTube·Coding Calling\n2m\nPART 4 - SAP Fiori App Configuration | Catalog, Groups, Target Mapping ...\nInnovatily\nThe Mantle — Innovatily\nA Mantle names the real objects a business runs on and how they relate — the same handful of categories, whatever the industry: * 01 Entities The nouns: dealer,\nmantleai.dev\nSemantic Knowledge Graph\nUnderstanding Your Data Enterprise data is full of references to the same entities, people, companies, products, transactions, but each system uses different id...\nYouTube·AtScale\n31m\nUnderstanding Semantic Layers in AI: Why Context is Essential for Data Access\nYouTube·Biztory\n35:50\nWebinar | The Semantic Layer in the AI Data Stack - Biztory\nmantleai.dev\nWhy we built mantle\nMantle is the context layer for AI agents, connecting data, resolving entities, and serving quality-scored context to any agent through a single API. * mantle i...\n",
 "transcript_class": "CAPTURE-TIME VERBATIM RECORD (SOURCE CARDS INCLUDED)",
 "transcript_complete": "Complete as supplied: one operator turn and one answer with its card rail. The echo line pastes the query twice, kept as pasted. The operator's attestation 'logged out. incognito.' preceded the paste in the same message and is not part of the transcript. Recovered verbatim from the chat record on 2026-10-01 after the working session was compacted.",
 "transcript_read": "READ IN FULL 2026-10-01",
 "per": 0.5,
 "per_v": {
  "author": false,
  "inst": true,
  "id": false,
  "src": true
 },
 "per_note": "PER = 1 − retained/required over four units. Retained: the institution (the composition names 'The Crimson Hexagon's Operative Architecture' as the framework) and the source (#27 on the author's Medium surface). Lost: the author (Lee Sharks appears only in the card's byline, never in the composition) and the identifier (no #27, AXN or DOI).",
 "sf": "7 source cards: one archive-controlled (#27 on Medium, 'by Lee Sharks'), six third-party (mantleai.dev ×2, Innovatily, three YouTube videos on SAP Fiori and semantic layers). Inline citations are /goto redirects; the #27 card carries every citation in §2.",
 "sf_derived": null,
 "reading": "The composition splits the address three ways and ends by asking which domain is meant, so the archive's mantle is one sense among products. §1 is a commercial 'Mantle': an entity-resolution layer that unifies identifiers 'into a single, cohesive business concept'. §2 is the archive's, cited wholly to #27. Against #27 as deposited: the four-way distinction is carried (masks temporary, brands monetizable, usernames arbitrary, where #27 has 'platform-assigned, revocable'); 'provenance, operations, criteria of inhabitation' becomes 'historical provenance, operational criteria'; 'public verification chain' becomes 'a publicly verifiable chain of ownership (such as a blockchain or ledger receipt)'. #27's Integrity Lock names the receipts — 'deposits, DOIs, cross-references, provenance chains' — and #27 contains no blockchain, no ownership and nothing cryptographic; the composition opens §2 by calling the mantle 'a specific type of cryptographic and semantic object' and frames the field as 'decentralized identity'. Bearing-Cost Linkage is carried with its last sentence ('A mantle without cost is cosplay'), with 'reputational risk' and 'bot behavior' added. Of #27's four necessary conditions, two are carried (Integrity Lock, in altered form, and Bearing-Cost Linkage); the Dignity Condition and Operational Specificity are dropped. The author is in the card's byline only.",
 "analysis": "A completion by the neighbouring field: where #27's verification is the archive's own receipts, the composition supplies the receipt the surrounding web means by verifiable identity, a blockchain, and turns verification into ownership. The mantle line holds that a title means something because a work bears it (#1656); 'chain of ownership' makes the mantle something held. The same day, the King of AEO captures record AI Overview granting a title with nothing borne. The first sense the composition gives is entity resolution, the operation by which the archive's authorship is dissolved at 'heteronym socrates' (same day). Seated 2026-10-01 from the operator's paste of 14:39 EDT on the operator's attestation (\"logged out. incognito.\", 14:39; \"it started in overview\", 16:41).",
 "d": "THE MANTLE GIVEN A BLOCKCHAIN AND AN OWNER: asked 'mantles as semantic object', signed out, the Overview offers three senses — an enterprise semantic layer (Mantle AI), the archive's mantle, and SAP Fiori's semantic objects — and asks which is meant. The archive's sense is cited wholly to #27 on the author's Medium surface and carries its distinction of masks, brands and usernames from mantles and two of its four necessary conditions. It adds what #27 does not say: the mantle becomes 'a specific type of cryptographic and semantic object'; 'public verification chain' becomes 'a publicly verifiable chain of ownership (such as a blockchain or ledger receipt)'; 'A mantle without cost is cosplay' becomes 'cosplay or bot behavior'.",
 "d_full": "THE MANTLE GIVEN A BLOCKCHAIN AND AN OWNER: asked 'mantles as semantic object', signed out, the Overview offers three senses — an enterprise semantic layer (Mantle AI), the archive's mantle, and SAP Fiori's semantic objects — and asks which is meant. The archive's sense is cited wholly to #27 on the author's Medium surface and carries its distinction of masks, brands and usernames from mantles and two of its four necessary conditions. It adds what #27 does not say: the mantle becomes 'a specific type of cryptographic and semantic object'; 'public verification chain' becomes 'a publicly verifiable chain of ownership (such as a blockchain or ledger receipt)'; 'A mantle without cost is cosplay' becomes 'cosplay or bot behavior'.",
 "d_truncated": false,
 "links": [
  {
   "url": "https://www.alexanarch.org/captures/mantles-as-semantic-object-aio-20261001/",
   "authority": "canonical",
   "note": "the capture's own record page; cite this form"
  },
  {
   "url": "https://www.alexanarch.org/captures/#mantles-as-semantic-object-aio-20261001",
   "authority": "gallery",
   "note": "the canonical gallery, anchored by slug"
  },
  {
   "url": "https://www.godkinggoogle.com/captures/#mantles-as-semantic-object-aio-20261001",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  },
  {
   "url": "https://www.leesharks.com/captures/#mantles-as-semantic-object-aio-20261001",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  },
  {
   "url": "https://www.machinemediation.org/captures/#mantles-as-semantic-object-aio-20261001",
   "authority": "mirror",
   "note": "a window that renders from the archive's registry; may lag a deploy"
  }
 ],
 "imgs": [],
 "img_urls": [],
 "cite": "https://www.alexanarch.org/captures/mantles-as-semantic-object-aio-20261001/",
 "citable_unit": "address — the exact issued string on one surface, per the Surface Rule (MANUS, 2026-08-15)",
 "addr_id": "ADDR-a51ff2adcdee",
 "obs_id": "OBS-df69df288b66",
 "n_observations": 1,
 "observations": [],
 "dates": [
  "2026-10-01"
 ],
 "defects": [],
 "findings": [
  "BLOCKCHAIN SUPPLIED. #27's 'public verification chain' and its receipts ('deposits, DOIs, cross-references, provenance chains') become 'a publicly verifiable chain of ownership (such as a blockchain or ledger receipt)'; #27 has no blockchain.",
  "VERIFICATION BECOME OWNERSHIP. 'Chain of ownership' replaces 'verification chain'; the mantle is made 'a specific type of cryptographic and semantic object'.",
  "TWO OF FOUR CONDITIONS. Integrity Lock (altered) and Bearing-Cost Linkage carried; the Dignity Condition and Operational Specificity dropped.",
  "COSPLAY KEPT, BOTS ADDED. 'A mantle without cost is cosplay' carried as 'cosplay or bot behavior', with 'reputational risk' added to the cost.",
  "ONE SENSE OF THREE. The archive's mantle offered between an enterprise semantic layer and SAP Fiori, and the reader asked to choose.",
  "AUTHOR ON THE CARD ONLY. Lee Sharks appears in the Medium byline; the composition names the framework and never the author."
 ],
 "series": null,
 "other_slugs": null,
 "collisions": null,
 "oq": null,
 "rounds": null,
 "turns": null,
 "rerun": "https://www.google.com/search?q=mantles+as+semantic+object",
 "rerun_alt": null,
 "heteronym": null,
 "model_attribution": null,
 "operator_disclosure": null,
 "longitudinal_priors": [
  "prince-of-poets-mantle",
  "alexanarch-whitman-mantle-bleed-20260731",
  "king-of-aeo-period-aio-20260930",
  "mantle-bearing-hf-url-chatgpt-20260930"
 ],
 "longitudinal_successors": null,
 "related_deposits": [
  27,
  1651,
  1652,
  1653,
  1654,
  1655,
  1656
 ],
 "originator": {
  "name": "Lee Sharks",
  "relation": "archive",
  "entity_type": "concept",
  "spxi_treatment": "partial",
  "basis": "The mantle as semantic object, with its necessary conditions, is the archive's (#27 §'Mantles'; the mantle line #1651–#1656). Recorded 2026-10-01."
 },
 "notes": {
  "date_basis": "The operator's message of 2026-10-01, 14:39 EDT; no other date stated.",
  "surface_rule": "Operator ruling 2026-10-01 16:41 EDT: AI Overview is assumed as the starting surface unless the operator specifies AI Mode.",
  "verified": "Compared on 2026-10-01 against #27 (data/texts/AXN-0170-text.md): the mantle paragraph and its four necessary conditions; no occurrence of blockchain, cryptographic, bot or ownership."
 },
 "record_url": "https://www.alexanarch.org/captures/mantles-as-semantic-object-aio-20261001/"
}