docs: the README sold a kernel that is not on npm and not on main - #12
Merged
Conversation
The front page of a public protocol repo opened with `npm install
@hyperdag/protocol`, a `createHDP` example, a six-interface/six-default table,
links to ARCHITECTURE.md and packages/protocol/README.md, and a row reading
"V1 - Live today ... Six-interface modular kernel · @hyperdag/protocol@0.1.0-alpha
on npm."
Verified against the registry and the branch, not assumed:
npm view @hyperdag/protocol -> 404
npm view @hyperdag/identity-erc8004 -> 404
npm view @hyperdag/reputation-zkp -> 404
npm view @hyperdag/validation-trinity -> 404
npm view @hyperdag/payment-x402 -> 404
npm view @hyperdag/linkage-registry -> 404
npm view @hyperdag/hallucination-hal -> 404
Seven for seven. The kernel source is not on main either - it is on
feat/modular-kernel-interfaces-2026-05-04 - and both linked docs 404 on disk.
packages/protocol and packages/interfaces hold only untracked dist output with
no rebuildable source. So the first command a visiting developer runs fails, and
the two links they follow to understand why are dead.
The underlying work is real: the contracts are live on Base Sepolia, HAL and
x402 are running, and the interface design is settled. What was false was the
PACKAGING - present-tense claims of a shipped, installable artifact.
Rewritten to state what is true and to route a visitor to something that
actually works:
- quick start now installs @hyperdag/trustshell, which IS published, with a
real working call (verifyOutput) instead of an unrunnable createHDP example.
- createHDP retained, explicitly labelled a design target, not a shipped API.
- the six-defaults table gains a status column per row, and names the two
packages that DO exist here (hallucination-hal-local, identity-erc8004-viem),
neither of which is one of the six.
- dead links to ARCHITECTURE.md and packages/protocol/README.md removed; every
remaining relative link in the README now resolves on disk.
- the "Live today" row separates what is live (contracts, HAL, x402, all
reachable via trustshell) from what is branch-only (the kernel).
No claim was softened that was true, and no work was hidden. The vision reads
the same; only the tense changed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The front page of a public protocol repo opened with
npm install @hyperdag/protocol, acreateHDPexample, a six-interface/six-default table, links toARCHITECTURE.mdandpackages/protocol/README.md, and a row reading "V1 — Live today … Six-interface modular kernel ·@hyperdag/protocol@0.1.0-alphaon npm."Verified against the registry, not assumed
Seven for seven. The kernel source is not on
maineither — it's onfeat/modular-kernel-interfaces-2026-05-04— and both linked docs 404 on disk.packages/protocolandpackages/interfaceshold only untrackeddistoutput with no rebuildable source.So the first command a visiting developer runs fails, and the two links they'd follow to understand why are dead.
What was actually wrong
The underlying work is real — contracts live on Base Sepolia, HAL and x402 running, interface design settled. What was false was the packaging: present-tense claims of a shipped, installable artifact.
Rewritten to state what's true and route a visitor to something that works:
@hyperdag/trustshell, which is published, with a real working call (verifyOutput) instead of an unrunnablecreateHDPexamplecreateHDPretained, explicitly labelled a design target, not a shipped APIhallucination-hal-local,identity-erc8004-viem) — neither of which is one of the sixNo claim was softened that was true, and no work was hidden. The vision reads the same; only the tense changed.
🤖 Generated with Claude Code