more

catalog/builder_test.go

@@ -194,7 +194,7 @@ func TestBuilderFractionalStringPriceCorrectScale(t *testing.T) {
 	}
 }
 
-// Drop-ship routing carriers (docs/plan-dropship.md Phase 1): seller id /
+// Drop-ship routing carriers (docs/archive/plan-dropship.md Phase 1): seller id /
 // name / lead time coerce from per-tenant source keys via Schema overrides,
 // mirroring how the live feed emits supplierName-style keys. Zero values
 // (missing keys, negative numbers, junk strings) must stay at the documented

catalog/doc.go

@@ -34,8 +34,9 @@
 //     issues a "lookup this SKU" RPC today and resolving it here would be
 //     premature.
 //
-// See docs/published-document-vocabulary-pass.md §11 for the wider vocabulary
+// This package implements the catalog side of the shared vocabulary used by
-// context (this package implements the cart side of that contract; the full
+// `platform/event` + `platform/inventory` + `platform/order`. A generic
-// vocabulary is the next pass and lives in `platform/published` once proven
+// `platform/node` aggregate is deliberately held back (see docs/status.md
-// out).
+// "Deliberately deferred"); cross-module boundaries are served by
+// `platform/catalog` + `platform/projection` instead.
 package catalog

catalog/projection.go

@@ -106,7 +106,7 @@ type Projection struct {
 	TaxClass         string          `json:"tax_class"`
 	InventoryTracked bool            `json:"inventory_tracked"`
 	DropShip         bool            `json:"drop_ship"`
-	// Drop-ship routing carriers (Phase 1 of docs/plan-dropship.md).
+	// Drop-ship routing carriers (Phase 1 of docs/archive/plan-dropship.md).
 	// SellerID mirrors AddItem.ItemId coercion rules: 0 = "producer didn't
 	// publish" and downstream keeps whatever the HTTP fallback fetched.
 	// SellerName is what checkout writes into order-line

doc.go

@@ -9,5 +9,8 @@
 // and other platform/ packages — never an application module. Application
 // modules depend downward onto platform. This is what keeps it a stable seam.
 //
-// See docs/platform-uniforming-plan.md for the layout and the migration order.
+// The migration that built this module is recorded in
+// docs/platform-uniforming-plan.md; the live package inventory lives in
+// docs/status.md ("Shared seams (platform/)"). Individual seam packages are
+// documented in platform/agents.md.
 package platform

mcp/server.go

@@ -4,7 +4,8 @@
 // (their domain logic) stay in each module. A module builds its []Tool and calls
 // NewServer; nothing here knows about carts, content, or orders.
 //
-// See docs/platform-uniforming-plan.md §3b and platform-event-messaging-sketch.md.
+// See docs/platform-uniforming-plan.md (platform/mcp seam, migration done) and
+// platform-event-messaging-sketch.md.
 package mcp
 
 import (

rabbit/conn.go

@@ -3,7 +3,7 @@
 // hand-roll. It carries NO event vocabulary: topic and routing names are plain
 // strings supplied by the caller, so each module keeps its own naming policy
 // (finder's "<country>_<topic>", CMS's "kind.dataType", etc.). See
-// docs/platform-uniforming-plan.md Win 3.
+// docs/platform-uniforming-plan.md (platform/rabbit seam, migration done).
 package rabbit
 
 import (