Skip to content

AgentCollab v1.0.0

Choose a tag to compare

View all tags
@CaptainMcCrank CaptainMcCrank released this 13 Aug 20:55
· 22 commits to main since this release
v1.0.0
b9f8b16

First public release of AgentCollab — a cryptographically verifiable collaboration protocol for AI agents sharing a project: handoff envelopes, inventory-before-edit, conflict negotiation, specialist delegation, and a hash-manifest handshake that lets two agents prove they are operating under the same, unmodified rules.

Protocol identity

AgentCollab/1.0.0#sha256:c031fa97e660faac

Full bundle root and per-file SHA-256 hashes: PROTOCOL_MANIFEST.yaml, signed by the maintainer (detached SSH signature, namespace agentcollab-manifest).

Maintainer signing key

Out-of-band anchor: patrickmccanna.net/agentcollab — serves this fingerprint, a machine-readable allowed_signers file, and verification instructions from a domain this repository does not control.

Pin this fingerprint from a source other than the repo itself — that is what makes L2 verification mean "unmodified from upstream" (see Handshake.md §7):

ED25519 SHA256:QzsA94AxteAb+u4NZXUuZltfXT6JOhdkALs3onZqF2U  (patrickmccanna@gmail.com)

Verify this release

git clone --branch v1.0.0 https://github.com/CaptainMcCrank/AgentCollab
cd AgentCollab
./bin/acp-verify.sh          # expect: VERIFIED [L2] AgentCollab/1.0.0#sha256:c031fa97e660faac
./tests/run-tests.sh         # expect: RESULT pass=10 fail=0

What's in the release

  • protocol/Agent_Collaboration_Protocol.md — the core spec: CONTEXT-HANDOFF envelopes, INVENTORY-first receivers, CONFLICT/RECONCILE negotiation, DELEGATE
  • protocol/Handshake.md — the agreement mechanism: bundle root computation, protocol ID, verification levels L0/L1/L2, mismatch resolution, signing, release procedure
  • protocol/Agent_Charter.md — the minimal per-agent declaration the protocol arbitrates between
  • bin/acp-id.sh, bin/acp-verify.sh — POSIX reference implementation (deps: sha256sum, ssh-keygen)
  • adapters/ — integration-profile template for binding the tool-agnostic interfaces (work tracker, session log, …) to your stack
  • tests/ — fixture suite proving the verifier rejects tampered docs, forged manifests, stale and untrusted signatures

The handshake proves integrity and authenticity of the rules — it cannot prove a model followed them. Every mechanism is labeled honestly (shell-enforced / instructed-only / deployment-enforceable) in the spec.

License: Apache-2.0

Assets 5
Loading