pending / stagingno direct publish
Submit a capability
AgentMaps prioritizes projects with clear setup instructions, visible permission boundaries, source links, and evidence that a developer can safely evaluate.
Review flow
- 1. Candidate submitted.
- 2. Metadata normalized into AgentMaps schema.
- 3. L1-L4 verification harness runs where safe.
- 4. Data QA reviews risk flags before publication.
No direct publish
Submissions only enter the review queue. Public catalog entry still requires normalization, verification, risk review, and a final publish review.
Runtime, approvals, and recovery
- Token, write, shell, external network, or local file access requires human review.
- Thin evidence stays in manual review and never auto-enters the public catalog.
- Missing server configuration should block preview/production submission instead of pretending success.