oficina / suite Public

Two corrections the amendments found, and where each app half landed

Applying Appendix A to the four app specs turned up two defects in the
appendix itself.

A.1 said "add ruling 22" to the home spec. The home already has a ruling 22
— team selection is navigation state — so the number was taken before it was
ever used. GPT-6's review of revision 3 flagged the risk; checking the home
spec confirmed it. It landed as ruling 23.

The memoria citations are worse than a number. Decisions 13 and 14, gate 26
and §8.4 resolve only in memoria's unmerged tensorx-provider worktree at
8dfc3c9, not on its main at 5869e73 — so this document cites text that is
not where it says it is. Recorded as open in §14 and asked at
oficina/memoria discussion 1, with the ask that memoria say which baseline
is real. Either the citations move to the commit that carries them or the
claims come out. Nothing else in the doctrine depends on them.

Where §12 step 1 stands. Docs, Sheets and the home each have a
`suite-amendment` branch, pushed and described; A.2 also closes
oficina/docs discussion 33. memoria is a request rather than a branch,
because that repo has three locked worktrees and two of A.4's sections are
ones those sessions are plausibly editing. A.5 waits for calendar's first
screens, as the appendix already says.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Paul Campbell pushed by paul@keymail.dev 71fe55ac82541dd8ae289d262d807789be338889 parent 210312f
1 file changed, +14 −1
  • docs/superpowers/specs/2026-09-05-suite-sharing-doctrine.md +14 −1

Intent

Attributed to this commit: 231 g CO₂e (24758714 tokens). This is an attribution, not a measurement — usage counted from this commit's own marker forward to the next one on worktree-doctrine-corrections, never backward from it. A turn that produced more than one commit books all of its tokens to the last one, and a concurrent session on this branch can add to the same figure. Some of it was priced using the shared default rate, because no model-specific factor row exists yet for at least one model involved. The Carbon view has the repo total, which is never derived from this attribution.

diff --git a/docs/superpowers/specs/2026-09-05-suite-sharing-doctrine.md b/docs/superpowers/specs/2026-09-05-suite-sharing-doctrine.md
index fda9dc5..304dd32 100644
--- a/docs/superpowers/specs/2026-09-05-suite-sharing-doctrine.md
+++ b/docs/superpowers/specs/2026-09-05-suite-sharing-doctrine.md
@@ -1117,6 +1117,13 @@ change to where the list comes from.
answered in place and cited where they landed.
- **Pegamento filing.** §5.5's divergence from Pegamento §10.3, and
ruling 1's application of §1 to a suite, both to `carlos/pegamento`.
+- **memoria's citation baseline.** Four things this document cites —
+ decisions 13 and 14, gate 26 and §8.4 — resolve only in memoria's
+ unmerged `tensorx-provider` worktree at `8dfc3c9`, not on its `main` at
+ `5869e73`. The doctrine was read against a branch without saying so.
+ Asked at `oficina/memoria` discussion 1; when it answers, either the
+ citations move to the commit that carries them or the claims come out.
+ Nothing else in this document depends on them.
- **The `/auth/begin` dial.** rastrillo's sign-in classifier fetches
`.well-known/keymail` on the typed address's domain before the admission
gate, so an anonymous visitor makes any instance dial any host
@@ -1151,7 +1158,13 @@ copy. *(GPT-6 review, finding 14.)*
### A.1 `oficina/home`, spec §1 and §2.2
-Add ruling 22: *"The suite sharing doctrine (`oficina/suite`) binds this
+**Add ruling 23, not 22.** The home spec already has a ruling 22 — team
+selection is navigation state — so the number in this appendix was taken
+before it was ever used. Landed as 23 on `oficina/home` branch
+`suite-amendment`. *(GPT-6 review of revision 3, finding R3-12, confirmed
+against the home spec on 2026-09-05.)*
+
+Ruling 23: *"The suite sharing doctrine (`oficina/suite`) binds this
spec. The team is the boundary; the home owns identity, the team and the
membership roster; it never owns a per-item grant. Call 8, roster pull,
is added to §9."*