Skip to content

ROADMAP.md

Latest commit

 

History

History
177 lines (135 loc) · 7.05 KB

ROADMAP.md

File metadata and controls

177 lines (135 loc) · 7.05 KB

apcore Roadmap

Last Updated: March 2026 Status: Living document — updated quarterly

This roadmap outlines the planned development for the apcore protocol specification and its ecosystem. Community input is welcome — open an issue to discuss priorities.

Current Status (v1.6.0-draft)

Completed

Protocol Specification

  • Complete PROTOCOL_SPEC.md (RFC 2119 conformant)
  • Module lifecycle (11-step pipeline)
  • Schema system (three-layer metadata: module, action, LLM extension)
  • Behavioral annotations (readonly, destructive, requires_approval, idempotent, open_world)
  • ACL access control (pattern-based, role-aware)
  • Context object and trace propagation
  • Middleware system
  • Configuration management
  • Observability (tracing, metrics, structured logging)
  • Error handling with ai_guidance field

Language SDKs

Toolkit (Schema Transformation)

MCP Bridge

A2A Bridge

CLI Adapter

Framework Adapters

Core Product: apexe (CLI-to-Agent Bridge)

  • apexe — v0.2.0, Rust, 9.1K LOC
    • Scan any CLI tool into governed apcore modules (apexe scan <tool>)
    • Serve as MCP tools with ACL, audit logging, and shell injection prevention (apexe serve)
    • 3-tier scanning engine (--help → man pages → shell completions)
    • Auto-inferred behavioral annotations (readonly/destructive/requires_approval)
    • Explorer UI for interactive debugging
    • Single-binary distribution, zero dependencies

Governance & Compliance

  • Apache 2.0 License
  • GOVERNANCE.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, MAINTAINERS.md
  • OpenSSF Best Practices Badge (Passing)
  • DCO enforcement via GitHub App

2026 Q2: Specification Finalization & Foundation Submission

Specification

  • Finalize v1.6.0 specification
  • Cross-language conformance test suite (Python, TypeScript, Rust)
  • Formal specification review process

Foundation Submission

  • Contact AAIF — understand project acceptance process
  • CNCF TAG App Delivery engagement (backup track)
  • Positioning document (docs/POSITIONING.md)
  • Formal submission (AAIF primary, CNCF secondary)

Community Building

  • "Good first issue" labeling for contributor onboarding
  • Community discussion channels
  • Document internal dogfooding results as GitHub issues
  • External early adopter outreach

2026 Q3: Hardening & Ecosystem Validation

Scope adjusts based on team recruitment and foundation progress.

SDK Quality & Testing

  • Expand test coverage across Python, TypeScript, and Rust SDKs
  • Cross-language behavioral conformance test suite
  • CI/CD pipeline hardening (automated release, regression tests)
  • Performance benchmarks across languages

Ecosystem Validation

  • End-to-end integration tests: apcore → MCP → A2A → CLI full chain
  • Framework adapter conformance verification (all 6 adapters)
  • apexe integration validation with real-world CLI tools
  • Continued pilot feedback integration

Developer Experience

  • Getting-started tutorials per language
  • Interactive module playground
  • Video walkthroughs and demos

apexe Evolution

  • A2A protocol support (expose scanned tools as agent skills)
  • Package registry publishing (crates.io, Homebrew)

2026 Q4+: Expansion

Scope and pace depend on community growth and contributor recruitment.

Ecosystem Growth

  • 3+ independent adopters (Incubation requirement)
  • External maintainers from different organizations
  • OpenSSF Badge Silver/Gold progression
  • Conference talks and workshops

Additional Language SDKs

  • Go SDK — apcore-go + toolkit + MCP/A2A/CLI bridges + Gin/Echo adapters
  • Java/Kotlin SDK — apcore-java + toolkit + MCP/A2A/CLI bridges + Spring Boot adapter
  • Swift SDK — apcore-swift + toolkit + MCP/A2A/CLI bridges + Vapor adapter
  • C# SDK — apcore-dotnet + toolkit + MCP/A2A/CLI bridges + ASP.NET Core adapter

Advanced Features

  • Module versioning and compatibility system
  • Advanced observability (OpenTelemetry deep integration)
  • Distributed module discovery
  • Enhanced security scanning for modules
  • Plugin system for custom extensions
  • Event engine for audit trails
  • apdev — Architecture guardian with multi-language dependency analysis

Broader Ecosystem (Built on apcore)

  • aphub — AI Agent registry and governance platform
  • apflow — AI Agent production middleware (durable execution, cost governance)
  • apevo — Autonomous error detection, diagnosis, and repair

How to Contribute

We welcome contributions at every level:

  • Spec discussion: Open an issue with the spec label
  • SDK improvements: Pick up issues in language-specific repos
  • Framework adapters: Port existing adapters or create new ones
  • Documentation: Improve guides, add examples, fix typos
  • Testing: Expand conformance tests across languages

See CONTRIBUTING.md for details.

Prioritization

Roadmap priorities are set by maintainers based on:

  1. Foundation submission requirements
  2. Community demand (GitHub issues, discussions)
  3. Cross-language consistency needs
  4. Security and stability improvements

To influence priorities, open an issue or join the discussion on existing ones.