Delivered 2026-09-27 by spice-sp-fidelity-researcher (verified by claude-code): SPICE already carries most of the Publishing feature - content approval (ContentApproval.cs, _ModerationStatus), PublishingRollupImage, the catalog connection / cross-site publishing (AGT.59/84), page layouts as data (Scope.PageTemplates: OneColumnHtml, TwoColumnHtml, ShipCityViz), managed metadata. Two real gaps, no new part kind: scheduling (PublishingStartDate/EndDate on ContentType.Page + a visibility check beside IsVisible) and the per-site master page (SiteBlueprint@MasterPageUrl declared, Theme page writes it, but PagesController and BoardChromeShell hardcode MasterPage.xslt and IMasterPageEngine is registered and never called). Design Manager deliberately not borrowed: layouts are declared XML, not converted HTML. Units filed as SPWAY.10b-10h; staffing: Author (Actor.PageSmith shape), Designer (new ActorProfile, authors Scope.PageTemplates layouts), Approver (any Lead + Tool.ModerateListItem), Editor (Actor.PartArchitect shape, owns the blueprint and the term set); Agency.Publishing mirrors Agency.PartsFactory.