013-remote-state-on-failed-attempts

Remote state on attempts that end without a stop (amends 003)

Lifecycle approvedImplementation completeVerification unknownQualification unknown

A separately reviewable amendment of approved spec 003 (R-16), chosen by the owner in R-28 for the gap spec 009 5.1 records: the runtime derives `possibly_continuing` only from cancellation, so an attempt whose request left the process and whose connection then failed is recorded as `finished` although remote work and charges may continue. This adds one field to the attempt report through which an adapter states that remote work may continue, and one derivation rule in the runtime. The `rustev.run/1` schema and every existing record's bytes are unchanged. Approved (A-07) and implemented.

Read the full pinned specification ↗

Relationships

depends on

amends

003-runtime-execution-and-evidence

Claimed units

extends

{
  "nature": "amending",
  "spec": "002-decision-contract-and-pure-core",
  "unit": {
    "kind": "directory",
    "path": "crates/rustev-core/"
  }
}

extends

{
  "nature": "amending",
  "spec": "003-runtime-execution-and-evidence",
  "unit": {
    "kind": "directory",
    "path": "crates/rustev-runtime/"
  }
}

extends

{
  "nature": "additive",
  "spec": "005-reference-backends",
  "unit": {
    "kind": "directory",
    "path": "backends/rustev-backend-rules/"
  }
}

extends

{
  "nature": "additive",
  "spec": "004-evaluation-and-replay",
  "unit": {
    "kind": "directory",
    "path": "crates/rustev-eval/"
  }
}

extends

{
  "nature": "additive",
  "spec": "001-boundaries-and-authority",
  "unit": {
    "kind": "file",
    "path": "Makefile"
  }
}

Source headings

013: Remote state on attempts that end without a stop (amends 003)
1. Purpose
2. Territory
3. Behavior
3.1 The attempt report
3.2 Runtime derivation
3.3 Compatibility
4. Out of scope
5. Observable negative cases
Acceptance
Implementation record
Verification

Frozen anchors

No frozen anchors declared.