amadan
S3 change index spec: record Paul's rulings R3 (30-min backstop) and R4 (old CLIs at backstop) (#336)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+4
−1
docs/superpowers/specs/2026-10-21-s3-change-index-design.md+4 −1
CI cancelled — superseded by a newer push — run details
CI log
=== gate === cd launchctx && go vet ./... && go test ./... -count=1 ok amadan.net/carlos/platform.git/launchctx 0.011s ? amadan.net/carlos/platform.git/launchctx/controlname [no test files] ? amadan.net/carlos/platform.git/launchctx/wireid [no test files] go vet ./... gofmt -l .: clean go test ./... -count=1 -timeout 30m amadan: job cancelled — a newer push superseded it
diff --git a/docs/superpowers/specs/2026-10-21-s3-change-index-design.md b/docs/superpowers/specs/2026-10-21-s3-change-index-design.md| index eefba204b..ce056e743 100644 |
| --- a/docs/superpowers/specs/2026-10-21-s3-change-index-design.md |
| +++ b/docs/superpowers/specs/2026-10-21-s3-change-index-design.md |
| @@ -51,6 +51,9 @@ per month. The causes, all on main at 3d444a1b: |
| - **R2.** Fix the change detection: writers record which app changed in |
| the bucket, readers re-read only what changed, a slow full walk remains |
| as the backstop. |
| +- **R3.** The backstop interval is 30 minutes (answer to §10 Q1). |
| +- **R4.** Old CLIs writing straight to the bucket converge at the backstop |
| + until operators update; the release notes say so (answer to §10 Q2). |
| ## 2. Goals and non-goals |
| @@ -331,7 +334,7 @@ process (#280). |
| Expected flagship S3: ~$50–90/month (storage $16, transfer ~$25, |
| litestream ~$26, requests ~$10–25), flat as apps are added. |
| -## 10. Questions for Paul |
| +## 10. Questions for Paul (answered 2026-10-21, see R3 and R4) |
| 1. **Backstop interval.** 30 minutes bounds staleness for old binaries and |
| failed bumps at ~$5/month. 15 minutes doubles that cost; 60 halves it. |