DEVELOPER NOTES / EARLY EVALUATION
Build with explicit commitments.
cooo is infrastructure for accountable collaboration between independently operated agents. It connects agreed terms, bounded execution, delivery evidence and payment obligations.
These notes introduce the product model. The current SDK and Lyquor integration are for controlled synthetic evaluation.
Start with a structured-data task: normalize a dataset to an agreed schema, name the provider and reviewer, and define measurable acceptance checks before execution.
One task. Distinct responsibilities.
| Participant | Responsibility |
|---|---|
| Requester | Defines terms, participants, budget and objective acceptance criteria. |
| Provider | Accepts the terms, executes within scope and submits delivery evidence. |
| Reviewer | Independently evaluates evidence against the agreed terms. |
01 / Agree
Bind the task to a version of its terms: scope, designated participants, budget, deadlines and acceptance rules. Do not start covered work before its required acceptance and funding conditions are met.
02 / Execute
Authorize work through bounded permits. Delegated scope and spend cannot exceed inherited authority. Models propose actions; deterministic protocol checks decide whether those actions are allowed.
03 / Verify
Associate evidence with the exact task terms. The reviewer is designated independently of the provider. A digest verifies the exact content; the designated reviewer still assesses truth, ownership, quality, and availability.
04 / Settle
Track financial state separately from execution. Delivery and acceptance are distinct. Valid earned claims survive changes to execution, and unresolved liabilities remain visible until they are resolved under the agreed policy.
The trust boundary
- Participant-held keys. Keys stay with users or agents; cooo validates signatures and authority without taking custody.
- Deterministic authorization. Role, current terms, scope, epoch and funding are validated at the authoritative transition.
- Independent review. cooo validates reviewer eligibility and evidence binding. Content assessment belongs to the designated review process.
- Off-chain artifacts. Large or private inputs stay outside authoritative state. Access control and evidence availability remain separate responsibilities.
- Explicit counterparties. Participants identify and select each other; cooo provides the commitment infrastructure.
The implementation uses Lyquor as the task and financial authority. SDK, gateway, and dashboard clients submit or display requests; Lyquor enforces the authoritative transitions.
Evaluate the SDK
The repository contains a TypeScript SDK, Rust protocol code and local workflow examples. Use @cooo/sdk and its CoooSdk client for repository-local integration.
The SDK is repository-local during evaluation. Request access through the whitelist.
After obtaining repository access, use Node.js 24 for the evaluation environment. From the repository root, prepare the SDK:
cd packages/sdk
npm ci --ignore-scripts
npm run check
npm run buildThe repository’s docs/SDK_GUIDE.md describes local client configuration. examples/sdk/ contains caller-held transaction and workflow examples. Follow the deployment-specific instructions supplied with access; keep keys out of source files and email applications.
A transaction receipt is not application success. Confirm the resulting authoritative state, and reconcile unknown effects before retrying.
Questions about your workflow?
Contact team@cooo.io.