Files
seaweedfs/sw-block
pingqiuandClaude Opus 4.7 80036404ce T4d planning + G-1 doc landing (architect Path B + Issue 2(a) ratification)
Lands four T4d planning artifacts together:

1. v3-phase-15-t4d-3-g1-v2-read.md (NEW)
   T4d-3 G-1 V2 read v0.2, QA-signed in conversation 2026-04-25.
   Per architect Issue 2(a) ratification: G-1 docs land first;
   implementation references the committed hash. Future T4d-3
   commits should reference this commit's sha via:
     Refs G-1 sign: <this-commit-sha>

2. v3-phase-15-t4d-forward-carry-checklist.md (NEW)
   v0.2 — 19 active T4a/T4b/T4c invariants with risk grades and
   per-batch focus rows. T4d-3 close gate inscribed
   (CARRY-T4D-LANE-CONTEXT-001 option A or B); pre/with-T4d-3
   doc fixes recorded.

3. v3-phase-15-t4d-qa-scenario-catalogue.md (NEW)
   v0.1 — 9 QA component-scope scenarios mirroring T4c QA
   Stage-1 discipline. 10 framework primitives surfaced for
   sw's batch PRs.

4. v2-v3-contract-bridge-catalogue.md (UPDATED)
   §3.3 inscriptions for T4d-locked invariants:
     - INV-REPL-NO-PER-LBA-DATA-REGRESSION (round-43)
     - INV-REPL-RECOVERY-STALE-ENTRY-SKIP-PER-LBA (round-43)
     - INV-REPL-RECOVERY-COVERAGE-ADVANCES-ON-SKIP (round-44)
     - INV-REPL-LIVE-LANE-STALE-FAILS-LOUD (round-44)
     - INV-REPL-RECOVERY-COVERAGE-RESTART-SAFE (Option C)
     - INV-REPL-LANE-DERIVED-FROM-HANDLER-CONTEXT (Q2 + round-46)
     - INV-REPL-TRANSPORT-STORAGE-CONTRACT-ONLY (Q1+Q3 + T4d-1
       strengthening)
     - INV-REPL-CATCHUP-FROMLSN-IS-REPLICA-FLUSHED-PLUS-1
       (T4d-3 G-1 §5)
     - INV-REPL-CATCHUP-FROMLSN-FROM-ENGINE-STATE-NOT-PROBE
       (T4d-3 G-1 §5)
     - CARRY-T4D-LANE-CONTEXT-001 (named carry, T4e/post-G5)
   INV-REPL-CATCHUP-WITHIN-RETENTION-001 status updated:
   T4c downgrade → T4d-2+T4d-3 un-pin path.

Process rule inscribed (architect 2026-04-25):
G-1 sign docs land in seaweedfs FIRST; sw implementation in
seaweed_block references the committed G-1 hash via
"Refs G-1 sign: <sha>" per mini-plan §7.1 procedural binding.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-25 22:26:21 -07:00
..

sw-block

Private WAL V2 and standalone block-service workspace.

Purpose:

  • keep WAL V2 design/prototype work isolated from WAL V1 production code in weed/storage/blockvol
  • allow private design notes and experiments to evolve without polluting V1 delivery paths
  • keep the future standalone sw-block product structure clean enough to split into a separate repo later if needed

Suggested layout:

  • design/: shared V2 design docs
  • prototype/: code prototypes and experiments
  • .private/: private notes, phase development, roadmap, and non-public working material

Repository direction:

  • current state: sw-block/ is an isolated workspace inside seaweedfs
  • likely future state: sw-block becomes a standalone sibling repo/product
  • design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths