Skip to content

Maintain incremental control-state projections from durable history #1373

Description

@Brad-Edwards

Control-history appends and effect processing repeatedly scan accumulated history, producing quadratic cumulative work as a run grows.

Acceptance criteria

  • Maintain the state needed for crossing admission, provider causal state, and pending-effect processing incrementally under the revised commit and occurrence contracts.
  • Keep immutable history authoritative. Define projection versioning, invalidation, reconstruction, and crash consistency without changing historical meanings.
  • Verify incremental state against a complete fold across accepted, refused, duplicate, and recovered operations, including incomplete commits.
  • Demonstrate that steady-state append/dispatch work no longer scales with unrelated accumulated history. Bound performance claims to the measured workload and disclosed active-state size.

Prerequisites: #1369.

References: Diagnosis.

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

    area:runtimeRuntime and control-plane codeenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions