docs(portal): restructure org as a tiered tree; add wasmagent-protocol to Core - #128
Merged
Conversation
…l to Core Evolve the flat focus groups into an expandable tree so a first-time visitor grasps the ecosystem in 30 seconds and future official tools/apps have a home: - ⭐ Core — wasmagent-js, wasmagent-protocol (new), symkernel, agent-trust-infra (+ planned wasmagent-py). Runtime, protocol, verification, trust. - 🛠 Official tooling — CLI/devtools/examples. Planned tier, reserved (no repos). - 🔌 Evidence surfaces — wasmagent-proxy, trace-pipeline, wasmagent-train-replay; move to community maintenance once roadmaps land. - 🧪 Research — fresharena. - 📦 Product / reference / hub — open-agent-audit, bscode, .github. - 🎮 Apps — playground/desktop/editor extensions. Planned tier, reserved. Deliberately NOT done (keeps the provable-infra moat intact): - agent-trust-infra stays Core, not demoted to Research (EU AI Act is the moat). - No new wasmagent-runtime and no SDK/Runtime split — js IS the runtime, the Go layer IS symkernel; a second runtime repo would collide. - Add wasmagent-protocol to project-index.json (category "protocol", core-spine focus) and the profile Core table; add official-tooling to focus_legend. - Redraw product-matrix.svg as a clean, layered tier diagram. - Mirror the tree in roadmap.md and repository-boundaries.md. Validator + go tests green; profile/index coherence preserved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Evolves the flat focus groups into an expandable tree (Core → Official tooling → Evidence surfaces → Research → Product/Reference/Hub → Apps) so visitors grasp the ecosystem in 30 seconds and future tools/apps have a reserved home.
Adopted from the tiering proposal: dont split the org, classification over count, 30-second legibility, tree-shaped layers.
Deliberately rejected (keeps the provable-infra moat):
agent-trust-infrastays Core, not demoted to Research — EU AI Act Annex IV compliance is the market moat.wasmagent-runtimeand no SDK/Runtime split —wasmagent-jsis the runtime; the Go layer issymkernel; a second runtime repo would collide.Changes: add
wasmagent-protocolto Core (project-index + profile), addofficial-toolingto focus_legend, redrawproduct-matrix.svgas a clean layered tier diagram, mirror the tree in roadmap.md + repository-boundaries.md. Validator + go tests green; profile/index coherence preserved.