Most on-chain contracts ship with no docs, stale docs, or docs for a different version. The reading layer writes the manual from the deployed bytecode itself — per exact revision, with observed usage attached. Yours, your dependencies', and the undocumented one you're integrating on a deadline.
The transcript above is real output — the study is the machine's own text, and the reader answering the second query is the same one behind this site's explorer.
642 studies like this already written. 114 are live behind this proof — your coding agent reads them over MCP today, and the rest ship as the store grows.
What does this exact revision actually do?
Show me real transactions that used this function — and one that failed.
What changed between revision N and N+1?
This was the one use case a sophisticated outside buyer proposed unprompted: a CLI and API that coding agents consult, because agents can't read Move calls either. The manual a human reads and the context an agent consumes are the same artifact.
Building on Sui? What's the first package you'd point this at?
bartosz@research.tech