Every technology revolution creates a new shareable artifact — and the artifact always appears before the institution that organizes it. Trace the line from the binary to the context bundle, then watch where it points next.
Tim O'Reilly's essay is a history lesson aimed at the future: every technology revolution creates new knowledge artifacts — binaries, source repos, web pages, clicks — and the artifact precedes the institutions that organize it. His bet is that the AI economy's artifact is the context bundle, and that the mechanisms for sharing, trusting and paying for it are still unbuilt.
This essay reads that bet forward. Linked Open Agentic Commerce (LOAC) — demonstrated live on the URIBurner weblog — is exactly the missing mechanism: hyperlinks as identifiers, WebID identity with on-behalf-of delegation, RDF-ABAC enforcement, and decoupled orchestration vs settlement. Where O'Reilly asks “what comes next?”, LOAC is the answer being built.
Both see the same future from opposite ends. O'Reilly names the artifact and asks for its institutions; LOAC supplies the institution — the hyperlink — and turns the artifact into a governed, payable resource. The agent trace becomes the new click, and the grade receipt becomes the license.
O'Reilly's answer: the context bundle — the artifact you hand the model to do its work. It is not one thing but several, and each one is already becoming a shareable, tradeable unit. Hover any species to see how LOAC packages it.
Hover or tap a species to see what it is — and how LOAC makes it tradeable.
O'Reilly: “The challenge for the software development community is to identify the new knowledge artifacts of the AI economy, and to build new mechanisms and incentives for sharing them.” What will be the derivatives of the AI era? This essay answers: the artifact is the context bundle, the institution is the hyperlink, and the derivative is the license.
Kevin Kelly, answering O'Reilly's Foo Camp question, observes that the magic genie makes creation abundant — so difference becomes the scarce, valuable thing. What gets shared is the specification, the goal: like a seed, it grows differently in different soil.
The value is in the goal, not the prompts — a consultation that each genie grows into its own prompts and actions.
The new artifacts succeed only if they carry distinctions in a standardized way — the way 26 identical letters carry every distinct thing ever written.
A prompt, a bundle, a spec, weights, or an action — standardized, and carrying provenance so a genie can tell if it is good, safe, and from whom it claims.
Kelly says the artifact must be standardized to carry difference; LOAC supplies the alphabet — the dereferenceable offer, the hyperlink identifier, the RDF-ABAC license. That standardization is what makes difference valuable, and it is what the next unit of knowledge is built on.
Each bridge maps an observation or open question in O'Reilly's and Kelly's essays onto the LOAC mechanism that fulfills it — the question on the left, the answer on the right. Table on wide screens; entity cards on narrow screens.
| Bridge | Tim O'Reilly & Kevin Kelly frame the question | LOAC — what comes next |
|---|---|---|
| Code is displaced; the context bundle becomes the tradeable artifact | For a growing number of use cases source code is no longer the most important shareable artifact. | The context bundle — a skill, spec, prompt library, dataset, or knowledge graph — is packaged as a dereferenceable offer an agent can acquire. |
| "We haven't figured out what needs to be shared" | "Part of the problem is that we haven't yet figured out what needs to be shared." | The offer is the unit of sharing — a machine-readable offer with price, license and access rules. |
| Artifacts precede institutions | New artifacts appear before the institutions that organize them (GitHub a decade after open source; Google a decade after websites). | The hyperlink is the coordinating institution: discovery starts at a well-known endpoint, and the graph is its own directory. |
| Trust mechanisms | Cronon's grain trade needed grading standards and grade receipts to let strangers trust one another. | WebID delegated identity + RDF-ABAC is that trust mechanism; access resolves 401→402→200. The license is the grade receipt. |
| "What will be the derivatives of the AI era?" | Grade receipts begat grain futures; O'Reilly asks what the AI era's derivatives will be. | The license separates the right to access from the artifact, settled one-time or by subscription, scoped by a Shared Payment Token. |
| The agent trace as raw material | The agent trace could be "the raw material for attribution and payment, much as the click was for advertising." | Because identity is explicit (principal → agent), who did what under whose authority is auditable end-to-end. |
| "Pheromone trails" and the agentic PageRank | Will agents leave "pheromone trails" that strengthen or fade, like links? | The LOAC substrate is that graph — hyperlinks are identifiers and traversal, leaving exactly the weighted trail a ranker reads. |
| "Anchor on Canonical Names" | A canonical name references a whole methodology more reliably than a paraphrase. | A canonical name is a dereferenceable IRI resolving to the entity's machine-readable description. |
| Protecting the eval holdout set | Nick Vincent warns evals only work if the model hasn't seen the answers. | An eval is an ABAC-gated resource — licensed and gated rather than leaked into training data. |
| A "home for personal context" | O'Reilly follows Duncan Davidson's home for personal context. | The LOAC posts run on exactly such a store — an RDF agent memory whose entities are hyperlink-identified, queryable, licensable. |
| The book is the ultimate knowledge artifact — it becomes a living knowledge graph | O'Reilly's law says every artifact unbundles — binary, source repo, page, click, context bundle. The book is the longest-lived artifact of all, so it is next. | Kingsley's 'Future of Books' article: the book becomes a living, queryable knowledge graph — sold chapter, section, or paragraph at a time as addressable, verifiable units; pay per query or extracted claim. |
| The spec is the new unit — standardization makes difference valuable | Kevin Kelly answers O'Reilly's Foo Camp question: the magic genie makes creation abundant, so difference becomes the scarcity. What gets shared is the specification — the goal, like a seed that grows differently in different soil. | LOAC is that standardization: the dereferenceable offer, the hyperlink identifier, the RDF-ABAC license — the 26 letters that let every distinct, valuable artifact be captured and traded. |
The flywheel is the loop that makes a knowledge artifact discoverable, payable, and reusable — hover a stage to see what happens there. The four URIBurner weblog posts below it demonstrate the loop running live.
An agent dereferences a well-known entry point (.well-known/acp.json) to learn capabilities, entry points and workflows — nothing hard-coded, everything discoverable.
Nodes are entities (principal, agent, offer, license, resource); edges are typed relationships. The agent walks Principal → Agent → Offer → License → Resource.
A purchase generates an RDF policy binding identity, license terms and constraints — access resolves 401 → 402 → 200.
O'Reilly says the new artifacts are “only half-formed” and the institutions “unbuilt.” The URIBurner posts show the mechanism working today — one URI with four outcomes, delegated on-behalf-of commerce, and x402-settled machine payments.
Live demonstrations, not speculation — each a protected, hyperlink-identified resource published on the URIBurner weblog.
A single protected HTML resource resolves four ways depending on the caller's WebID and delegated authority — no browser login UI.
The same gated resource, probed by four callers, demonstrates RDF-ABAC enforcement.
A storyboard of how a principal delegates authority to an agent over ACP & UCP.
A meshup of a16z's intelligence-network thesis with LOAC and x402 machine micropayments.
O'Reilly's law ends at the context bundle; Kingsley's The Future of Books in the Age of AI names the longest-lived artifact of all as next. The book won't become a PDF, an ePub, or a hyperlinked page — it becomes a living knowledge graph.
Sell a chapter, a section, even a single paragraph — as an addressable, verifiable unit of knowledge, not a 300-page monolith.
Readers don't read start-to-finish; they query it, remix it, and link it to other graphs — and pay only for what they use.
Long-form writing becomes curated, versioned, forkable graph branches — with cryptographically provable attribution and mathematically detectable plagiarism.
Each paragraph is an offer; each claim is a license; each read is a micro-transaction. That is granular monetization of personal knowledge — the book surviving as a live service on the Agentic Web, exactly where O'Reilly's context bundles and LOAC's offers converge.
Six steps turn O'Reilly's context bundles into governed, payable linked-open artifacts.
Curate data, information, or knowledge — a spec, a skill, a prompt library, a dataset, or a knowledge graph — into a well-formed context bundle worth sharing.
Describe the artifact as an offer entity with a dereferenceable IRI, a price, and license terms.
Advertise capabilities at a well-known URI (e.g. .well-known/acp.json) so agents can discover the offer without prior API knowledge.
Represent the principal-agent relationship on-behalf-of, using a WebID-identified principal.
Let ACP/UCP handle discovery, negotiation, and ordering, and MPP/x402 (e.g. Stripe) handle payment and settlement.
Materialize an RDF-ABAC policy from the license so access resolves 401 → 402 → 200; rinse and repeat per curated artifact.
A unit of value that can be shared, traded, and built upon; each technology revolution creates new ones.
The artifacts handed to a model to do its work — prompts, specs, agent skills, MCP servers, traces, evals, and conjectures.
A folder of instructions, scripts, and reference material an agent loads only when a task calls for it.
A Model Context Protocol server — a mechanism for presenting context that shapes an LLM's work.
The record of what an agent tried and which context it drew on — commit history for unformalized work.
A set of test cases encoding what good work looks like for a task — valuable to create, withhold, or share.
The Chicago grain trade's artifact that certified quality and separated ownership of grain from the grain itself.
Dereferenceable hyperlinks as stable identifiers — "the hyperlink is the API."
Kingsley Idehen's extension of the medallion architecture: hyperlinks as standardized identifiers.
Commerce as a linked-data entity-relationship graph; pronounced "lock."
The explicit principal-agent relationship and the scope of delegated authority.
Access control expressed as RDF policy; access derives from the graph.
LOAC's separation of ACP/UCP (ordering) from MPP/x402 (payment).
A scoped, time-bounded, cryptographically bound payment authorization.
The machine-readable unit of sharing in LOAC — price, license, and access terms.
A policy entity governing access — the ABAC-enforced grade receipt.
A queryable, versioned, forkable graph that replaces the static document — the format the book becomes.
Selling chapters, sections, or paragraphs as addressable, verifiable units — pay per query or extracted claim.
The book as a queryable service — readers query, remix, and link it to other graphs rather than reading start-to-finish.
The specification — the goal — is the shareable unit; the value is in getting the question right, and like a seed the spec grows differently in different soil.
Standardized units — like 26 letters and a shared dictionary — let distinct, valuable differences be captured and traded.
The standardized package passed between agents — a prompt, a bundle, a spec, weights, or an action — carrying provenance so a genie can tell whether it is good, safe, and from whom it claims.
Drag to pin nodes, double-click to unpin, click a node or edge to open its RDF description via URIBurner. Click the graph surface to arm zoom; click outside to release.
Query the companion knowledge graph live on URIBurner. Select a recipe, edit, and run.
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT ?type (SAMPLE(?s) AS ?sampleEntity) (SAMPLE(?label) AS ?sampleLabel) (COUNT(?s) AS ?entityCount)
WHERE {
GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/oreilly-new-knowledge-artifacts-loac-meshup-deepseek_v4pro-1.ttl> {
?s rdf:type ?type .
OPTIONAL { ?s rdfs:label ?label }
}
}
GROUP BY ?type
ORDER BY DESC(?entityCount)PREFIX schema: <http://schema.org/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
SELECT ?sourceIri ?title ?date ?author
WHERE {
GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/oreilly-new-knowledge-artifacts-loac-meshup-deepseek_v4pro-1.ttl> {
?sourceIri a ?type .
VALUES ?type { schema:NewsArticle schema:BlogPosting }
?sourceIri schema:name ?title .
OPTIONAL { ?sourceIri schema:datePublished ?date }
OPTIONAL { ?sourceIri schema:author ?author }
}
}
ORDER BY ?datePREFIX : <https://oreillyradar.substack.com/p/the-new-knowledge-artifacts-of-the#>
PREFIX schema: <http://schema.org/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
SELECT ?bridgeIri ?name ?about
WHERE {
GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/oreilly-new-knowledge-artifacts-loac-meshup-deepseek_v4pro-1.ttl> {
?bridgeIri a :MeshBridge ;
schema:name ?name .
OPTIONAL { ?bridgeIri schema:about ?about }
}
}
ORDER BY ?bridgeIriPREFIX schema: <http://schema.org/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
SELECT ?personIri ?name ?jobTitle
WHERE {
GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/oreilly-new-knowledge-artifacts-loac-meshup-deepseek_v4pro-1.ttl> {
?personIri a schema:Person ;
schema:name ?name .
OPTIONAL { ?personIri schema:jobTitle ?jobTitle }
}
}
ORDER BY ?namePREFIX schema: <http://schema.org/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
SELECT ?termIri ?term
WHERE {
GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/oreilly-new-knowledge-artifacts-loac-meshup-deepseek_v4pro-1.ttl> {
?termIri a schema:DefinedTerm ;
schema:name ?term .
}
}
ORDER BY ?termPREFIX schema: <http://schema.org/>
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
SELECT ?stepIri ?position ?stepName
WHERE {
GRAPH <https://linkeddata.uriburner.com/DAV/demos/daas/oreilly-new-knowledge-artifacts-loac-meshup-deepseek_v4pro-1.ttl> {
?stepIri a schema:HowToStep ;
schema:position ?position ;
schema:name ?stepName .
}
}
ORDER BY ?position