Ecosystem
This is not one product.
It is a category with an editorial hub, a flagship implementation, adjacent methods, proof sources, runtimes, and extensions.
The point of the ecosystem page is to make those roles legible instead of flattening everything into one list.
The layers
Editorial layer
1/6Category framing, positioning, and routing
Explains the idea and helps visitors understand where to go next.
Method layer
2/6Reference implementations and adjacent methods
Shows how better thinking loops actually work across different systems.
Proof layer
3/6Cases, review signals, and evidence quality
Where the category earns trust through visible changed thinking, changed action, and review.
System layer
4/6Files, commands, routines, and reusable structures
Turns methods into things people can actually adopt and adapt.
Runtime layer
5/6Claude, ChatGPT, Gemini, Hermes, local coding environments
The environments where the same method gets practiced in different ways.
Extension layer
6/6Wedges, products, experiments, and community contributions
Where the category branches into narrower applications and entry points.
The map is organized by role, not by chronology and not by ownership alone.
Classification model
Every entry in the ecosystem should answer two questions: what role does it play, and what is its relationship to the author?
Category roles
Relationship labels: `Internal`, `External`, or `Mixed`.
Current internal map
Global AI Hub
Defines the category, organizes the proof, compares methods, and maps the ecosystem.
Symbiotic AI
The clearest current authored system for persistent context, commitment, and review across sessions.
Personal AI Hub
Explores app surfaces, onboarding, and productized experiences built on related ideas.
Bug Map
A pain-first entry point around recurring patterns and self-defeating loops.
`symbiotic-ai` should be featured prominently because it is the flagship reference implementation, but the ecosystem must also make room for outside methods, outside proof, and outside runtimes.