https://github.com/capiscio/capiscio-rfcs
Request for Comments (RFCs) for CapiscIO protocols and standards. Proposals for AGCP, trust policies, agent identity, and the governance of autonomous agent systems.
https://github.com/capiscio/capiscio-rfcs
a2a agcp agent-to-agent autonomous-agents governance protocol rfc specification standards trust-policy
Last synced: 5 months ago
JSON representation
Request for Comments (RFCs) for CapiscIO protocols and standards. Proposals for AGCP, trust policies, agent identity, and the governance of autonomous agent systems.
- Host: GitHub
- URL: https://github.com/capiscio/capiscio-rfcs
- Owner: capiscio
- Created: 2025-12-05T16:13:42.000Z (7 months ago)
- Default Branch: main
- Last Pushed: 2026-01-10T19:30:46.000Z (5 months ago)
- Last Synced: 2026-01-11T05:45:32.597Z (5 months ago)
- Topics: a2a, agcp, agent-to-agent, autonomous-agents, governance, protocol, rfc, specification, standards, trust-policy
- Homepage: https://docs.capisc.io/rfcs/
- Size: 91.8 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: docs/CONTRIBUTING.md
Awesome Lists containing this project
README
# Capiscio RFCs
This repository contains the technical specifications and architectural decisions for the Capiscio platform.
## Active RFCs
| RFC | Title | Status | Version |
|-----|-------|--------|---------|
| [RFC-001](docs/001-agcp.md) | Agent Governance Control Plane (AGCP) | ✅ Approved | - |
| [RFC-002](docs/002-trust-badge.md) | Trust Badge Specification | ✅ Approved | v1.4 |
| [RFC-003](docs/003-key-ownership-proof.md) | Key Ownership Proof Protocol | ✅ Approved | - |
| [RFC-004](docs/004-tchb-transaction-hop-binding.md) | Transaction and Hop Binding (TCHB) | 📝 Draft | v0.3 |
| [RFC-005](docs/005-policy-definition-distribution-enforcement.md) | Policy Definition, Distribution, and Enforcement (PDEP) | 📝 Draft | v0.2 |
## RFC Process
1. **Draft:** Open a PR with a new RFC in `rfcs/`
2. **Review:** Discussion happens in the PR
3. **Approved:** Merged to main
4. **Superseded:** Noted in the RFC header with pointer to replacement
## RFC Numbering
- `001-099`: Core Architecture
- `100-199`: Protocol Specifications
- `200-299`: SDK & Integration
- `300-399`: Security & Trust
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md) for RFC authoring guidelines.