Vision & Direction
Seshat keeps a broad open-source vision on purpose. The discipline is not to remove that ambition, but to place it on the right surface: a narrow product wedge on the homepage, a more serious deployment story for organizations, and a wider thesis in the docs for builders and contributors.
Overview
Seshat is not trying to be just another chat interface or a thin wrapper over one model vendor. The project is trying to build a governed runtime and platform foundation for agentic work that can stay open, self-hostable, extensible, and useful across many serious domains over time.
That broad direction matters for the community because it explains why the project cares about self-hosting, provider portability, MCP, skills, permissions, session ownership, and eventually more structured team coordination. A contributor needs the wider map, not only the current feature list.
For the current product boundary, continue with What is Seshat?. For the architectural bets behind that direction, continue with Technical Hypotheses.
Three Layers Of The Vision
The public messaging should not flatten these layers into one vague promise. Each surface should emphasize the layer that matters most to its audience.
Long-Term Directions
- Organized agentic work: agents that do not only act, but coordinate through explicit roles, reports, handoffs, and mission memory.
- Progressive automation: not magic autonomy everywhere, but serious automation wherever work becomes observable, structured, delegable, and governable.
- Open extensibility: providers, tools, skills, MCP, APIs, and deployment shapes should remain portable instead of locking users into one stack.
- Learning and transmission: the same foundation should eventually support explanation, guided learning, and adaptive educational flows without inventing a separate execution philosophy.
This is the large vision that belongs in the docs and in open-source communication. It gives contributors a reason to build on top of Seshat beyond today's narrow runtime wedge.
What Is Real Today And Why That Matters
A broad vision is healthy only if the project stays honest about what exists now. Seshat today is strongest as a governed, self-hosted, multi-provider runtime and platform base, not yet as a fully mature team-operating environment across every domain.
This is why the homepage must stay narrower than the vision. The docs can carry the larger map without making the product sound scattered or inflated.
Why The Open Foundation Matters
The community case for Seshat is not just that the code is public. The deeper claim is that agent infrastructure should remain inspectable, governable, affordable to run, and adaptable by the people who understand real workflows best.
- Developers can push the runtime, APIs, SDKs, and deployment story forward.
- Operators can harden permissions, observability, and governance paths.
- Domain experts can encode knowledge through skills, retrieval, and integration patterns.
- Future partners can build product surfaces and specialized workflows without starting from a closed black box.
That is the point of keeping the broad vision alive in the documentation: it tells builders what kind of ecosystem Seshat is trying to become, even while the product messaging stays disciplined elsewhere.