docs: credit the ERC-8004 team, map the trust stack, say why, narrow claims (LOW + approved vision text)

ACKNOWLEDGEMENTS.md

@@ -0,0 +1,26 @@
+# Acknowledgements
+
+HyperDAG is built on other people's work. Thank you.
+
+## ERC-8004: Trustless Agents
+
+The standard every HyperDAG agent identity and reputation write uses. ERC-8004 is a community effort coordinated by **Marco De Rossi** (MetaMask) and **Davide Crapis** (Ethereum Foundation), with the co-authorship of **Jordan Ellis** (Google) and **Erik Reppel** (Coinbase). The core team is joined by **Leonard Tan** (MetaMask), **Vitto Rivabella** (Ethereum Foundation) and **Isha Sangani** (Ethereum Foundation).
+
+- Specification: [EIP-8004](https://eips.ethereum.org/EIPS/eip-8004)
+- The registry contracts, the spec copy and the ABIs in [`packages/contracts`](packages/contracts) are the team's work, from [erc-8004/erc-8004-contracts](https://github.com/erc-8004/erc-8004-contracts), with their commit history. That history is why the team appears in this repository's contributor graph. Twenty files are byte-identical to upstream commit `b9e466c`; [`packages/contracts/NOTICE`](packages/contracts/NOTICE) lists each one, the files that differ, and the licences: MIT for the Solidity sources (CC0-1.0 for `SingletonFactory.sol`) and ISC for the package.
+- The registries on Base Sepolia, and on mainnet, are the team's deployments. We use them; we do not operate them.
+
+## Other work we build on
+
+- **x402** by Coinbase ([coinbase/x402](https://github.com/coinbase/x402)): the agent-to-agent payment protocol. Our engine implements it itself, on a test network.
+- **Plonky3** by Polygon Labs ([Plonky3/Plonky3](https://github.com/Plonky3/Plonky3)), with the **Poseidon2** hash: the proof system our prover, HyperDAG-core, uses.
+- **OpenZeppelin Contracts**, which the ERC-8004 contracts build on.
+- **The Ethereum Attestation Service**, which we use to anchor batches of proofs.
+- **Base Sepolia**, the test network all of this runs on today.
+- **The model providers our checks and test loops run on**, among them Groq, Cerebras and OpenRouter, and the public benchmark datasets credited where each is used (FEVER, HaluEval, TruthfulQA).
+
+## Research we lean on
+
+[`docs/WHY.md`](docs/WHY.md) explains why we build what we build, and cites the research for and against each part of it.
+
+If we have missed you, or credited you wrongly, please open an issue. We will fix it.

AUTHORS.md

@@ -2,7 +2,9 @@
 
 **Created and maintained by Sean Goodwin.**
 
-GitHub contributor **faces, graphs, and commit counts are a commit counter, not a credit assignment.** They do not imply co-authorship, endorsement, or maintainer status. The authoritative graph is [Contributors](https://github.com/DealAppSeo/hyperdag-protocol/graphs/contributors). We do not reprint names here as a hall of fame.
+**This repository stands on other people's work.** The ERC-8004 registry contracts, spec and ABIs in `packages/contracts` are the ERC-8004 team's, carried here with their commit history, which is why Marco De Rossi, Leonard Tan, Vitto Rivabella and others appear in the [contributor graph](https://github.com/DealAppSeo/hyperdag-protocol/graphs/contributors). Their credit, and everyone else's, is in [ACKNOWLEDGEMENTS.md](ACKNOWLEDGEMENTS.md).
+
+The contributor graph counts commits; it does not say who maintains this repository or who endorses it. Maintenance and every claim in this repository are Sean Goodwin's responsibility, not theirs.
 
 If two git identities are the same person, fold them with a `.mailmap` at the repo root (none is required today). Do not invent a mailmap to hide history.
 

BUILDERS.md

@@ -7,6 +7,8 @@ log — capped, dated, full of retractions and corrections aimed at people who
 already know the system. It is the wrong first thing for a stranger to meet, and
 it is not a promise we keep to you. This file is.
 
+Why we build any of this, and the research for and against it: [docs/WHY.md](docs/WHY.md). Whose work it stands on: [ACKNOWLEDGEMENTS.md](ACKNOWLEDGEMENTS.md).
+
 ---
 
 ## 1. What is actually usable today
@@ -18,7 +20,7 @@ publish X without touching this file.
 
 | Thing | State | How to check |
 |---|---|---|
-| **`@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/trustshell`** | **PUBLISHED — `1.8.0`** (measured 2026-10-23, with npm provenance; was 1.6.1 on 2026-10-14). 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 |
@@ -31,7 +33,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.1, re-measured 2026-10-14 (first measured on the 1.6.0 tarball, 2026-10-05).** `trustshell verify`
+**Published 1.8.0, measured 2026-10-23.** New in 1.8.0, Inspect: `trustshell check <run-url> --claims-file <file>` reads GitHub's own record of a GitHub Actions run and marks each sentence an agent wrote about it supported, contradicted or not checked. It exits 0 when every claim is supported, 1 when one is contradicted, and 3 when something was not checked; not checked never exits 0. Its only network call is to api.github.com. `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
@@ -128,6 +130,8 @@ when the two disagree.
 - **[DealAppSeo/trinity-symphony-shared](https://github.com/DealAppSeo/trinity-symphony-shared)**:
   the house agents. They call the engine. Nothing else calls them.
 - **DealAppSeo/trinity-ecosystem** (a private repository): the site at aitrinitysymphony.com.
+- **[DealAppSeo/trustrepid](https://github.com/DealAppSeo/trustrepid)**: a RepID dashboard site, at trustrepid.vercel.app. It reads the engine.
+- **DealAppSeo/trustmarket** (a private repository): the agent-marketplace sandbox. It calls the engine; its payments are mocked.
 
 **Who calls whom**
 
@@ -136,6 +140,7 @@ when the two disagree.
   reputation, for example once paid work passes its check); and a person, by a link to
   `https://controller.aitrinitysymphony.com`, when a decision needs a human.
 - the house agents → the engine (and a health check of the prover).
+- trustrepid and trustmarket → the engine.
 - nothing else → the house agents.
 - this repository → nothing at runtime.
 

METHODOLOGY.md

@@ -1,6 +1,8 @@
 # HyperDAG RepID — Methodology & Mathematical Specification
 ## Version 1.0 · April 2026
 
+> **Historical document, kept for the record.** It was written in April 2026, and several figures and mechanisms below have since been corrected or superseded. Lines marked *(superseded)* are not current. For what is true today, read [BUILDERS.md](BUILDERS.md); for why we build it and the evidence for and against, read [docs/WHY.md](docs/WHY.md); for credits, read [ACKNOWLEDGEMENTS.md](ACKNOWLEDGEMENTS.md).
+
 ### Abstract
 RepID is a verifiable behavioral credit score for AI agents (and humans who wish to participate and contribute to the ecosystem, and/or own and train agents — thus being responsible for, but also reaping the benefits of their agents' performance — as their custodians), designed to bridge deterministic smart-contract execution with probabilistic LLM decision-making. By cryptographically isolating constitutional behavior from logical capabilities, it solves the adversarial misalignment problem in multi-agent topologies. What makes RepID mathematically novel is its decoupling of traditional reputational metrics onto a zero-knowledge verifiable layer powered by an asymmetric dissonance filter, enforcing accountability before execution.
 
@@ -10,11 +12,10 @@ RepID is a verifiable behavioral credit score for AI agents (and humans who wish
   d = (0.4×harm + 0.3×epistemic + 0.2×evidence + 0.1×scope) × (531441/524288)
 - Veto threshold: dissonance > 0.0195 → VETO
 - Constitutional block: dissonance > 0.48
-- Production evidence: 2,585 vetoes from 2,600 evaluations (99.4% refusal rate)
-- 714 capital protection events
+- *(superseded)* "Production evidence: 2,585 vetoes from 2,600 evaluations (99.4% refusal rate)" and "714 capital protection events" were April-2026 counts on an engine that has since changed. A 99.4% refusal rate described an over-strict configuration, not accuracy. Current HAL measurements, with the corpus each was taken on, are in repid-engine's README.
 
 ### 2. RepID Scoring Formula
-- Tier structure: CUSTODIED_DBT (0-999) / EARNING_AUTONOMY (1000-4999) / AUTONOMOUS (5000-10000)
+- *(superseded)* Tier structure: CUSTODIED_DBT (0-999) / EARNING_AUTONOMY (1000-4999) / AUTONOMOUS (5000-10000). RepID now has five tiers, PROBATIONARY to VETERAN ([BUILDERS.md](BUILDERS.md)).
 - Decay function: decayed = current × √(activity_30d / baseline)
 - Floor: never reaches zero. Ceiling: 10,000
 - φ-Asymmetric challenge scoring:
@@ -24,18 +25,18 @@ RepID is a verifiable behavioral credit score for AI agents (and humans who wish
 
 ### 3. The Grace Pool
 - Definition: 20% unconditional RepID issuance to lowest-scoring cohort
-- Implementation: on-chain, immutable, cannot be canceled by vote
+- *(superseded)* Implementation: "on-chain, immutable, cannot be canceled by vote". At its last audit (2026-05-28) the Grace Pool had a database schema and no distributions; it is not on-chain.
 - Rationale: prevents reputation concentration, encodes equity as constraint
 
 ### 4. BFT Consensus (SBFA)
-- 3-LLM supermajority: Claude + Grok + Gemini
+- *(superseded)* 3-LLM supermajority: Claude + Grok + Gemini. Today's hosted check uses two checkers on free model providers; how they are chosen is in repid-engine's README.
 - Threshold: ≥ 66.7%
 - Pythagorean Comma applied to detect coordination attacks
 - Constants: BFT_THRESHOLD = 0.618, CONFIDENCE_GATE = 0.8, REPID_HITL_GATE = 70
 
 ### 5. ZK Proof Architecture
 - Proof system: Plonky3 (no trusted setup, recursive, WASM < 100ms)
-- Current status: 122 proofs generated on HashKey Chain
+- *(superseded)* Current status: 122 proofs generated on HashKey Chain. Today the prover is HyperDAG-core, and its proofs are batch-anchored with EAS on Base Sepolia.
 - Attestation: EAS schema on Base Sepolia
 - Note: Plonky3 integration is production-stub in current deploy; 
   full circuit in active development (Sprint 3)

NOTICE

@@ -0,0 +1,10 @@
+HyperDAG Protocol
+Copyright 2026 Sean Goodwin
+
+This repository includes the ERC-8004 registry contracts, specification and
+ABIs by the ERC-8004 team (Marco De Rossi, Davide Crapis, Jordan Ellis,
+Erik Reppel, with Leonard Tan, Vitto Rivabella and Isha Sangani), from
+https://github.com/erc-8004/erc-8004-contracts. Those files keep their own
+licences (MIT, CC0-1.0, ISC). Details: packages/contracts/NOTICE.
+
+Full credits: ACKNOWLEDGEMENTS.md.