Skip to content

Define reload, health, and failure semantics #11

Description

@ian-pascoe

Question

What state transitions and concurrency rules govern startup, accepted Host Configuration Snapshot replacement and PostgreSQL cluster mismatch, revisioned host and Organization state changes, Capability Source discovery under host-owned, Organization-owned, or Account-owned credentials, Project Configuration upload and replacement, Project Context lease renewal and expiry, source reconnect, degraded health, last-valid projection retention, Client Surface changes, in-flight calls, and shutdown while isolating failures between Organizations, Accounts, and Capability Sources and preserving the context on which each request began?

Activity

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