Skip to content

Implement precise verification reports and corruption refusal #20

Open
Open
Implement precise verification reports and corruption refusal#20
Labels
area:formatCanonical durable formats and decodingarea:identityLogical content identity and typed coordinatesarea:readReconstruction, streaming, and byte-range readsarea:recoveryCrash states, reconciliation, and recoveryarea:verificationIntegrity verification and corruption posturekind:implementationProduction implementation workkind:testTest infrastructure or failure-mode evidencepriority:P1Must fix before closing out the current milestone
Milestone
M4 — Retention, Verification & GC

Description

@flyingrobots
flyingrobots
opened on Jul 20, 2026

Outcome

Verify content and store structure at explicit depths, report exactly what was established, and refuse when evidence is missing, conflicting, or corrupt.

Dependencies

Blocked by #15, #16, and #17.

Acceptance criteria

  • Verification policy uses explicit enums rather than boolean flags.
  • Reports distinguish framing, checksum, chunk identity, layout identity, complete blob identity, catalog reachability, and retention-root verification.
  • Partial verification cannot be presented as complete verification.
  • Expected and observed identities, lengths, generations, or format versions are retained in typed failures where safe.
  • Missing content is distinguished from corrupt content and ambiguous conflicting content.
  • Verification never silently repairs, substitutes, quarantines, or rewrites physical state.
  • Every durable structural field has permanent corruption mutations.
  • Verification memory, I/O, and complexity are documented and bounded.
  • Reports contain no plaintext content, keys, or unbounded sensitive paths.
  • The Golden File Worldline corruption assertions pass.

Non-goals

  • Automatic repair.
  • Remote attestation or cryptographic proof systems.
  • Application-level trust decisions.
  • Garbage collection.

Activity

  1. flyingrobots
    added this to the M4 — Retention, Verification & GC milestone on Jul 20, 2026
  2. flyingrobots
    added
    kind:implementationProduction implementation work
    kind:testTest infrastructure or failure-mode evidence
    area:recoveryCrash states, reconciliation, and recovery
    area:verificationIntegrity verification and corruption posture
    on Jul 20, 2026
  3. coderabbitai
    added
    area:formatCanonical durable formats and decoding
    area:identityLogical content identity and typed coordinates
    priority:nextImmediate executable dependency for the active milestone
    area:readReconstruction, streaming, and byte-range reads
    on Jul 20, 2026
  4. flyingrobots
    removed
    priority:nextImmediate executable dependency for the active milestone
    on Jul 20, 2026
  5. flyingrobots
    added
    priority:P1Must fix before closing out the current milestone
    on Jul 30, 2026
  6. flyingrobots
    added a commit that references this issue on Sep 7, 2026

    Fix: bind observed retention state to this store's catalog and its ow…

    e398c5d
  7. flyingrobots
    added 2 commits that reference this issue on Sep 30, 2026

    Feat: explicit-depth verification reports for the reference view

    5a23238

    Feat: process-death crash matrix for the 21 migration phases

    65ed69e

  8. flyingrobots commented on Oct 1, 2026

    @flyingrobots
    flyingrobots
    on Oct 1, 2026
    OwnerAuthor

    Audit follow-up for T-21.1 / T-21.2. Tracker: #132.

    Treat this as the verification tracking parent for #114 (durable reports) and #115 (mutation evidence through reports). Reports must land before report-level mutation evidence. Other existing requirements remain owned here; grouping is not duplicate executable work.

    The audit source is docs/audits/completed-roadmap-2026-09-30.md on feature/roadmap-m4-tasks. Original acceptance criteria and definitions of done remain authoritative. This comment records remaining work and links existing ownership; it does not assert that the issue is complete or change its recorded dependencies.

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:formatCanonical durable formats and decodingarea:identityLogical content identity and typed coordinatesarea:readReconstruction, streaming, and byte-range readsarea:recoveryCrash states, reconciliation, and recoveryarea:verificationIntegrity verification and corruption posturekind:implementationProduction implementation workkind:testTest infrastructure or failure-mode evidencepriority:P1Must fix before closing out the current milestone

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions