Developer Manual / public docs
Build, test, recover, and operate.
For a first action, follow the first-action guide. Use this Manual for the host decisions and tests behind it, with the API Reference for exact signatures.
Recommended reading order
- Run the current example, then read architecture, prerequisites, and package roles
- Adapt one Actions operation with independent verification and a matching permitted claim
- Test host admission, replay and partial effects, then add persistence and recovery
- Use troubleshooting, operations, authority, and versioning as deeper references
Architecture and responsibilities
Understand host, package, provider, verifier, and authority boundaries.
Read chapter →Prerequisites
Confirm the current package set, access boundary, and host responsibilities.
Read chapter →Package guide
Choose package roles and package-root imports.
Read chapter →Grounding and authorization
Bind proposals to referents, context, identity, scope, and policy.
Read chapter →Execution and reconciliation
Separate acknowledgment, effect truth, and safe recovery.
Read chapter →Provider adapters
Implement the host-owned mutation boundary.
Read chapter →Independent verifiers
Read authoritative state and classify bounded evidence.
Read chapter →Results and errors
Handle COMMITTED, DISPROVED, and UNKNOWN safely.
Read chapter →Persistence
Design host-owned records, leases, fencing, and CAS.
Read chapter →Operations
Separate tested behavior from host responsibility.
Read chapter →Testing and conformance
Test retries, loss, privacy, recovery, and bounded claims.
Read chapter →Troubleshooting
Diagnose failures without unsafe retries.
Read chapter →Versioning
Use the current package set and its compatibility limits.
Read chapter →Package execution currently uses preview access. See Patterns for established integration shapes.