Skip to content

[CA-01-S2] Persist and recover causal-anchor admissions through the WAL #663

Closed
Closed
[CA-01-S2] Persist and recover causal-anchor admissions through the WAL#663
Labels
coreEcho Core TechnologiesenhancementNew feature or requestpriority:highMethod priority high.runtimeRuntime coretaskSmall, 1–3h tasktype:enhancementMethod work type enhancement.
Milestone
CA-01 - Trusted causal anchor admission

Description

@flyingrobots
flyingrobots
opened on Jul 14, 2026

Goal

Give causal-anchor admission a canonical WAL transaction and recovery path.

Acceptance criteria

  • The WAL has explicit causal-anchor admission transaction and record kinds with stable numeric codes.
  • One committed transaction atomically records the canonical anchor and its Echo admission receipt.
  • Payload codecs reject truncation, trailing bytes, malformed enum values, and duplicate required frames.
  • Recovery returns only fully committed, internally consistent admissions.
  • A failed WAL commit yields no admitted anchor result.
  • Deterministic restart and corruption witnesses cover the new record.

Activity

  1. flyingrobots
    added this to the CA-01 - Trusted causal anchor admission milestone on Jul 14, 2026
  2. flyingrobots
    added
    runtimeRuntime core
    coreEcho Core Technologies
    priority:highMethod priority high.
    type:enhancementMethod work type enhancement.
    on Jul 14, 2026

  3. coderabbitai commented on Jul 14, 2026

    @coderabbitai
    coderabbitaibot
    on Jul 14, 2026 – with coderabbitai
    Contributor
    🔗 Related PRs

    #358 - feat(core): add admission evidence boundaries [merged]
    #379 - feat(core): commit runtime WAL ACK evidence [merged]
    #598 - feat(warp-core): add filesystem WAL failure atomicity [merged]
    #609 - feat(warp-core): project WAL recovery evidence [merged]
    #618 - Lock retained evidence crosswalk [merged]

    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan
    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
  auto_enrich:
    enabled: false

    💬 Have feedback or questions? Drop into our discord!

  4. coderabbitai
    added
    enhancementNew feature or request
    taskSmall, 1–3h task
    on Jul 14, 2026

  5. flyingrobots commented on Jul 15, 2026

    @flyingrobots
    flyingrobots
    on Jul 15, 2026
    OwnerAuthor

    Implemented in 5e63da9 and hardened in 75ac3b2. Causal-anchor admission has stable WAL transaction/record kinds, atomic fact+receipt commit, strict codecs, committed-only recovery, sealed reconstruction evidence, and restart/corruption/failure witnesses.

  6. flyingrobots
    closed this as completedon Jul 15, 2026
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

    coreEcho Core TechnologiesenhancementNew feature or requestpriority:highMethod priority high.runtimeRuntime coretaskSmall, 1–3h tasktype:enhancementMethod work type enhancement.

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions