RFC-0037 WorkspaceService cross-reference
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
The RDF claim RFC-0037/sec-4/workspace-creation-out-of-scope says that
RFC-0014 covers Workspace creation and tenant binding. RFC-0014 is the Module
Versioning Protocol and contains no tenancy or Workspace contract. An older
RFC-0037 Lean evidence item repeats the same attribution. The current
RFC-0037 §4.7 says Workspace creation and tenant binding are outside this
service, cites RFC-0045 for tenant-mode configuration and RFC-0051 for
PostgreSQL RLS binding, and defers the complete cross-backend tenancy
contract. Section 5.4 repeats that scope. None of these RFCs is described as
owning Workspace creation.
This is a source-reference correction, not a choice of tenancy behavior. The claim should state only the out-of-scope rule, then cite RFC-0045 and RFC-0051 for their specific responsibilities. The Lean evidence and top-level references should be reconciled with the authored prose. Regenerate the reference and Turtle from their sources, refresh affected review hashes, and verify all linked RFC IDs and section targets. Keep the claim subject IRI.
Resolution
The protobuf claim now names RFC-0045’s tenant-mode setting and RFC-0051’s PostgreSQL RLS binding without assigning Workspace creation to either. The Lean evidence and references use the same mapping. The pinned Lean corpus compiled and regenerated RFC Turtle; the reference catalog and claim Turtle drift checks passed. All 171 RFC-0037 source-bound reviews were refreshed against the changed Lean source, and the WorkspaceService claim now matches. The broader cross-backend tenancy contract remains deferred by §4.7 and §5.4.