oficina / docs Public

Branch suite-amendment at fad41bd, opened as the review record before merge, per AGENTS.md: "push and open the branch discussion, then squash-merge to main. Never merge without the discussion existing first."

What this is, honestly. A transcription made at merge time — not an independent review pass and not an approval. The branch's reasoning lives in its single commit message, and the squash would flatten it; this thread is where it survives. Opened by the memoria session, on Paul's instruction to merge the three suite-amendment branches (2026-09-05).

What the branch does

Appendix A.2 of the suite sharing doctrine. Four sections change and one is added: §8.2's boundary becomes the team rather than the instance (suite ruling 1), §9.1's second copy of the home call list is replaced by a citation, §9.2 keeps what is Docs' own, §11.2's conversion-API rejection stands with its edge now named under ruling 6, and a new §14a lists every consumed ruling.

It closes oficina/docs discussion 33, which asked for the boundary to be recorded rather than the rejection reversed.

The commit message, verbatim

Consume the suite doctrine: cite it, and stop restating it

Appendix A.2 of the suite sharing doctrine (oficina/suite, revision 4,
commit 210312f). Four sections change, and one is added.

§8.2 said "Sharing is membership" forbids data crossing the *instance*
boundary. The boundary is the team (suite ruling 1): a team's instances
across every app are one trust domain, so a same-team memoria may hold
team-visible documents under the suite contract, and Docs serves S1, S2, S3
and S8 wherever sibling consumer tokens are configured. That switch does not
depend on a home being present, so the wording is "wherever tokens are
configured" rather than "in suite shape" — Docs has to serve a lone memoria
before any home exists.

§9.1 listed five home calls. That list is the exact drift the doctrine was
written to stop: correct when written, and now wrong, because the home spec
has six calls with a seventh and eighth designed, and nothing made this copy
notice. Deleted in favour of a citation. The two things in it that are Docs'
own — the home hashes the address, and Docs never sends a title — stay.

§9.2 kept everything that is Docs' obligation and cited the rules those
obligations serve. The GPT-6 review of the doctrine warned about exactly
this: replacing a whole section with a citation loses locally-owned
behaviour along with the copies. The outbox mechanics, the guest tail, the
share dialog's disclosure and the full-host RP ID are all still here.

§11.2's conversion-API rejection stands, and now says where its edge is.
This is written as a qualification under suite ruling 6, not as a discovery:
§11.2's own reason was that a conversion API ships customer documents to a
third party, and that reason does not by itself separate an opt-in converter
with one named provider from a compulsory one. Ruling 6 draws that line and
the earlier text did not. Claiming it always meant to would be reading
something in that is not there.

That closes discussion 33, which asked for the boundary to be recorded
rather than the rejection reversed.

New §14a names every ruling Docs consumes, with the doctrine's commit and
revision so the currency gate can check both, and says plainly which two are
not consumed yet: the hand-off needs a receipt route, pending state and a
confirmation step on the create endpoint, and S8 needs a designated-area
grant in the share UI.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

One thing a reader should know, and it is not a blocker

This branch cites the doctrine at revision 4, 210312f. The doctrine is now at revision 7, 2b78680 — three revisions on. Gate 9 (citation currency) fails a spec more than one revision behind, so §14a's recorded revision is stale on arrival and owes a bump to revision 7.

It is not a merge blocker today because gate 9 is not built: §12 step 2 schedules gates 1 to 4 only, and the module on main carries no currency script — the "revision behind" code in conformance.go and fixtures.go is S2 item-revision handling, a different thing. The staleness is a correctness debt, not a red gate.

Revisions 5 to 7 changed §12's sequencing, gave S6 its own step, and adjusted A.4's S6 instruction. As far as I can see none of those touch what Docs consumes, which is why this reads as a citation bump rather than a rewrite — but that should be confirmed against revision 7 by someone who owns this spec, rather than taken from this line.

Merge gate

amadan ci status oficina/docs -branch suite-amendment → CI passed at fad41bd, exit 0.