amadan
Retire stale suite pin and CI-blocker claims
Co-Authored-By: Codex <noreply@openai.com>
3 files changed,
+7
−21
docs/superpowers/specs/2026-09-03-memoria-design.md+7 −6internal/memoria/sibling/policy.go+0 −8internal/memoria/sibling/policy_test.go+0 −7
CI passed — run details
diff --git a/docs/superpowers/specs/2026-09-03-memoria-design.md b/docs/superpowers/specs/2026-09-03-memoria-design.md| index 5d686a0..1f489bd 100644 |
| --- a/docs/superpowers/specs/2026-09-03-memoria-design.md |
| +++ b/docs/superpowers/specs/2026-09-03-memoria-design.md |
| @@ -13,10 +13,11 @@ draft-5 findings, which are still unfixed and still listed in §13. |
| **revision 7, commit `2b78680`** — with two amendments adopted since and |
| not yet reflected here as a version bump: revision 8 (the module's |
| importability, now closed) and **revision 10, which adds `AHEAD`** (§4.1). |
| -The module this repository pins is `60b01a8`, which is revision 8's merge. |
| +The module this repository pins is `1ac4323`, containing revision 8 plus |
| +the reviewed S2 required-field and HTTPS transport fixes. |
| Gate 9 fails a spec more than one revision behind, so this citation is |
| -owed a bump the moment the suite's branches merge; they cannot, because |
| -suite CI is unconfigured (§13). Rulings 1, 3, 4, 6, 7, 9, 14 and 15 are |
| +owed a bump when the remaining doctrine branches merge. Suite CI is now |
| +configured and green; the AHEAD branch has not merged. Rulings 1, 3, 4, 6, 7, 9, 14 and 15 are |
| cited and never restated (suite ruling 7) — 15 at §5's custody mark, which |
| is where "only the `team` rung is team-visible, so custody keys on the rung |
| and never on the link" decides what memoria may hold. Not consumed yet: the hand-off |
| @@ -1022,14 +1023,14 @@ the sibling answered". Three wrong homes, so a fourth value. |
| Suite revision 7 had ruled the case `UNKNOWN`; **revision 10 replaces |
| that with `AHEAD`**, in the shape memoria proposed and with one half |
| declined — see below. The module carries it on an unmerged branch, so the |
| -version this repository pins (`60b01a8`) still has four constants. |
| +version this repository pins (`1ac4323`) still has four constants. |
| **So the wire shape above is four values today and five when the module |
| ships**, and every reference to `AHEAD` in this spec is written against the |
| five-value design. That is a shipping lag, not a disagreement, and the |
| distinction matters: nothing here needs redesigning, and nothing here can |
| -be built until the module lands. Suite CI is unconfigured, which is what |
| -holds it (§13). |
| +be built until the AHEAD module branch lands. Suite CI is now configured; |
| +the remaining dependency is the unmerged AHEAD implementation (§13). |
| **How it got settled, because the route matters more than the outcome.** |
diff --git a/internal/memoria/sibling/policy.go b/internal/memoria/sibling/policy.go| index 2a1a924..9b217e5 100644 |
| --- a/internal/memoria/sibling/policy.go |
| +++ b/internal/memoria/sibling/policy.go |
| @@ -115,14 +115,6 @@ func Decide(a suite.Authorization) Disposition { |
| // aheadNotYetOnTheWire is the fifth row of §4.1's table, and it is not a |
| // constant this client can switch on. |
| // |
| -// The module this repository pins carries four values. `AHEAD` is adopted — |
| -// suite doctrine revision 10, settled 2026-09-06 on memoria's own argument |
| -// — and lands on a branch that has not shipped, held by suite CI being |
| -// unconfigured (§13). Until it does, a sibling answering "AHEAD" is folded |
| -// to UNKNOWN by the module and withheld loudly here: **safe, and lossy.** |
| -// What is lost is the marking for re-announce, which is the collapse the |
| -// fifth value was cut to prevent. |
| -// |
| // This constant exists so a test can assert the lag is still a lag. See |
| // TestAheadIsStillAShippingLag: it goes red on the day the module gains the |
| // value, which is the day `Decide` owes it an arm and this file owes the |
diff --git a/internal/memoria/sibling/policy_test.go b/internal/memoria/sibling/policy_test.go| index bd95a8d..8ec4bb1 100644 |
| --- a/internal/memoria/sibling/policy_test.go |
| +++ b/internal/memoria/sibling/policy_test.go |
| @@ -210,13 +210,6 @@ func TestTheNoticesNameTheAppAndTheShapeOfTheLoss(t *testing.T) { |
| // **AHEAD is adopted and not yet on the wire, and this is the tripwire.** |
| // |
| -// §4.1: suite doctrine revision 10 settled `AHEAD` on 2026-09-06, on |
| -// memoria's argument, and the module carries it on a branch that has not |
| -// shipped — held by suite CI being unconfigured (§13). The version this |
| -// repository pins has four constants. So a sibling answering "AHEAD" today |
| -// is folded to UNKNOWN by the module and withheld loudly here: safe, and |
| -// lossy. What is lost is the marking for re-announce. |
| -// |
| // A shipping dependency nothing checks is a shipping dependency nobody |
| // notices has arrived. **This test goes red the day the module gains the |
| // value** — DecodeS2 will stop folding it — and whoever bumps the |