oficina / home Public

Move the doctrine citation to revision 6, because it carried a claim as well as a citation

The doctrine is revision 6 at 7876689: S6 got §12 step 3 of its own and
A.4 now cites S6's specification rather than a fixture until that step
lands, which unblocks memoria today.

Gate 9's one-revision grace would have allowed staying at revision 5, and
the rulings this spec consumes are unchanged between 5 and 6. The
citation moved because §1.1 does not only name a revision — it asserts
that the commit is that repository's main, and revision 6 made that
assertion false. A claim about the world goes stale differently from a
citation, and that distinction is now written down where it applies.

§4's "the module's first step" needs no change: step 2 is still S1, S2
and S3, and the later renumbering does not reach it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Rk1LgZH74vJxLbQXraA6re

Paul Campbell pushed by paul@keymail.dev 1 month ago 4959d82d57d9dd5949e4b4aa76d2785ade95a812 parent 2b6b5a6

1 file changed, +11 −3

docs/superpowers/specs/2026-09-05-activity-pull-design.md +11 −3

CI passed — run details

diff --git a/docs/superpowers/specs/2026-09-05-activity-pull-design.md b/docs/superpowers/specs/2026-09-05-activity-pull-design.md

index a5cdedf..4ee2f44 100644

--- a/docs/superpowers/specs/2026-09-05-activity-pull-design.md

+++ b/docs/superpowers/specs/2026-09-05-activity-pull-design.md

@@ -28,8 +28,8 @@ wrote enough of the resulting argument to no longer be independent, and it

says so itself. **A fresh reviewer is still required.**

**Coordinated with the suite sharing doctrine, 2026-09-05.** `oficina/suite`,

-`docs/superpowers/specs/2026-09-05-suite-sharing-doctrine.md`, revision 5 at

-`f627359`, adopts this design as **suite contract call 7** (its ruling 11). Five points

+`docs/superpowers/specs/2026-09-05-suite-sharing-doctrine.md`, revision 6 at

+`7876689`, adopts this design as **suite contract call 7** (its ruling 11). Five points

were settled with that session and are reflected below: the doctrine's §4.3

now carves out call 7 explicitly, the wire shape stays here rather than moving

into the contract module, the `roster_epoch` invalidation exception is scoped

@@ -108,9 +108,17 @@ the drift the doctrine exists to stop. This section is that citation. Nothing

below is restated here in its own words.

**Document:** `oficina/suite`, `docs/superpowers/specs/2026-09-05-suite-sharing-doctrine.md`,

-**revision 5**, commit **`f627359`**. Verified: that commit is `main` in that

+**revision 6**, commit **`7876689`**. Verified: that commit is `main` in that

repository and the file is present in its checkout.

+**Why this moved off revision 5, when it did not have to.** Gate 9 allows a

+consumer to sit one revision behind so it is not chased on every edit, and the

+rulings this spec consumes are unchanged between 5 and 6. The citation moved

+anyway because it does not merely name a revision, it asserts that the commit

+is that repository's `main` — and revision 6 made that assertion false. **A

+claim about the world goes stale differently from a citation**, and this

+section carries both.

| Suite ruling | What this spec takes from it |

|---|---|

| 1 | The team is the boundary; a team's instances across apps are one trust domain. This is why ruling 6's per-team scoping is the correct shape and not a narrowing. |