Roadmap
Current Phase
Agent Manifest is in its foundational stage. The v1.0 specification is published and frozen.
The priority is conceptual clarity, structural minimalism, and architectural coherence.
This project does not optimize for rapid feature expansion. It prioritizes structural stability over feature velocity.
Phase I — Foundation
- Consolidate core specification (JSON Schema stability)
- Refine examples across different risk/autonomy profiles
- Document design rationale and philosophical grounding
- Maintain strict separation between doctrine and implementation
No enforcement mechanisms. No runtime integrations. No ecosystem expansion.
Stability over velocity.
Phase II — Validation (Exploratory)
- Research lightweight validation tooling
- Explore schema linting utilities
- Collect structured feedback from early technical reviewers
- Evaluate real-world use cases
No commercial tooling. No compliance frameworks. No monetization strategy.
Observation before expansion.
Phase III — Extension (Conditional)
Only after architectural maturity:
- Optional validation CLI — an initial standalone validator exists in
agent-manifest-cli - Optional SDK references
- Optional integration patterns
- Optional registry concepts
Extensions will remain modular and non-intrusive.
The core specification will remain minimal.
Design Principle
Agent Manifest does not grow by accumulation. It grows by refinement.
Minimal surface area. Maximum clarity. Structural integrity before ecosystem scale.
Long-Term View
If agent autonomy becomes structurally significant in digital infrastructure, declarative authority frameworks may become necessary.
Agent Manifest positions itself as a foundational layer — not a runtime, not a product, not a platform.
Declarative Integrity — Future Direction
Agent Manifest currently defines a declaration layer — a candidate declarative primitive — and its structural foundations.
Future work may include formalization and automation of the Declarative Integrity Framework (DIF) as a validator layer.
Such a validator would:
- Evaluate manifest coherence and completeness
- Detect declarative failure zones
- Provide structured reporting outputs
- Remain execution-agnostic
- Operate independently from runtime systems
This potential evolution does not alter the normative specification contract.
Declaration precedes evaluation.
Evaluation precedes enforcement.
Architecture first. Adoption second. Monetization last.