Join witnessed frozen review under custody and record continued-work policy

This commit is contained in:
Frank14f committed 2026-11-14 21:15:13 +08:00
1 parent f652534287
commit dbfb11ea42
10 files changed
+387

No files matched your search

+2
View File
@@ -8,3 +8,5 @@
- Preserve original data, failures, review limitations and immutable evidence. Do not label proposals as executed or reviewed results.
- Current E1 scope follows the standing continue-work authorization relayed in Slack `1794651141.035699` and Claude caps `1794651169.320839`: bounded CPU-only label-free preparation and synthetic checks may proceed after the count checkpoint, without another user approval loop. Total 16 CPU-hours / 25 GiB, at most 8 processes, per-job 30 min / 1.25 GiB tree RSS, at most 2000 registration pairs; the 10-part stage additionally stays sequential within 3 h / 5 GiB. Never read labels, fit models, use GPU, run pilot/full matrix, or exceed caps in this scope. See `docs/s2-e1-budget-checkpoint-2026-11-14.md`.
- Post-witness update (2026-11-14 21:12) supersedes treating the preceding E1-only scope as the entire remaining project scope. Follow the latest section of `docs/collaboration-stage-review-policy.md` and Claude Slack `1794661944.308269`: custody join, label-free copy calibration, k=3 per-route candidate count, bounded registration (up to 4000 pairs / 100 worker CPU-h / 16 workers), band review, component freeze, then coordinated S2 continuation. No repeated approval gates or reruns of completed review; preserve concrete execution limits and distinguish future stages from completed work. User preference: tens of CPU-hours alone are not a reason to block progress. No additional scientific task is implied by this preference.