diff --git a/profile/README.md b/profile/README.md
index 88d4f34..b8cb50a 100644
--- a/profile/README.md
+++ b/profile/README.md
@@ -3,12 +3,24 @@
 **Define once. Run anywhere.**
 
 Traverse is a contract-driven WebAssembly runtime and a governed registry for
-**portable business capabilities**. You write a rule — pricing, eligibility,
+**portable business capabilities**. You define a rule — pricing, eligibility,
 authorization, escalation — once, as a capability with a machine-readable
 contract, and the same signed WASM artifact runs on Linux, macOS, and Windows,
 in the browser, on a server, and inside an AI agent — producing a verifiable
 execution trace when the governed path runs.
 
+**You do not need to write Rust to create capabilities.** The usual path is the
+Claude skill
+[`traverse-capability-author`](https://github.com/traverse-framework/claude-skills/tree/main/skills/traverse-capability-author)
+(plain English interview → registry check → contract → WASM → human-reviewed
+PR). Manual authoring still uses Rust→WASM. Under the hood remains Rust→WASM
+for determinism, sandboxing, and portability.
+
+**One shared WASM runtime everywhere.** Same capability artifact, same
+`runtime.wasm` orchestrator, same semantics and governance on every host.
+Browser, native, CLI, and MCP are **embedders / entry points**, not different
+Traverse runtimes.
+
 Mobile embedders and reference-app shells for iOS and Android exist and are
 advancing (Swift/`wasmi`, Kotlin/Chicory), but they are not yet certified
 public releases the way native desktop and the published Web/TypeScript
@@ -30,7 +42,7 @@ start in [`traverse`](https://github.com/traverse-framework/traverse)
 | [`traverse`](https://github.com/traverse-framework/traverse) | Core runtime, CLI, contracts, and MCP surface. Rust, published crates at **`v0.12.0`**, **150** approved specs, **6** crates on crates.io (`traverse-contracts`, `traverse-runtime`, `traverse-embedder`, `traverse-cli-rs`, `traverse-mcp`, `traverse-expedition-wasm`; registry client is the separate `traverse-registry` crate), ~754 commits. |
 | [`registry`](https://github.com/traverse-framework/registry) | The public capability registry — a git-based, CI-validated, PR-published catalog. **92** capabilities across **33** domains (**213** signed versions; **175** non-deprecated) live at [registry.traverse-framework.com](https://registry.traverse-framework.com). |
 | [`reference-apps`](https://github.com/traverse-framework/reference-apps) | UI shells for the same Traverse capabilities: Web, macOS, iOS, Android, Windows, Linux, CLI, plus MCP façades for Claude, Cursor, ChatGPT, and Grok. |
-| [`claude-skills`](https://github.com/traverse-framework/claude-skills) | Claude Skills for building on Traverse — check the registry before authoring, compose capabilities, validate against the real CLI. |
+| [`claude-skills`](https://github.com/traverse-framework/claude-skills) | Claude Skills for building on Traverse — primary authoring on-ramp (`traverse-capability-author`), plus extractor and workflow-planner. Check the registry before authoring; validate against the real CLI. |
 | [`website`](https://github.com/traverse-framework/website) | The public site and documentation. |
 | [`.github`](https://github.com/traverse-framework/.github) | *(this repo)* Org-wide governance — constitution, NFRs, quality standards, CI gates, CLA, and AI-agent hardening rules shared by every repo above. |
 | [`repo-template`](https://github.com/traverse-framework/repo-template) | Starting point for a new org repo — compliant with governance from the first commit. |
@@ -43,6 +55,16 @@ usable in-tree / via reference apps, with public package certification still
 open. Cloud and edge placement targets are specified and on the roadmap, not
 yet shipped.
 
+### Consumers / clients (honest)
+
+| Surface | Status |
+|---|---|
+| JS/TS | Published npm `traverse-embedder-web@0.12.0` |
+| Rust | Published crates.io `traverse-embedder@0.12.0` |
+| AI agents | Published `traverse-mcp` (stdio) |
+| Python | Works today by shelling out to `traverse-cli capability-package execute` — **no Python SDK** |
+| Swift / Kotlin / .NET | In-tree with conformance; not first-class published package consumers yet |
+
 ---
 
 ## Why it matters