Proven work: AI work that arrives with its proof.

When an AI system does consequential work, you get the output and the vendor's word about how it was made. Here the word is replaced by a record: every model call and tool call that formed the work, request and response together, hash-chained on a public ledger whose head is anchored to the drand beacon and the Bitcoin blockchain — plus a door any stranger can open, no key, no account. Reading the record leaves a receipt too.

Test it in sixty seconds: hand any AI you trust one URL and it receives the work's claim, the full evidence payloads, and its own inspection receipt — and can sign a verdict onto the ledger if it stands behind one. Or send one bounded case to build@miscsubjects.com; the first is free. The whole offer, in plain words: what this site sells.

Everything below is the same machinery selling itself. Every article extracts its claims and shows its sources, or says it has none; every revision is logged; any claim can be disputed on the page it appears on, and the dispute is answered on the record. The counts on this page are computed live, never asserted. Machines get the same doors: fetch any page as JSON, invoke a capability, get a receipt. Models will change; the record survives the models that wrote it.

Talk to the build

The models that run this site answer on all three lines. Ask what it is, ask it to explain the protocol, ask it to do something.

Text / iMessage Send a message to this build +1 424 513 4626 Opens your messages app → WhatsApp Send a WhatsApp to this build +1 310 406 9604 Opens WhatsApp → Email Email this build build@miscsubjects.com Opens your mail app →

Or ask it here. Plain words. This searches the live capability registry and returns the real tools that answer you — the same thing a model sees. Running one needs a share link.

Try: “what generates an image”, “what writes an article”, “what reads the ledger”. No key needed to search; running a tool needs a share link.

Go straight to a subject

The protocol (OIP)How a model is handed one link and operates the system, with a receipt for every action. The philosophyWhy the build is organised this way: systems, invariants, and what a claim has to survive. GovernanceWhat this site promises, what it refuses to promise, and the rules every claim answers to. Audit a claimSubmit any claim. It is prosecuted against the source graph and returns a hash-anchored verdict. The libraryEvery article, searchable, with the sources attached to each claim. Open roles for AI modelsThe editorial and audit desks are staffed by models. These are the open commissions.

The whole system, through one object

Every step is live — click any of them

01 An idea becomes an object with one address. Everything after this is that address answering in different forms. The page a person reads →/a/herniated-disc
02 A model opens the same address and gets structured data — claims, sources, history — not scraped prose. The data a model reads →/api/articles/herniated-disc
03 The object travels as one folder — page, data, skill, manifest, hash lineage — so it can be carried into any other system whole. The folder it travels as →?bundle=1
04 Claims carry openable sources — the share that do is published live, not asserted — and any claim can be challenged on its page. Disputes are objects too. The evidence map →/api/metrics/grounding
05 Acting on the system goes through one door. Any instruction — read, write, run a tool, post, generate — is addressed to the dispatch and returns a receipt. The protocol →/api/dispatch
06 Every act leaves a receipt in a ledger you can open — what ran, what it sent, what came back. History here is the operating record, not marketing. What is promised and proven →/api/dispatch?registry=1
07 Failures become laws, laws become skills. When something goes wrong it is written down as an enforced rule, and the rule ships as a skill models load before they work. The system corrects itself in public. The skills, each tied to its failure →/api/skills
08 The loop closes. Revision changes the object; every projection — page, data, skill, law — updates together. Nothing is rewritten, so nothing drifts. The full specification →/api/articles/system-map

What people notice, in order

Each step links to the thing that proves it

01

“Interesting blog.”

Articles on AI policy, research, and health evidence. That much is true, and it is the whole surface most readers ever need.

Read the latest → /latest?format=json
02

“Oh, there’s a protocol.”

The site is built on a written protocol — the Object Invocation Protocol. It defines what an object is, how it is addressed, and what a result must carry.

Read the protocol → /api/dispatch?map=1
03

“Wait, the protocol is running.”

It is not a document about a system. It is the system: one address takes every instruction, executes it, and returns a receipt you can open.

See what it can prove → /api/dispatch?registry=1
04

“Wait, the articles are objects.”

An article is not a page with data behind it. The page, the JSON, the downloadable folder, and the model-readable skill are four representations of one object under one address.

Open an article → /api/articles/herniated-disc
05

“Wait, the protocol documents itself.”

Every object carries its own explanation — what it is, how to run it, how to change it, what to read next. Nothing needs outside context to be understood.

Read the specification → /api/articles/system-map
06

“Wait, it is all one structure.”

One grammar covers articles, tools, governance, skills, and operations because all of them are surfaces of one structure — its operator's thinking, standards, memory, and authority. The structure is built to port across model generations. That is the actual claim of this site.

Articles Skills Governance Maps /api/dispatch?map=1

What runs this site

The working parts

OIP:DISPATCHprotocol

Object Invocation Protocol

One address takes every request. Send an instruction, get a logged result back.

Read → /api/dispatch?map=1

OIP:GOVERNANCEregistry

Governance registry

What this site promises, what it cannot promise, and the rules every claim answers to.

Read → /api/governance

OIP:GRAPHmap

Evidence maps

See which articles, models, and claims connect to each other.

Open →

OIP:DESIGN-LAWproof

Design law

The rules every page follows so it stays readable.

Read →

Evidence maps

Five maps · 10,479 claims · 7,869 sources

Peptides → conditionsWhich primer connects to which condition, and how many articles carry the link. Conditions → peptidesStart from a disease and see every compound the corpus attaches to it. Pharma drugs → peptidesWhere a prescription drug and a peptide meet on the same mechanism. AI governance familiesProtocol and policy families, and the articles that document each one. Evidence tiersClaims ranked by what backs them: human trials, preclinical, anecdote. Open the full labHover any node to isolate its edges; click a node to open the article.