|
| 1 | +# apcore Roadmap |
| 2 | + |
| 3 | +> **Last Updated**: March 2026 |
| 4 | +> **Status**: Living document — updated quarterly |
| 5 | +
|
| 6 | +This roadmap outlines the planned development for the apcore protocol specification and its ecosystem. Community input is welcome — open an [issue](https://github.com/aiperceivable/apcore/issues) to discuss priorities. |
| 7 | + |
| 8 | +--- |
| 9 | + |
| 10 | +## Current Status (v1.6.0-draft) |
| 11 | + |
| 12 | +### Completed |
| 13 | + |
| 14 | +**Protocol Specification** |
| 15 | +- [x] Complete PROTOCOL_SPEC.md (RFC 2119 conformant) |
| 16 | +- [x] Module lifecycle (11-step pipeline) |
| 17 | +- [x] Schema system (three-layer metadata: module, action, LLM extension) |
| 18 | +- [x] Behavioral annotations (`readonly`, `destructive`, `requires_approval`, `idempotent`, `open_world`) |
| 19 | +- [x] ACL access control (pattern-based, role-aware) |
| 20 | +- [x] Context object and trace propagation |
| 21 | +- [x] Middleware system |
| 22 | +- [x] Configuration management |
| 23 | +- [x] Observability (tracing, metrics, structured logging) |
| 24 | +- [x] Error handling with `ai_guidance` field |
| 25 | + |
| 26 | +**Language SDKs** |
| 27 | +- [x] [apcore-python](https://github.com/aiperceivable/apcore-python) — Python 3.11+ |
| 28 | +- [x] [apcore-typescript](https://github.com/aiperceivable/apcore-typescript) — Node 18+ |
| 29 | +- [x] [apcore-rust](https://github.com/aiperceivable/apcore-rust) — Rust 1.75+ |
| 30 | + |
| 31 | +**Toolkit (Schema Transformation)** |
| 32 | +- [x] [apcore-toolkit-python](https://github.com/aiperceivable/apcore-toolkit-python) |
| 33 | +- [x] [apcore-toolkit-typescript](https://github.com/aiperceivable/apcore-toolkit-typescript) |
| 34 | +- [x] [apcore-toolkit-rust](https://github.com/aiperceivable/apcore-toolkit-rust) |
| 35 | + |
| 36 | +**MCP Bridge** |
| 37 | +- [x] [apcore-mcp-python](https://github.com/aiperceivable/apcore-mcp-python) |
| 38 | +- [x] [apcore-mcp-typescript](https://github.com/aiperceivable/apcore-mcp-typescript) |
| 39 | +- [x] [apcore-mcp-rust](https://github.com/aiperceivable/apcore-mcp-rust) |
| 40 | + |
| 41 | +**A2A Bridge** |
| 42 | +- [x] [apcore-a2a-python](https://github.com/aiperceivable/apcore-a2a-python) |
| 43 | +- [x] [apcore-a2a-typescript](https://github.com/aiperceivable/apcore-a2a-typescript) |
| 44 | + |
| 45 | +**CLI Adapter** |
| 46 | +- [x] [apcore-cli-python](https://github.com/aiperceivable/apcore-cli-python) |
| 47 | +- [x] [apcore-cli-typescript](https://github.com/aiperceivable/apcore-cli-typescript) |
| 48 | +- [x] [apcore-cli-rust](https://github.com/aiperceivable/apcore-cli-rust) |
| 49 | + |
| 50 | +**Framework Adapters** |
| 51 | +- [x] [django-apcore](https://github.com/aiperceivable/django-apcore) |
| 52 | +- [x] [flask-apcore](https://github.com/aiperceivable/flask-apcore) |
| 53 | +- [x] [fastapi-apcore](https://github.com/aiperceivable/fastapi-apcore) |
| 54 | +- [x] [nestjs-apcore](https://github.com/aiperceivable/nestjs-apcore) |
| 55 | +- [x] [axum-apcore](https://github.com/aiperceivable/axum-apcore) |
| 56 | +- [x] [tiptap-apcore](https://github.com/aiperceivable/tiptap-apcore) |
| 57 | + |
| 58 | +**Governance & Compliance** |
| 59 | +- [x] Apache 2.0 License |
| 60 | +- [x] GOVERNANCE.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, MAINTAINERS.md |
| 61 | +- [x] OpenSSF Best Practices Badge (Passing) |
| 62 | +- [x] DCO enforcement via GitHub App |
| 63 | + |
| 64 | +--- |
| 65 | + |
| 66 | +## 2026 Q2: Ecosystem Maturity |
| 67 | + |
| 68 | +### Specification |
| 69 | +- [ ] Finalize v1.6.0 specification |
| 70 | +- [ ] Cross-language conformance test suite |
| 71 | +- [ ] Formal specification review process |
| 72 | + |
| 73 | +### Tooling |
| 74 | +- [ ] **apexe** — CLI-to-Agent bridge for infrastructure tools (kubectl, docker, gh) |
| 75 | +- [ ] **apdev** — Architecture guardian with multi-language dependency analysis |
| 76 | + - Tree-sitter based code analysis |
| 77 | + - MCP server integration for IDE support |
| 78 | + |
| 79 | +### Community & Standards |
| 80 | +- [ ] Foundation submission preparation (AAIF / CNCF) |
| 81 | +- [ ] Positioning document ([docs/POSITIONING.md](docs/POSITIONING.md)) |
| 82 | +- [ ] "Good first issue" labeling for contributor onboarding |
| 83 | +- [ ] Community discussion channels |
| 84 | + |
| 85 | +--- |
| 86 | + |
| 87 | +## 2026 Q3: Foundation & Adoption |
| 88 | + |
| 89 | +### Standards Body Engagement |
| 90 | +- [ ] Formal foundation submission (AAIF primary, CNCF secondary) |
| 91 | +- [ ] CNCF TAG App Delivery engagement |
| 92 | +- [ ] Industry partnership outreach |
| 93 | + |
| 94 | +### Technical Expansion |
| 95 | +- [ ] Additional framework adapters (Spring Boot, Express, Actix) |
| 96 | +- [ ] Enhanced security scanning for modules |
| 97 | +- [ ] Plugin system for custom extensions |
| 98 | +- [ ] Event engine for audit trails |
| 99 | + |
| 100 | +### Developer Experience |
| 101 | +- [ ] Interactive module playground |
| 102 | +- [ ] Getting-started tutorials per language |
| 103 | +- [ ] Video walkthroughs and demos |
| 104 | + |
| 105 | +--- |
| 106 | + |
| 107 | +## 2026 Q4+: Industry Standard |
| 108 | + |
| 109 | +### Ecosystem Growth |
| 110 | +- [ ] 3+ independent adopters (Incubation requirement) |
| 111 | +- [ ] External maintainers from different organizations |
| 112 | +- [ ] OpenSSF Badge Silver/Gold progression |
| 113 | +- [ ] Conference talks and workshops |
| 114 | + |
| 115 | +### Advanced Features |
| 116 | +- [ ] Module versioning and compatibility system |
| 117 | +- [ ] Distributed module discovery |
| 118 | +- [ ] Advanced observability (OpenTelemetry deep integration) |
| 119 | +- [ ] Performance benchmarks across languages |
| 120 | + |
| 121 | +### Broader Ecosystem |
| 122 | +- [ ] **aphub** — AI Agent registry and governance platform |
| 123 | +- [ ] **apflow** — Distributed orchestration engine |
| 124 | +- [ ] **apevo** — Autonomous error detection, diagnosis, and repair |
| 125 | + |
| 126 | +--- |
| 127 | + |
| 128 | +## How to Contribute |
| 129 | + |
| 130 | +We welcome contributions at every level: |
| 131 | + |
| 132 | +- **Spec discussion**: Open an [issue](https://github.com/aiperceivable/apcore/issues) with the `spec` label |
| 133 | +- **SDK improvements**: Pick up issues in language-specific repos |
| 134 | +- **Framework adapters**: Port existing adapters or create new ones |
| 135 | +- **Documentation**: Improve guides, add examples, fix typos |
| 136 | +- **Testing**: Expand conformance tests across languages |
| 137 | + |
| 138 | +See [CONTRIBUTING.md](CONTRIBUTING.md) for details. |
| 139 | + |
| 140 | +--- |
| 141 | + |
| 142 | +## Prioritization |
| 143 | + |
| 144 | +Roadmap priorities are set by maintainers based on: |
| 145 | +1. Foundation submission requirements |
| 146 | +2. Community demand (GitHub issues, discussions) |
| 147 | +3. Cross-language consistency needs |
| 148 | +4. Security and stability improvements |
| 149 | + |
| 150 | +To influence priorities, open an issue or join the discussion on existing ones. |
0 commit comments