Copy and reduce
Start from the example, rename every identity, and declare only capabilities your fixture can prove.
ADAPTER API 1.0 · ACP V1
Connect an ACP agent.
Keep the boundary visible.
Point a strict local manifest at an already-installed ACP v1 process. SwiftAgent reuses its workspace-scoped client, contract suite, receipts, and capability-aware UI—without importing plugin code or auto-downloading an executable.
CONTRIBUTOR CONTRACT
Prove before declaring.
The kit includes a fake agent, JSON schema, event fixture, security checklist, compatibility template, cancellation/resume checks, and a receipt-producing harness.
PROCESS BOUNDARY
Configuration, not installation.
The manifest supplies literal argv and a bounded environment allowlist. It cannot run a shell, replace a built-in ID, self-assign verified trust, download code, or silently update an executable.
FIRST ADAPTER
Run the contract
Exercise new session, declared events, resume, cancellation, limits, and failure isolation without network access.
Review locally
Install explicitly, restart, inspect the Local custom badge, and submit redacted evidence if you want community review.
TRUST IS SEPARATE
A passing fixture is not endorsement.
Every manifest-loaded integration remains Local custom. Community verified requires exact contract evidence, security review, distribution provenance, a named owner, and repository-assigned metadata. SwiftAgent never auto-installs from a catalog.
Submit a compatibility report