Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions BUILDERS.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ publish X without touching this file.

| Thing | State | How to check |
|---|---|---|
| **`@hyperdag/trustshell`** | **PUBLISHED — `1.6.0`** (measured 2026-10-05; was `1.4.0` on 2026-10-04). The one package to install. | `npm view @hyperdag/trustshell version` |
| **`@hyperdag/trustshell`** | **PUBLISHED — `1.6.1`** (measured 2026-10-14; was 1.6.0 on 2026-10-05 and 1.4.0 on 2026-10-04). The one package to install. | `npm view @hyperdag/trustshell version` |
| `@hyperdag/protocol` | **NOT published** (404) | `npm view @hyperdag/protocol version` |
| `@hyperdag/identity-erc8004`, `@hyperdag/reputation-zkp` | **NOT published** (404) | same |
| `IdentityRegistry` on Base Sepolia (84532) | **LIVE** — `0x8004A818BFB912233c491871b3d84c89A494BD9e` | any RPC client, or basescan |
Expand All @@ -31,7 +31,7 @@ publish X without touching this file.
npm badge for `@hyperdag/protocol`, a package that does not exist; it misled one of our own
agents on 2026-09-08 and was removed on 2026-10-04.

**Published 1.6.0, measured from the tarball on 2026-10-05.** `trustshell verify`
**Published 1.6.1, re-measured 2026-10-14 (first measured on the 1.6.0 tarball, 2026-10-05).** `trustshell verify`
exits 0 on PASS or FLAG, 1 on VETO, and 2 when HAL did not decide (NOT_CHECKED, never a pass).
Exit 3 is a runtime error and 4 means the command is waiting for a person to answer (ASK).
`ethers` (`^6`) is an optional peer: a plain install does not include it. The package uses it
Expand Down Expand Up @@ -63,8 +63,9 @@ curl -s -X POST https://repid-engine-production.up.railway.app/api/v1/classify \
- **In:** `{text, labels}`. `labels` is optional; if present it must be exactly the three.
- **Out:** `{label, latency_ms, by}`, where `label` is `pass`, `veto` or `not-checked` and `by`
says what decided (`arithmetic`, `votes`, or `skipped` when nothing was sent). When models voted
it also carries `voters` (every host the text reached) and `deciders` (the two whose answers made
the label), and, only when the operator has questions switched on, a `question`. Read `label`;
it also carries `voters` (every host the text reached), `deciders` (the two whose answers made
the label), `votes` (one `{voter, family, verdict}` per host that answered, measured
2026-10-14), and, only when the operator has questions switched on, a `question`. Read `label`;
the other fields are for showing your user who checked.
- **What decides:** a whole-text arithmetic equation is evaluated locally. Prose up to
1,500 characters goes to **two independent free models, which must agree**: both true
Expand Down
4 changes: 2 additions & 2 deletions CLAUDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,8 +61,8 @@ on npm"*. It is **not published** — `npm view @hyperdag/protocol` returns 404,
the top of `README.md` without running the query, while the README's own *"Known broken / not
live"* table three screens below said plainly that it 404s. **A badge is a link, not a
measurement** — same class as reading `-stub` in a filename as evidence about production.
The package an outside builder should install is **`@hyperdag/trustshell`** (`1.6.0` on npm,
MEASURED 2026-10-06; it was 1.3.0 when this line was first written). Two others are published
The package an outside builder should install is **`@hyperdag/trustshell`** (`1.6.1` on npm,
MEASURED 2026-10-14; 1.6.0 on 2026-10-06, 1.3.0 when this line was first written). Two others are published
and are not the entry point: `@hyperdag/proof-verifier` (0.2.0, bundled inside trustshell) and
`@hyperdag/trustshell-mcp` (1.0.0 from 2026-07-08, older than the `trustshell-mcp` bin that
ships inside trustshell itself). See `BUILDERS.md`.
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The stranger-facing product is [`@hyperdag/trustshell`](https://github.com/DealA
1. Fork. Branch from `main`.
2. Tests for code you add. `npm ci` then the jobs in `.github/workflows/ci.yml`.
3. No `package.json` version bump unless Sean asked. No `npm publish`. No prod SQL.
4. No “MVP launched.” Published npm is `@hyperdag/trustshell@1.6.0` (2026-10-05).
4. No “MVP launched.” Published npm is `@hyperdag/trustshell@1.6.1` (measured 2026-10-14; `BUILDERS.md` is where this is checked).
5. Open the pull request. MERGE_POLICY: agents may squash-merge when checks are green and the PR is not publish / DDL / secrets.

Security: [SECURITY.md](SECURITY.md). Ecosystem map: [BUILDERS.md → How the pieces fit](BUILDERS.md#how-the-pieces-fit).
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ install — see **[`@hyperdag/trustshell`](https://github.com/DealAppSeo/trustsh
**For an AI tool (Claude Desktop, Cursor, Claude Code).** The checks are also an MCP server: the `trustshell-mcp` bin inside `@hyperdag/trustshell`. Install the package globally, then point the tool's config at the bin:

```bash
npm i -g @hyperdag/trustshell@1.6.0
npm i -g @hyperdag/trustshell
```

```json
Expand All @@ -181,7 +181,7 @@ The separate npm package `@hyperdag/trustshell-mcp` is older (1.0.0, 2026-07-08)
| If you're… | Install | What you get |
|---|---|---|
| A developer building an agent/app **in code** | `npm install @hyperdag/trustshell` | The SDK — HAL verification + ERC-8004 RepID + x402 payments, in your TypeScript/JS |
| Using an **AI tool** (Claude Desktop, Cursor, Claude Code), **no code** | `npm i -g @hyperdag/trustshell@1.6.0`, then the `trustshell-mcp` bin (above) | The checks as AI-callable tools |
| Using an **AI tool** (Claude Desktop, Cursor, Claude Code), **no code** | `npm i -g @hyperdag/trustshell`, then the `trustshell-mcp` bin (above) | The checks as AI-callable tools |
| Only verifying **ZK proofs** client-side | `npm install @hyperdag/proof-verifier` | Standalone Plonky3 proof checking (usually bundled with trustshell — rarely installed directly) |

**Most people want `@hyperdag/trustshell`. The SDK, the CLI and the MCP server are all in that one package. `proof-verifier` is a building block that ships inside trustshell.**
Expand Down
19 changes: 11 additions & 8 deletions scripts/check-builders.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -27,12 +27,15 @@ function notChecked(why) {
process.exit(2);
}

if (!builders.includes('PUBLISHED — `1.6.0`')) {
fail('BUILDERS.md does not name published @hyperdag/trustshell 1.6.0');
}
if (/PUBLISHED — `1\.4\.0`/.test(builders)) {
fail('BUILDERS.md still names 1.4.0 as the published package');
// The version is read FROM the doc, not written here. This file used to hardcode `1.6.0` twice,
// so publishing 1.6.1 turned every PR in this repo red until someone edited the CHECKER, which is
// the wrong file: the doc is what an outsider reads. Now a publish still turns CI red until
// BUILDERS.md names the new version, and the check itself never needs touching.
const named = [...builders.matchAll(/PUBLISHED — `(\d+\.\d+\.\d+)`/g)].map((m) => m[1]);
if (named.length !== 1) {
fail(`BUILDERS.md must name exactly one published @hyperdag/trustshell version; it names ${named.length}`);
}
const documented = named[0];
if (!builders.includes('exits 0 on PASS or FLAG, 1 on VETO, and 2 when HAL did not decide (NOT_CHECKED, never a pass)')) {
fail('BUILDERS.md does not say NOT_CHECKED exits 2 and is never a pass');
}
Expand All @@ -57,9 +60,9 @@ try {
} catch (err) {
notChecked(`npm view did not answer: ${String(err?.message ?? err).split('\n')[0]}`);
}
if (version !== '1.6.0') {
fail(`npm view @hyperdag/trustshell version is ${version}, and BUILDERS.md says 1.6.0`);
if (version !== documented) {
fail(`npm view @hyperdag/trustshell version is ${version}, and BUILDERS.md says ${documented}`);
}

console.log('check:builders — VERIFIED');
console.log(' BUILDERS.md names 1.6.0, exit 2 on NOT_CHECKED, and the optional ethers peer');
console.log(` BUILDERS.md names ${documented} (= npm), exit 2 on NOT_CHECKED, and the optional ethers peer`);
Loading