From ba98a406d6e1a5c3032b12c4f98df21842bf8140 Mon Sep 17 00:00:00 2001 From: Claude Bot Date: Thu, 30 Jul 2026 12:39:37 +0800 Subject: [PATCH] docs(profile): adopt provable-agent framing, link runnable golden-path (closes #139) The portal was internally inconsistent: the heading/tagline said "The Trusted Agent OS" while the Projects section already framed WasmAgent as "open infrastructure for provable AI agents". Align the whole page: - heading -> "Open infrastructure for provable AI agents" - tagline drops the "Trusted Agent OS" metaphor, centers on signed / verifiable / auditable evidence - Golden Path now points at the runnable WasmAgent/agent-golden-path repo (public, MIT, bun install && bun test) as the canonical reference, and clarifies the in-repo golden-path/ harness as the WIP cross-repo contract acceptance line Docs-only change to the org portal. No structure/index change. --- profile/README.md | 25 ++++++++++++++++--------- 1 file changed, 16 insertions(+), 9 deletions(-) diff --git a/profile/README.md b/profile/README.md index 8bc17fc..e8d2f8a 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,26 +1,33 @@ -# WasmAgent — The Trusted Agent OS +# WasmAgent — Open infrastructure for provable AI agents > The industry's focus is shifting from *"can the agent do the task?"* to *"can the agent run reliably, at scale, over time?"* We believe that is still not enough. The real question is: **"can you prove the agent ran correctly?"** > -> WasmAgent is building the infrastructure layer for that — a Trusted Agent OS: runtime isolation, protocol-level interception, symbolic verification, tamper-evident evidence, and regulatory compliance, composable as open infrastructure rather than a single product. +> WasmAgent is **open infrastructure for _provable_ AI agents** — the layer that turns agent execution into signed, verifiable, auditable evidence: runtime isolation, protocol-level interception, symbolic verification, tamper-evident evidence, and regulatory compliance, composable rather than a single product. > > Parts of this vision are shipping today. Parts are in active development. The table below is honest about which is which. ## Golden Path -The fastest way to see WasmAgent's trust loop end-to-end: +The fastest way to see the provable-agent stack run end-to-end is the +**[`agent-golden-path`](https://github.com/WasmAgent/agent-golden-path)** reference +app (public, MIT) — a runnable procurement copilot that wires every layer together: ```bash -git clone https://github.com/WasmAgent/.github -cd .github/golden-path -./scripts/demo.sh +git clone https://github.com/WasmAgent/agent-golden-path +cd agent-golden-path +bun install && bun test # end-to-end chain test, no live LLM required ``` -This runs `Protect → Record → Audit → Admit` across all core repos. -See [`golden-path/README.md`](../golden-path/README.md) for details. +It proves the full chain in one app: agent execution → tool admission +(`mcp-firewall`) → compliance verification → signed **AEP** evidence → audit +report + trust passport (`open-agent-audit`). This is the canonical reference the +rest of the ecosystem points to. -> **Status:** scaffolded — not yet runnable. Track progress via the [issue tracker](https://github.com/WasmAgent/.github/issues?q=is%3Aissue+golden-path). +> There is also an org-level cross-repo integration harness in +> [`golden-path/`](../golden-path/) (`Protect → Record → Audit → Admit`, one step +> per core repo). It is the multi-repo contract acceptance line and is still a +> work in progress — for a runnable demo, use `agent-golden-path` above. ## Projects