oficina / suite Public

Revision 8: the contract module is built and cannot be imported

The memoria session tried to wire the module and could not. Verified twice,
independently:

    $ go get amadan.net/oficina/suite@latest
    go: unrecognized import path: no go-import meta tags
    $ curl -o /dev/null -w '%{http_code}' "https://amadan.net/oficina/suite?go-get=1"
    302   -> /auth/login

The hub answers ?go-get=1 with a redirect to a login page, so the Go
toolchain never sees a go-import tag. It is not a missing tag so much as an
authenticated repo page standing where the tag should be.

So §12 step 2 is built rather than done. The code, fixtures and harness are
on main and their tests pass, and nothing can depend on any of it. That
matters because ruling 7 is "every app imports the module, serves its server
half, and passes the conformance suite in CI" — and there are no consumers
available to it. Steps 3 and 4 both say "against the module".

This is the same failure shape as S6 two revisions ago, which is why it is
worth the number: an artefact that exists reads as a step that is finished.
S6 had a number and no builder; the module has code and no consumer.

Three ways out are recorded and all three are Paul's, because each is hub or
hosting rather than doctrine: serve go-import for repo paths without auth,
which is the only one that works in CI and fixes every app at once; document
GOPRIVATE with a credential CI can hold, if the tag can be served behind
auth; or move the module to a resolvable host, which contradicts ruling 10 in
hosting but not in structure.

Two workarounds are recorded as deliberately refused. A local replace
directive works on one machine, breaks CI, and makes a go.mod a
machine-local artefact. Vendoring is the second copy ruling 7 exists to
prevent and defeats "fixtures are the interface" the first time a fixture
changes. The memoria session declined both and recorded itself blocked,
which is the right answer and is why this was found rather than papered
over.

The README stops repeating the doctrine's status. It still said revision 4
and three review passes while the doctrine was at 7 — this repository's own
README having become the stale second copy of the document whose §2
diagnoses exactly that. It now points at the doctrine's status block and
carries only what is about the repository, which today is that the module
cannot be imported. Its "an app imports the module" also stopped being
written in the present tense, because it is not true yet.

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