Skip to main content

Context

Meridian currently documents 3 active councils (Pathfinder, Hermes, Athena) across 4 populated domains. But the STRATT schema declares 11 domains, and BUNDLE-02 strategic plans define 2 additional councils (Neuro, Primer) with full agent rosters. This planned data was sitting in architecture documents, invisible to anyone browsing Meridian.

Learning

Adding planned councils to Meridian — with “Planned” badges, dashed card borders, and clear status labels — transforms the documentation site from a snapshot of current state into a roadmap of future capability. Visitors can see that the neuro domain will have 6 agents (CURIE-01 through TURING-06) and the primer pipeline will have a 3-agent meta-council. The 5 remaining empty domains (finance, nutrition, legal, film, artist) appear as “pending” chips, signaling that the platform’s horizontal scaling path is defined, not aspirational.

Business Takeaway

Documentation sites are often treated as trailing indicators — they describe what exists. Making them leading indicators (describing what is planned, with clear visual distinction) serves dual purposes: it gives potential adopters confidence in the platform’s direction, and it creates public accountability for the roadmap. The Primer pipeline’s planned council definitions appearing in Meridian make the path from 4 domains to 11 domains tangible rather than theoretical. This is especially valuable when fundraising or recruiting — the platform’s scope becomes self-evident without a separate pitch deck.