mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-10 18:16:18 +00:00
pingqiuandClaude Opus 4.7
88dcd49d67
Predecessor docs for the T3 batch, retained here for audit trail. The closure report (`v3-phase-15-t3-closure-report.md`), contract bridge catalogue, and BUG-005/006 artifacts already landed in commits `4127e5136` + `6e196885e`; this commit fills the docs those closure artifacts reference back to. Landed: v3-phase-15-t3-port-plan-sketch.md T3 umbrella sketch (rev-2.1, three-signed) v3-phase-15-t3-port-audit.md T3.0 port audit + Addendum A (QA-signed) v3-phase-15-t3a-mini-plan.md T3a scope + sign-off (CLOSED 0e1595c) v3-phase-15-t3b-mini-plan.md T3b scope + sign-off (CLOSED 72d0d40) v3-phase-15-t3c-mini-plan.md T3c scope + sign-off (CLOSED 829c6a9) Total 1,346 lines of doc; no code impact. 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