SteadyDoAPI reference

Agent operating guide

  1. Call getCapabilities and getWorkspaceSummary before planning mutations.
  2. Follow allowedActions and typed links; never invent endpoint names or parse opaque IDs/cursors.
  3. Read the canonical resource and strong ETag before a write. Send If-Match; on 412 reread, reconcile, and retry.
  4. Send an idempotency key for creates, duplicates, divides, scoped template applies, bulk actions, and destructive changes.
  5. Preview non-obvious or destructive effects. Confirmation tokens expire after ten minutes, are single-use, and are bound to actor, API key, operation, resource, aggregate version, and requested scope.
  6. Treat templates as future-item defaults. Never imply that editing a template changed existing items; use preview and scoped apply.
  7. Treat company order defaults as future-order defaults.
  8. Mutate canonical tasks/items/orders, then reread computed Home, Next Up, Attention, or Completed projections.
  9. Stop for user intent before permanent deletion or materially broad template application.
  10. Never disclose, log, echo, or persist API keys.

All scopes listed on an operation are conjunctive. Key creation/rotation can preserve or narrow the caller's scopes, never widen them; successor expiry cannot outlive the caller.