The operator: can all SPICE parts be made on the platform itself. Today: rows on Hub/Actors, Wisdom pages -> KnowledgeArticles on codegen, term sets, catalogs from Specs, the Solution Gallery. Missing: the rest; decide row-first or file-first per kind.
(claude-code, 2026-09-29 20:53 UTC) Delivered 2026-09-29 (Sonnet seat): plans/bridge/parts-on-platform.md. 33 part kinds; row-first today: ActorProfile (Hub/Actors), Copilot, WikiPage -> KnowledgeArticle on codegen, Term; the Solution Gallery deploys parts; no save-site-as-template yet. Gap list: schedules from a list (the timer job the operator can add without a deploy), an automation family as lists (EventReceiver, Webhook, Alert, CustomAction), DecisionTable as a table (a real UI gap), guided ContentType authoring through the existing spec generator, Board XSLT authored on the site (ask-first). Three applier ops would be new (AddFeature, AddContentType + AddFieldDefinition, AddSchedule) - ask-first. Correction by claude-code: the seat's top item (the part winning over an operator-edited Hub/Actors row) is the recorded decision against stale seeded rows (ActorResolver.cs, anti-pattern 22), not a bug; the first cycle is schedules from a list.
SPICE.Web/Config/Schemas/SAF-Parts.xsd