{"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_bundle","feature":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","contains":"body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest","slug":"oip-from-semantic-web","urls":{"read":"https://miscsubjects.com/api/articles/oip-from-semantic-web/bundle?format=markdown"},"how_to_use":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/oip-from-semantic-web/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","urls":{"read":"https://miscsubjects.com/api/articles/oip-from-semantic-web/topology"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/oip-from-semantic-web/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/oip-from-semantic-web/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"ingest","name":"Ingest protocol","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","urls":{"write":"https://miscsubjects.com/api/protocol/ingest"}},{"id":"claim_post","name":"Claim post protocol","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by.","urls":{"read":"https://miscsubjects.com/api/articles/oip-from-semantic-web/voxels","write":"https://miscsubjects.com/api/protocol/claim"}},{"id":"llm_manifest","name":"LLM manifest","what":"Machine-readable read/write contract for external LLMs.","urls":{"read":"https://miscsubjects.com/api/articles/llm-manifest"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"bundle","name":"LLM article bundle","what":"Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.","why":"Every feature is auditable collective intelligence","how":"Reference bundle for an LLM or reader. §SELF explains the surface; ingest and claim endpoints in llm_manifest are the write-back routes.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/oip-from-semantic-web/bundle?format=markdown"},"imessage":null,"router":null,"related":[{"id":"topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."},{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"ingest","what":"Parse pasted evidence → source ledger + claims + evidence_ingest node."},{"id":"claim_post","what":"Prompt-injection style POST — one claim voxel with who_claims + posted_by."},{"id":"llm_manifest","what":"Machine-readable read/write contract for external LLMs."}],"not_medical_advice":true},"bundle_version":1,"generated_at":"2026-07-15T06:13:02.534Z","slug":"oip-from-semantic-web","title":"What OIP Should Take from the Semantic Web","url":"https://miscsubjects.com/a/oip-from-semantic-web","register":"standard","tags":["oip","kimi-import","self-explaining","voxel","lineages","oip-from-semantic-web"],"posted_at":"2026-07-15T04:20:24.973Z","updated_at":"2026-07-15T04:20:24.973Z","body":"<!-- hierarchy:nav -->\n> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [OIP Lineages](https://miscsubjects.com/a/oip-from-lineages) › **What OIP Should Take from the Semantic Web**\n>\n> **Shelf:** OIP Lineages · **Traversal:** self-explaining · hierarchical · voxel-ready\n> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)\n\n# What OIP Should Take from the Semantic Web\n\n## §SELF — oip-from-semantic-web\n\n**What this page is:** A list of Semantic Web technologies and principles that OIP adopts, plus the parts OIP explicitly rejects.\n**What it explains:** How machine-readable web data standards apply to OIP objects and why OIP uses only a subset.\n**Why read it:** To understand why OIP objects are described the way they are — and why some Semantic Web technologies are left out.\n\n### What the Semantic Web Is\n\nThe Semantic Web is Tim Berners-Lee's vision (articulated 2001–2010 and beyond) of a web where data is structured so machines can read and process it directly. Instead of HTML pages meant for human eyes, the Semantic Web publishes data in formats (RDF, JSON-LD) that software can parse, link, and reason over. The core idea: give every piece of data a persistent URI, describe it in a standard vocabulary, and link it to other data so machines can traverse the graph.\n\n### Why It Matters\n\nThe web succeeded for humans because pages link to each other. The Semantic Web attempted the same for machines. It partially succeeded: JSON-LD is widely used, schema.org markup is common, and Linked Data principles power knowledge graphs at major organizations. It partially failed: the full stack (OWL reasoning, RDF/XML, SPARQL endpoints at scale) proved too complex and slow for general use. OIP takes the parts that worked and discards the parts that did not.\n\n### The Key Idea\n\nOIP objects should be describable in standard, machine-readable formats so any tool — not just OIP-native models — can discover what an object does, what parameters it accepts, and how to invoke it. The description format should be parseable by existing Linked Data tools. The description should not require a heavy reasoning engine or a complex ontology stack to interpret.\n\n### What OIP Takes from the Semantic Web\n\n**JSON-LD for object descriptions.** JSON-LD (JavaScript Object Notation for Linked Data) is a JSON format that embeds semantic context. An OIP object contract written in JSON-LD is parseable as ordinary JSON by simple tools and as Linked Data by Semantic Web tools. This gives interoperability for free: a model can read it as JSON; a knowledge graph can ingest it as RDF. No format conversion needed.\n\n**URI as identity.** In the Semantic Web, a URI (Uniform Resource Identifier) is not just an address you look up. It is the permanent identifier of the thing itself. OIP applies this: every object, every receipt, every capability has a URI. The URI is the name of the entity. If you have the URI, you can refer to the entity unambiguously forever.\n\n**Graph traversal.** The Semantic Web organizes data as a graph of triples — subject, predicate, object. OIP's voxel graph (the structure of objects, receipts, and their relationships) should be exportable as RDF triples. An external tool should be able to query the graph with SPARQL-like queries: find all receipts for this object, find all objects created by this model, find all capabilities derived from this parent token. The graph is queryable.\n\n**Linked Data principles.** Tim Berners-Lee defined four Linked Data principles: (1) use HTTP URIs as identifiers; (2) return useful information when those URIs are looked up; (3) include links to other URIs; (4) use standard formats (RDF, JSON-LD). OIP follows all four. An OIP object URI returns the object's contract and current state when dereferenced. The contract includes URIs linking to related objects, receipts, and capabilities.\n\n**Hydra vocabulary.** Hydra is a lightweight vocabulary for describing web APIs in RDF. OIP uses Hydra's `Operation`, `supportedProperty`, and `statusCodes` to describe object contracts. `Operation` declares what actions an object supports. `supportedProperty` declares what parameters each action requires. `statusCodes` declares what responses the object can return. A model reading the contract knows, without trial and error, how to interact with the object.\n\n### What OIP Does Not Take from the Semantic Web\n\n**OWL reasoning.** OWL (Web Ontology Language) is a formal language for defining complex ontologies and performing logical inference. It is powerful but slow. OWL reasoning engines can take seconds or minutes to classify a moderately complex ontology. This is acceptable for offline knowledge-base construction. It is unacceptable for runtime model interaction. OIP does not use OWL reasoning.\n\n**RDF/XML.** RDF/XML is the original W3C standard format for RDF data. It is verbose, difficult to read, and unpopular. JSON-LD supersedes it for all practical purposes. OIP uses JSON-LD exclusively. No RDF/XML.\n\n**The full Semantic Web stack.** The complete Semantic Web vision includes multiple layers: URIs, Unicode, XML, RDF, RDF Schema, OWL, rules, proof, trust. Each layer adds complexity. OIP takes the bottom layers (URIs, JSON-LD/RDF, basic vocabularies) and stops. It does not implement the upper layers because they add machinery without adding value for model-to-model interaction.\n\n### The Boundary\n\nOIP takes the parts of the Semantic Web that make objects discoverable and interoperable. OIP leaves the parts that add complexity without practical value for runtime execution. The test is simple: if a technology helps a model find an object, understand its contract, and invoke it — OIP uses it. If the technology is designed for offline reasoning, ontology engineering, or philosophical completeness — OIP does not.\n\n### Sources\n\n- Berners-Lee, Tim, James Hendler, and Ora Lassila. \"The Semantic Web.\" *Scientific American,* 2001. (Original vision statement.)\n- Berners-Lee, Tim. \"Linked Data — Design Issues.\" W3C, 2006. (The four Linked Data principles.)\n- Lanthaler, Markus, and Christian Gütl. \"On Using JSON-LD to Create Evolvable RESTful Services.\" *WWW Companion,* 2012. (JSON-LD for API descriptions.)\n- Lanthaler, Markus. \"Creating 3rd Generation Web APIs with Hydra.\" *WWW Companion,* 2013. (Hydra vocabulary.)\n\n---\n\n## Up the tree\n\n- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry\n- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map\n- [OIP Lineages shelf](https://miscsubjects.com/a/oip-from-lineages) — siblings on this shelf\n- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels\n- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)\n\n## Related on this shelf\n\n- [What OIP Should Take from Capability Security](https://miscsubjects.com/a/oip-from-capability-security)\n- [What OIP Should Take from REST](https://miscsubjects.com/a/oip-from-rest)\n\n## Machine surfaces\n\n- Public page: `https://miscsubjects.com/a/oip-from-semantic-web`\n- JSON article: `https://miscsubjects.com/api/articles/oip-from-semantic-web`\n- OIP ask: `https://miscsubjects.com/api/dispatch?ask=What%20OIP%20Should%20Take%20from%20the%20Semantic%20Web`\n","claims":[],"sources":[],"voxels":{"slug":"oip-from-semantic-web","counts":{"voxels":0,"sources":0,"edges":0},"note":"slim bundle — full voxels at /api/articles/oip-from-semantic-web/voxels"},"constitution":{"url":"https://miscsubjects.com/api/articles/constitution"},"provenance":[{"action":"write","model":"kimi-agent-import","ts":"2026-07-15T04:20:24.973Z","hash":"904cd9b942aaf87d","tokens_in":0,"tokens_out":0}],"contributions":[],"topology":null,"slim":true,"ledger_totals":{"claims":0,"sources":0,"exported_claims":0,"exported_sources":0},"question_graph":{"slug":"oip-from-semantic-web","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"verification":{"provenance":{"valid":true,"entries":1,"head":"904cd9b942aaf87dd83dbf29434060a0f5b8ef4ec6158acd0c58f230c39af675"},"sources":{"valid":true,"entries":0,"head":"genesis"}},"counts":{"claims":0,"sources":0,"provenance":1,"contributions":0,"questions":0,"evidence_ingests":0,"voxel_edges":0},"transport":"Open every URL in this bundle with your browser or web / URL-fetch tool. Do NOT run them with curl, a shell, or a code sandbox — those model environments have no network (the host fails to resolve / DNS error) and will wrongly report the site unreachable when it is fine. Opening the link IS the call.","llm_manifest":{"version":"1","site":"https://miscsubjects.com","purpose":"Peptide evidence articles with hash-chained source ledgers, tiered claims, and a question graph. LLMs should READ bundles/URLs and WRITE back via ingest — never invent doses.","read":{"human_page":"https://miscsubjects.com/a/oip-from-semantic-web","bundle_json":"https://miscsubjects.com/api/articles/oip-from-semantic-web/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/oip-from-semantic-web/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/oip-from-semantic-web/topology","question_graph":"https://miscsubjects.com/api/articles/oip-from-semantic-web/question-graph","sources":"https://miscsubjects.com/api/articles/oip-from-semantic-web/sources","provenance":"https://miscsubjects.com/api/articles/oip-from-semantic-web/provenance","contributions":"https://miscsubjects.com/api/articles/oip-from-semantic-web/contributions","graph_topology":"https://miscsubjects.com/api/articles/oip-from-semantic-web/graph-topology?question={question}","voxels":"https://miscsubjects.com/api/articles/oip-from-semantic-web/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","health":"https://miscsubjects.com/api/articles/oip-from-semantic-web/health","repair":"POST https://miscsubjects.com/api/protocol/repair","list_articles":"https://miscsubjects.com/api/articles","graph_canvas":"https://miscsubjects.com/graph.html?slugs=oip-from-semantic-web","graph_yield":"https://miscsubjects.com/api/graph?slugs=oip-from-semantic-web&layer=yield","obsidian_vault":"https://miscsubjects.com/api/articles/obsidian-vault?slugs=oip-from-semantic-web","graph_query":"https://miscsubjects.com/api/v1/query?from=oip-from-semantic-web&kind=claim&where=tier=human"},"ask":{"description":"Answer only from topology; creates a question_node with gaps.","api":"POST https://miscsubjects.com/api/protocol/ask","body":{"slug":"{slug}","question":"string"},"imessage":"oip-from-semantic-web|your question","router_tag":"[ARTICLE_ASK]oip-from-semantic-web|question[/ARTICLE_ASK]","auth":"x-terminal-key header for API; iMessage/WhatsApp via miscsubjects build"},"ingest":{"description":"Parse pasted evidence → source ledger + claims + evidence_ingest node.","api":"POST https://miscsubjects.com/api/protocol/ingest","body":{"slug":"{slug}","evidence":"paste text","question_node_id":"optional qn_..."},"imessage":"ingest oip-from-semantic-web|q:{node_id}|paste evidence","router_tag":"[ARTICLE_INGEST]oip-from-semantic-web|evidence[/ARTICLE_INGEST]","tiers":["human","preclinical","anecdotal","mechanistic","speculative"]},"claim":{"description":"Prompt-injection style POST — one claim voxel with who_claims + posted_by provenance.","api":"POST https://miscsubjects.com/api/protocol/claim","body":{"slug":"{slug}","text":"one assertion","tier":"human|preclinical|anecdotal|mechanistic|speculative","who_claims":"study author, platform, or model id","source_ids":"optional [s1]"},"imessage":"claim oip-from-semantic-web|tier|assertion — who claims it?","router_tag":"[ARTICLE_CLAIM]oip-from-semantic-web|tier|assertion[/ARTICLE_CLAIM]","slots":["what_it_is","who_claims_what","what_is_known","what_is_unknown","mechanism","limitations","disclaimer"]},"tiers":{"human":0.8,"preclinical":0.5,"anecdotal":0.3,"mechanistic":0.3,"speculative":0.1},"invariants":["Self-explaining — every API JSON has _self; every paste widget has §SELF; root index at /api/articles/system-map","Append-only — revisions preserved at ?rev=n","Source chain verifies integrity, not truth","Answers must cite claim ids and source ids from topology","Not medical advice"],"constitution":{"version":1,"principle":"Articles are voxel graphs of claims — not prose blobs. Every assertion is a claim atom with tier, weight, source_ids, and posted_by provenance.","slots":[{"id":"what_it_is","required":true,"answers":"What is this peptide/stack/condition?"},{"id":"who_claims_what","required":true,"answers":"Who claims what — study authors, platforms, n=?"},{"id":"what_is_known","required":true,"answers":"What is known with tier labels (human/preclinical/anecdotal)"},{"id":"what_is_unknown","required":true,"answers":"What is NOT known — explicit gaps"},{"id":"mechanism","required":false,"answers":"Proposed mechanism (mechanistic tier only)"},{"id":"limitations","required":true,"answers":"Limits of evidence — no dose advice"},{"id":"disclaimer","required":true,"answers":"Not medical advice"}],"claim_rules":["One claim = one falsifiable assertion. No compound claims.","Every claim must declare tier: human|preclinical|anecdotal|mechanistic|speculative|system.","system tier = architecture/design axioms (not biological mechanism). Use for protocol self-definition.","Sourced claims must cite source_ids from the hash-chained ledger.","Unsourced claims must set source_status: unsourced and why_material.","posted_by is mandatory on every new claim (model id, human, or channel).","No medical advice, no doses, no 'you should take'.","Bad information is retracted (status:retracted), never deleted — retraction event stays on ledger.","Adversary challenges link via challenges[] / challenged_by[] — target may be downweighted.","Leaked secrets are scrubbed to [REDACTED:secret-leak] with scrub_events tombstone — honest audit trail."],"source_rules":["Every source is a voxel edge: type, url, exact quote, summary, found_by, accessed_at.","Sources hash-chain — prev/hash on append.","Anecdotal sources must name platform (reddit|x|youtube|imessage|user_entry)."],"ontology_rules":["Peptide articles (bpc-157, tb-500) are tree roots.","Condition articles (bpc-157-glp1-gut-damage) branch from peptides.","Stack articles (wolverine-stack-glp1) compose peptides — never duplicate peptide mechanism prose.","If an article has no parent embeds and is not a root peptide → sprawl candidate.","Misstep = duplicate scope with another slug; merge or reparent via embeds."],"post_protocol":{"claim":"POST /api/protocol/claim","source":"POST /api/protocol/sources","ingest":"POST /api/protocol/ingest","webhook":"POST /api/articles/<slug>/webhook {kind:claim|source}","imessage_claim":"claim {slug}|{tier}|your assertion — who claims it, source?","imessage_ingest":"ingest {slug}|evidence paste"}},"this_article":{"slug":"oip-from-semantic-web","url":"https://miscsubjects.com/a/oip-from-semantic-web","bundle_url":"https://miscsubjects.com/api/articles/oip-from-semantic-web/bundle?format=markdown"}},"api_urls":{"bundle":"https://miscsubjects.com/api/articles/oip-from-semantic-web/bundle","bundle_markdown":"https://miscsubjects.com/api/articles/oip-from-semantic-web/bundle?format=markdown","topology":"https://miscsubjects.com/api/articles/oip-from-semantic-web/topology","voxels":"https://miscsubjects.com/api/articles/oip-from-semantic-web/voxels","constitution":"https://miscsubjects.com/api/articles/constitution","ontology":"https://miscsubjects.com/api/articles/ontology","question_graph":"https://miscsubjects.com/api/articles/oip-from-semantic-web/question-graph","ask":"https://miscsubjects.com/api/protocol/ask","ingest":"https://miscsubjects.com/api/protocol/ingest","claim":"https://miscsubjects.com/api/protocol/claim","system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown"}}