Skip to content

Durable rental journal for provider release across daemon restart #4972

Open

Description

@thymikee

Keep enough durable identity to settle a billable provider rental after the daemon exits.

ADR 0040

Required behavior

  • For a provider that supports reconciliation, persist its recoverable allocation key before a billable create. Record the exact provider instance and release intent before forgetting live ownership.
  • After registration on restart, restore the ending reservation before overlapping admission. Resume release by exact instance identity or resolve it when the provider proves absence.
  • If a provider cannot prove recovery, retain a fenced release unknown outcome for the operator.

Verification

Interrupt the daemon before identity arrives, after identity is recorded, and during release. Verify reconstruction of the reservation and release by exact identity. Verify that unknown release stays fenced.

Related work

Coordinate with ADR 0040 step 5 and the existing provider live and pending journals.

Use the ending reservation from step 5.

Activity

  1. apex-sentinel-staging commented on Nov 22, 2026

    @apex-sentinel-staging

    Apex Sentinel · Issue review

    Suggested label: feature

    The issue specifies new required behavior for persisting and restoring provider rental identity across daemon restarts, with verification steps and related ADR links, rather than reporting an existing broken behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions