Where we're going
Building in the open. Everything on this roadmap is subject to community feedback — your input shapes what we build next.
Phase 0 · Feb 2026
Foundation
Extract the PAI Framework specs, build the CLI tool, ship the starter kit to GitHub.
- 5-layer architecture specification
- Skill system spec (SKILL.md format)
- Hook lifecycle spec (6 events)
- CLI tool: pai init
- CLI tool: pai skill create / index / lint
- 4 starter skills (Research, DoWork, Reflect, HelloWorld)
- 5 starter hooks
- Template files (CLAUDE.md, context.md, etc.)
- Getting started documentation
- GitHub release
Phase 1 · Mar 2026
Skill Marketplace
A marketplace where anyone can browse, install, and share AI skills. Creators set prices, platform handles distribution.
- Skill package format and validation
- pai skill install <name> command
- pai skill publish command
- Web-based skill browser on percivallabs.com
- Creator profiles and skill ratings
- Revenue sharing (70/30 creator/platform)
- Security scanning for published skills
Phase 2 · Q2 2026
Community & Governance
Build the community infrastructure. Discord, contributor guides, skill quality standards, and governance framework.
- Discord server with skill channels
- Contributor guide and code of conduct
- Skill quality standards and review process
- Community skill submissions
- Monthly community calls
Phase 3 · Q2-Q3 2026
Multi-Agent & Coordination
Specs and tools for running multiple AI agents that share context, coordinate work, and maintain trust boundaries.
- Agent coordination spec
- Shared context with access control
- Zero Trust governance layer
- Agent-to-agent communication protocol
- Trust scoring and permission escalation
Phase 4 · Q3-Q4 2026
Hosted Platform
Cloud-hosted Engram management. Web dashboard, automatic backups, team features, and enterprise controls.
- Web dashboard for Engram management
- Cloud backup and sync
- Team Engrams with shared skills
- Usage analytics and insights
- Enterprise SSO and compliance
- API for programmatic Engram management
How we decide what to build
C > D
Does this make cooperation more rewarding than defection? Open by default.
Ship > Perfect
Working software over comprehensive documentation. We iterate in the open.
Transfer > Depend
Every feature should teach users to do more, not lock them in.
Community > Roadmap
User feedback overrides our plans. If the community needs something, we build it.
Shape what we build next
Join the waitlist to get early access and direct input on the roadmap.