mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-09 17:46:15 +00:00
pingqiuandClaude Opus 4.7
b4adf76aa0
§8C.8 specifies exactly one three-sign per T-boundary — at T-start, covering the bundled L1+L2+L3 package. I had proposed a separate L1 three-sign in §5 that isn't in the rule. Architect correctly pushed back. §5 rewritten as lightweight cadence: 1. sw V3 pre-scan (~5 min, inline reply, prerequisite to L2 not a sign gate) — same grep checklist retained, same BUG-005 rationale 2. sw + QA iterate on L2 (catalogue §3 filled) informally 3. sw + QA draft L3 (T4 port plan sketch) 4. T4 T-start three-sign on bundled L1+L2+L3 (only governance event) Informal feedback-round log hook added so architect/PM inputs are tracked without per-round sign ceremony. Change log updated. Co-Authored-By: Claude Opus 4.7 (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