Problem
A first-time visitor to the WasmAgent org page cannot tell the relationship between the four names they encounter:
- WasmAgent — the GitHub organization
- open-agent-audit / OpenAgentAudit — the audit specification project
- Trustavo — the commercial deployment layer
- AgentBOM — the independent spec and CLI
Currently there is no diagram or single-paragraph explanation that maps these together. This creates confusion and erodes trust.
Required change
Add a brand relationship diagram to the org-level README (profile/README.md or equivalent homepage location) that:
- Shows the four names and their relationship in a simple visual (Mermaid diagram is fine).
- Answers in one line each: what it is, who it is for, where to find it.
- Fits above the fold on a desktop browser — no scrolling required to see the full map.
Example structure:
WasmAgent (org)
├── open-agent-audit — open specification for verifiable agent compliance
├── wasmagent-js — reference runtime (AEP, policy, MCP)
├── AgentBOM — agent bill-of-materials spec & CLI
└── Trustavo — commercial compliance report layer (built on the above)
Acceptance criteria
- The diagram is visible on the org homepage without scrolling.
- Each of the four names links to its primary repo or landing page.
- A non-technical reader can explain the relationship after reading it once.
Problem
A first-time visitor to the WasmAgent org page cannot tell the relationship between the four names they encounter:
Currently there is no diagram or single-paragraph explanation that maps these together. This creates confusion and erodes trust.
Required change
Add a brand relationship diagram to the org-level README (profile/README.md or equivalent homepage location) that:
Example structure:
Acceptance criteria