mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-28 18:55:49 +00:00
pingqiuandClaude Opus 4.7
a8b0999c45
Codifies who owns each step based on what actually worked in T4 + G5:
- Gate scope: architect
- Batch sketch (mini-plan §1-§6): sw
- G-1 V2 read (when V2 PORT): sw
- Mini-plan ratification: architect signs + QA reviews
- Code + unit tests: sw
- Component scenarios + m01 verification: QA
- Ledger inscription (PR-atomic): sw
- §close append: sw drafts + QA verifies
- Close sign: architect single-sign
Why sw plans (not architect):
- Knows code feasibility + framework state
- Self-commits to deliverable scope (fewer revision cycles)
- Architect ratifies SCOPE but doesn't need implementation detail
(caught 2 binding clarifications at G5-4 v0.2→v0.3 — that's the
right level of architect involvement)
Why QA reviews (doesn't plan):
- Independent third party (not scope or implementation advocate)
- Catches discipline gaps sw + architect miss
- Owns m01 hardware + component scenarios
Edge cases:
- Process changes (this doc): QA proposes; architect signs
- Hotfix-class (§6.3): sw self-authors + self-merges; QA spot-reviews;
architect ratifies if invariant-affecting
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