mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-07-29 11:33:25 +00:00
pingqiuandClaude Opus 4.6
58aa842802
7-area acceptance matrix mapping current state vs product requirements: write/durability contract, fresh replica bootstrap, host observation completeness, serving/publish alignment, snapshot/rebuild convergence, adapter consistency, test contract alignment. Each item marked with: current state, required for product, blocks T6/T7, best test level. Priority ordered into must-close-before-Stage-1, should-close-before-Stage-2, and can-close-after-T6/T7. Key diagnosis: architecture-complete, execution-incomplete. The engine thinks like a product; the data plane still behaves partly like a prototype. The gap is end-to-end contract closure. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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-blockproduct structure clean enough to split into a separate repo later if needed
Suggested layout:
design/: shared V2 design docsprototype/: 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 insideseaweedfs - likely future state:
sw-blockbecomes a standalone sibling repo/product - design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths