048-run-operations

Typed run operations under one controller lease, recorded in the run record

Lifecycle approvedImplementation completeVerification unknownQualification unknown

Gives a run three typed operations, attempt.retry, attempt.continue and attempt.abort, submitted by one controller holding a lease. Each carries an idempotency key and the run version it was decided against; each request and its outcome append to spec 003's hash-linked run record, durable and uncapped, so replaying the record reproduces the run's state. A reconnecting controller reads events from a cursor over the record. The one live slot of spec 003 section 3.7 is held or released explicitly by each operation.

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
      "nature": "additive",
      "spec": "003-work-and-run-semantics",
      "unit": {
        "kind": "directory",
        "path": "crates/statecraft-run/"
      }
    }
  • extends
    {
      "nature": "additive",
      "spec": "006-command-surface",
      "unit": {
        "kind": "directory",
        "path": "crates/statecraft-cli/"
      }
    }
  • extends
    {
      "nature": "additive",
      "spec": "005-acceptance-and-evidence",
      "unit": {
        "kind": "directory",
        "path": "crates/statecraft-acceptance/"
      }
    }

Source headings

  1. 048: Typed run operations under one controller lease
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 The three operations
  6. 3.2 One controller lease
  7. 3.3 Idempotency and version
  8. 3.4 The record is the state
  9. 3.5 The live slot
  10. 3.6 The event cursor
  11. 4. Out of scope
  12. 5. Resolved decisions
  13. Verification

Frozen anchors

No frozen anchors declared.