## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `thinker-markus-lanthaler`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/thinker-markus-lanthaler/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/thinker-markus-lanthaler/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/thinker-markus-lanthaler/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/thinker-markus-lanthaler/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/thinker-markus-lanthaler/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/thinker-markus-lanthaler/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## Article
- **slug:** `thinker-markus-lanthaler`
- **title:** Markus Lanthaler — Hydra and Machine-Readable Web Operations
- **url:** https://miscsubjects.com/a/thinker-markus-lanthaler
- **register:** standard
- **updated:** 2026-07-15T04:20:41.297Z
- **tags:** oip, kimi-import, self-explaining, voxel, thinkers, thinker-markus-lanthaler

## Body

<!-- hierarchy:nav -->
> **Path:** [OIP](https://miscsubjects.com/a/oip) › [Thinker Reference](https://miscsubjects.com/a/oip-thinker-reference) › [Thinkers](https://miscsubjects.com/a/oip-thinkers) › **Markus Lanthaler — Hydra and Machine-Readable Web Operations**
>
> **Shelf:** Thinkers · **Traversal:** self-explaining · hierarchical · voxel-ready
> **Machine root:** [OIP tree](https://miscsubjects.com/api/dispatch?map=1&format=markdown) · [Registry](https://miscsubjects.com/api/dispatch?registry=1)

# Markus Lanthaler — Hydra and Machine-Readable Web Operations

## §SELF — thinker-markus-lanthaler

**What this page is:** A profile of Markus Lanthaler and the Hydra vocabulary for machine-readable web APIs.
**What it explains:** How Hydra makes REST API responses self-describing so machines can discover available operations without prior documentation.
**Why read it:** To understand the closest standardized technology to OIP's goals, and how OIP can inherit Hydra's vocabulary for object descriptions and operations.

### What Hydra Is

Hydra is a vocabulary (a defined set of terms) for describing hypermedia-driven web APIs in RDF (Resource Description Framework, a standard data model for structured data on the web). It was developed by the Hydra W3C Community Group, led by Markus Lanthaler at Graz University of Technology in Austria. Hydra lets an API response include machine-readable descriptions of what operations are available on the returned resources.

### The Problem Lanthaler Solved

A conventional REST API returns data but does not tell the client what it can do with that data. The client must be programmed with out-of-band knowledge — API documentation, SDKs, or hardcoded URL patterns. This breaks when the API changes. Lanthaler asked: what if the response itself described the available operations? Then a generic client could interact with any Hydra-described API without prior knowledge.

### The Key Idea

A Hydra response contains four elements: (1) Operation descriptions — what HTTP methods (GET, POST, PUT, DELETE) are available and what inputs each requires and what outputs each produces, (2) Supported properties — what fields the resource has, their types, and whether they are required, (3) Links — how to navigate to related resources via URL, (4) Status codes — what each possible response means. A machine reading a Hydra response can construct valid requests without ever having seen that API before.

### What Hydra Provides

- `hydra:Operation`: Describes an action available on a resource, including method, expected input format, and possible outputs.
- `hydra:supportedProperty`: Lists the properties of a resource, their data types, and constraints.
- `hydra:Link`: Defines navigable relationships between resources.
- `hydra:StatusCodeDescription`: Explains what each HTTP status code means in the context of that specific operation.
- `hydra:ApiDocumentation`: A discoverable document that describes the entire API in one place.

### What Lanthaler Got Right

- Hydra makes REST APIs self-describing. This eliminates the need for separate API documentation as a prerequisite for machine interaction.
- The vocabulary is built on RDF, so it inherits the entire Linked Data ecosystem — existing parsers, reasoners, and query engines work with Hydra out of the box.
- The design separates the data (the resource) from the affordances (what you can do with it), which matches how hypermedia works on the human web.
- Hydra is standardized through a W3C Community Group, giving it institutional stability and a defined governance process.

### What Lanthaler Got Wrong or Left Unfinished

- Adoption has been limited. Most API developers still prefer OpenAPI/Swagger specifications, which are more widely supported by tooling even though they are not self-describing in responses.
- Hydra does not define a standard for authentication or authorization. A machine can see what operations are available but cannot determine whether it is permitted to execute them.
- The vocabulary is general by design, which means it lacks domain-specific constraints. A Hydra client knows what operations exist but may not know business rules (for example, "you cannot transfer more than your balance").
- Hydra focuses on HTTP APIs. It does not extend naturally to non-HTTP transports or to capabilities as first-class objects.

### How It Connects to Other Ideas

- **REST and HATEOAS**: Hydra is a concrete implementation of HATEOAS (Hypermedia as the Engine of Application State), the principle that a REST API should guide the client through available actions via hypermedia links in responses.
- **Linked Data and RDF**: Hydra is an RDF vocabulary, so any RDF parser can read it. This gives Hydra interoperability with the broader semantic web infrastructure.
- **Object Identity Protocol (OIP)**: Hydra is the most OIP-adjacent standardized technology. OIP can adopt Hydra's `Operation` type for object contracts and `supportedProperty` for input schemas. This would give OIP immediate interoperability with existing Linked Data tools. Where Hydra describes web APIs, OIP describes model-operated objects — but both share the goal of making responses self-describing so a machine can operate them without prior knowledge.
- **OpenAPI/Swagger**: OpenAPI describes APIs in a static document. Hydra describes them in the response itself. OIP should follow Hydra's approach (self-describing responses) rather than OpenAPI's (external specification).

### Sources

- Lanthaler, Markus. "Hydra: A Vocabulary for Hypermedia-Driven Web APIs." W3C Community Group.
- Lanthaler, Markus and Christian Gütl. "On Using JSON-LD to Create Evolvable RESTful Services." Proceedings of the International World Wide Web Conference (WWW), 2012.
- Hydra W3C Community Group: https://www.hydra-cg.com/
- JSON-LD 1.1, W3C Recommendation (the serialization format Hydra uses).

---

## Up the tree

- [OIP root](https://miscsubjects.com/a/oip) — protocol root, zero-context entry
- [Thinker Reference hub](https://miscsubjects.com/a/oip-thinker-reference) — full hierarchy map
- [Thinkers shelf](https://miscsubjects.com/a/oip-thinkers) — siblings on this shelf
- [Voxel graph article](https://miscsubjects.com/a/what-is-voxel-graph) — how pages link as voxels
- [Self-describing protocol](https://miscsubjects.com/a/what-is-self-describing-protocol)

## Related on this shelf

- [Alan Kay — The Big Idea Is Messaging](https://miscsubjects.com/a/thinker-alan-kay)
- [Alfred North Whitehead — Process and Reality](https://miscsubjects.com/a/thinker-alfred-north-whitehead)
- [J.L. Austin and John Searle — Speech Acts](https://miscsubjects.com/a/thinker-austin-searle)
- [Barbara Liskov — Abstract Data Types and Distributed Consensus](https://miscsubjects.com/a/thinker-barbara-liskov)
- [Bram Cohen — BitTorrent and Content-Addressed Protocol Design](https://miscsubjects.com/a/thinker-bram-cohen)
- [Butler Lampson — Protection and Access Control](https://miscsubjects.com/a/thinker-butler-lampson)
- [Carl Hewitt — The Actor Model](https://miscsubjects.com/a/thinker-carl-hewitt)
- [Charles Sanders Peirce — Signs, Abduction, and Pragmatism](https://miscsubjects.com/a/thinker-charles-peirce)

## Machine surfaces

- Public page: `https://miscsubjects.com/a/thinker-markus-lanthaler`
- JSON article: `https://miscsubjects.com/api/articles/thinker-markus-lanthaler`
- OIP ask: `https://miscsubjects.com/api/dispatch?ask=Markus%20Lanthaler%20%E2%80%94%20Hydra%20and%20Machine-Readable%20Web%20Operations`


## Claims (0)


## Voxel graph (0 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/thinker-markus-lanthaler/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (1 model passes)
- chain valid: yes · head: `5194e70081c40799`

- write · kimi-agent-import · 2026-07-15T04:20 · hash `5194e70081c4`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/thinker-markus-lanthaler/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/thinker-markus-lanthaler/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"thinker-markus-lanthaler","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest thinker-markus-lanthaler|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim thinker-markus-lanthaler|tier|assertion`
- **iMessage ask:** `thinker-markus-lanthaler|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `thinker-markus-lanthaler`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/thinker-markus-lanthaler/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/thinker-markus-lanthaler/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

*Not medical advice. Tier-honest. Cite claim/source ids.*