You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ACI is an open spec for describing organizations to autonomous agents through machine-readable contracts. We are one independent implementation away from v1.0, and we want to make it easy for you to be that implementation.
The v1.0 gate: three independent implementations. We have the reference implementation (aci-spec + aci_validator) and we are looking for implementations built by other people, in other languages, against the published spec.
Build a small validator or explorer for ACI manifests in a language of your choice (JS/TS, Rust, Go, Java, anything)
Validate the examples and report any ambiguity you hit
That is the whole ask. You do not need to join anything, sign anything, or coordinate with us. Build it in the open, link it in this discussion, and it counts toward the v1.0 gate. We will list every implementation in the Independent Implementation Tracker.
Why now: the community feedback window is open until 2026-09-15, and the MCP governance space is moving fast. This is the moment to shape the standard before it freezes.
Questions welcome in this discussion. If you want the absolute smallest entry point, start with the examples and tell us what is unclear - that feedback is as valuable as a full implementation.
@hello-urvesh - noticed you forked the MCP governance risks framework we contributed to (Automating Evidence Collection appendix, PR #6). If ACI or the AIP/AJSON stack is adjacent to your LLM security work, this is an open door. No pressure either way.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
ACI is an open spec for describing organizations to autonomous agents through machine-readable contracts. We are one independent implementation away from v1.0, and we want to make it easy for you to be that implementation.
The v1.0 gate: three independent implementations. We have the reference implementation (aci-spec + aci_validator) and we are looking for implementations built by other people, in other languages, against the published spec.
A good first task (sized for one evening):
That is the whole ask. You do not need to join anything, sign anything, or coordinate with us. Build it in the open, link it in this discussion, and it counts toward the v1.0 gate. We will list every implementation in the Independent Implementation Tracker.
Why now: the community feedback window is open until 2026-09-15, and the MCP governance space is moving fast. This is the moment to shape the standard before it freezes.
Questions welcome in this discussion. If you want the absolute smallest entry point, start with the examples and tell us what is unclear - that feedback is as valuable as a full implementation.
@hello-urvesh - noticed you forked the MCP governance risks framework we contributed to (Automating Evidence Collection appendix, PR #6). If ACI or the AIP/AJSON stack is adjacent to your LLM security work, this is an open door. No pressure either way.
All reactions