Sample transfer
The founding scenario: one person shares a competitor research workflow with another person, on a separate account, and the receiving side checks the exact package before adopting it. The steps below are the states the live service moves through. Run it yourself with two accounts, or read the steps first.
Step 1
Package the capability
The sender's agent performs a competitor research workflow. The sender packages it with the sample action: the instructions, an example output, and the test manifest from the competitor-research example, with a manifest that records the tools it needs and a digest of the exact bytes.
Transfer state: Capability created, version 1.0.0
Step 2
Review and approve the exact package
The sender reads every file and the secret scan findings, then approves the transfer against the package digest. Approval moves the transfer from DRAFT to OFFERED and creates an invitation link that expires in 7 days. The token is shown once; only its hash is stored.
Transfer state: DRAFT, then OFFERED
Step 3
The recipient opens the invitation
A second person, on their own account, opens the invitation link. The offer page shows who sent it and what the capability does, with no package contents. Receiving moves the transfer to RECEIVED; reading the package moves it to INSPECTED.
Transfer state: OFFERED, then RECEIVED, then INSPECTED
Step 4
Verification runs against the received bytes
Verification checks the manifest against the schema, the package rules, the recomputed digest against the recorded digest, the secret and policy scan, and compatibility with the recipient's stated environment. Behavioral checks run only when a case carries fixture documents; the hosted sample package's public cases describe their sources in prose, so a hosted run reports behavioral NOT_TESTED and names the gap. The receipt records each result, including what did not run.
Transfer state: Verification NOT_STARTED, then PENDING, then VERIFIED or FAILED
Step 5
The recipient decides
Adoption is a separate approval by the recipient, recorded against the digest and the receipt. Accepting moves the transfer to ACCEPTED and the recipient can download the exact approved package. Rejecting and revoking are available at the states the protocol allows.
Transfer state: INSPECTED, then ACCEPTED
Checking the behavioral tests locally
The reference evaluation in the project repository runs the deterministic behavioral harness on the same sample package with synthetic fixture documents, plus a set of independent validation cases, and prints baseline and with-capability scores computed during the run. Reproduce it with npm run eval:reference in packages/verification after a build. This page quotes no scores: run the evaluation to see the current numbers.