[DealAppSeo]

Weight: MAJOR (r31: product scope). Sean approved this change in chat on 2026-10-24: remove the unshipped kernel from the README and BUILDERS, remove or fix the two packages that don't build, and tag the May branch so nothing is lost. Sean merges.

Why

The README described three things, one of which did not exist: a "six-interface kernel" (@hyperdag/protocol plus six default packages). It was designed in a May sprint and never shipped:

• npm view returns 404 for @hyperdag/protocol and every default package.
• The source sat on feat/modular-kernel-interfaces-2026-05-04 (71 files), never merged.
• packages/protocol and packages/interfaces were never in git; only build output on one machine.
• The "Known broken / not live" table listed these four things, which made a reader ask why they were listed at all.

The two packages that were on main (packages/defaults/hallucination-hal-local, identity-erc8004-viem) were the kernel's defaults. Both declare @hyperdag/interfaces as a dependency, which does not exist; the HAL package's own test file says its build fails on a clean clone. No other repository imports either one (searched the default branches of trustshell, repid-engine, HyperDAG-core, trustrepid and trinity-symphony-shared; other repos not searched). So they are removed, not patched.

What changes

File	Change
README.md	Opens with what is here (BUILDERS.md + the ERC-8004 team's contracts) and that nothing installs from it. Drops the kernel section, the kernel API sample, the Known-broken table and the HAL-parity row. The trust-model and threat-model tables now name where each piece runs (repid-engine, HyperDAG-core) instead of interface names.
README.md Receipts	One agent per row, with the address holding each token. The old table put two agents per row, so 12 agents looked like 6. Re-read with ownerOf on Base Sepolia on 2026-10-24: all 12 answer; 1 at the agent's own address, 3 at one address, 8 at another, matching the 2026-10-05 statement's custodian/deployer counts.
BUILDERS.md, CONTRIBUTING.md, CLAUDE.md, docs/living/GITHUB_ABOUT.md	No kernel. CLAUDE.md records the removal and the archive tag so agents stop describing it.
packages/defaults/	Removed (both packages).
.github/dependabot.yml	Drops the two removed directories.
scripts/check-map.mjs	Drops the read of the removed constants file. The registry addresses stay in BUILDERS.md and packages/contracts/README.md, and the existing map check already fails if BUILDERS stops saying the registries are the ERC-8004 team's and that we do not operate them.
.github/workflows/ci.yml	Two comments that named the removed package.

Nothing is lost: tag archive/modular-kernel-interfaces-2026-05-04 → 3fadb864, the branch tip ("Phase 8 — Smoke test passing, sprint complete"). The branch itself is untouched.

Checks run locally

• npm ci from the lockfile: exit 0 (the lockfile never listed packages/defaults/*; workspaces are packages/*, one level).
• npm run check:builders: VERIFIED (1.8.0 = npm).
• check:map against the four siblings' default branches (exported the way CI's sparse checkout lays them out): VERIFIED. Control: with "we do not operate them" removed from BUILDERS.md it FAILS, then passes again with it restored.
• check:sdk-claims: VERIFIED.
• Not run locally: the ERC-8004 contract suites (untouched by this PR; CI reports them, non-gating).

Not in this PR

• @hyperdag/trustshell-mcp on npm is 1.0.0 from 2026-07-08 and older than the trustshell-mcp bin inside @hyperdag/trustshell. The README already says to use the bin. Deprecating the old package is an npm action for Sean.
• The repo's GitHub "About" text still reads "Interface kernel + curated defaults…". The proposed replacement is in docs/living/GITHUB_ABOUT.md; changing it is a repo setting.
• packages/circuits/README.md says "In production, this directory would contain actual circuit files." That is a separate question.

🤖 Generated with Claude Code

[strix-security]

Strix Security Review

✅ No open security findings.

PR summary: This PR removes the never-shipped six-interface trust kernel from the documentation and deletes the two unbuildable default packages under `packages/defaults/`, rewriting the README, BUILDERS.md and related docs so the repository is described as a builder's map plus the ERC-8004 registry contracts, with `@​hyperdag/trustshell` as the only installable product. It also updates the README on-chain receipts table to one row per agent with the holding address.

Review summary

Reviewed all 33 changed paths: the README/BUILDERS/CONTRIBUTING/CLAUDE/GITHUB_ABOUT documentation rewrites, the two comment-only edits in .github/workflows/ci.yml, the .github/dependabot.yml directory removal, the 24 deleted files under packages/defaults/, and the six-line deletion in scripts/check-map.mjs.

No security-relevant code path is introduced by this change, and no security control is lost on a reachable path. The deleted packages were never workspace members (root workspaces is packages/*, and the lockfile contains no entries for them), and after this PR no file in the repository imports or references them; their former write-gating helpers therefore have no remaining consumer. The check-map deletion removes only an existence/content assertion on a constants file that this same PR deletes; the invariant it protected — that the ERC-8004 registries are the ERC-4004 project's deployments and not operated here — is still enforced twice in the same script, on the BUILDERS.md mechanism bullet and by the repository-wide scan. Dependabot coverage stays complete: the two remaining manifests (/ and /packages/contracts) are both still listed. Every contract address and external URL in the edited documents is byte-identical before and after, so no signpost value (registry address, npm package, or documentation link) was altered, and the previously misleading npm install @hyperdag/protocol example is removed rather than replaced. check:sdk-claims still finds a live call site in the README, so it does not degrade into a vacuous pass. No hidden characters or instruction-like content were introduced in the markdown. Minor non-security nit outside the diff: the "what to send here" table in CONTRIBUTING.md still says "Kernel", which is now the only stale mention of the removed design.

Ruled out (3)

• Does removing the constants-file assertion from scripts/check-map.mjs drop the only guard that the ERC-8004 registries are described as the ERC-8004 team's and…
  The deleted assertion only checked a file this PR deletes, and the invariant it protected is still enforced twice in the same script — on the BUILDERS.md mechanism bullet and by the repository-wide operated-by scan that walks every text file.
• Does deleting packages/defaults remove write-safety guards (mainnet block, dry-run gate, missing-signer error) that other code depends on?
  Nothing imports or references either package after the change, neither was ever a workspace member or listed in the lockfile, so no reachable code path loses those guards.
• Does dropping two directories from dependabot.yml leave any manifest without dependency or advisory monitoring?
  Only two package.json manifests remain in the repository and both are still covered by the dependabot directories list.

_{Review 1 on this PR · a7b61a1 · requested Oct 24 15:44 UTC when the PR was opened}

---

Reviewed by Strix
_{Re-run review · Configure security review settings}