How Item records, publication and connected context work.
Item guide
A thing, its identity, and the context that explains it.
Find and inspect
The collection shows published records, newest first, up to 200 at a time. Open a record to inspect identity, status and metadata. Connected shop, manufacture, order and history panels load through their owning Connections.
Create, then publish
The collection form sends an explicit publication choice to Item.Upsert; unchecked saves a draft. Item.Publish changes publication separately and requires the owning account. Item.Delete creates a tombstone. Reading a page never imports shop data or grants publication authority.
Supported connections
Item.List and Item.Get read records. Item.Status and Item.ViewPatch report current counts. Item.Preview requests a preview. Item.SyncCatalog and Item.MigrateLegacy are explicit import operations; they are never triggered by browsing.
About Item
The Item runtime app owns item identity and publication. HyperDB stores authoritative Item records. Asset and Protocol are declared host dependencies. Shop and Manufacture retain ownership of their own connected records.
Evidence and limitations
A record or rendered status is not proof of manufacture, fulfillment or settlement. Anonymous SSR exposes only explicitly published records. Authenticated management and connected history depend on their owning services being available.