project the remaining package contribution kinds: prompts, skills, MCP servers, defaults #1204

Open
opened 2026-10-27 13:39:26 +00:00 by sam · 0 comments
Owner

em7s.9 delivered the workflow contribution kind only, live both ways. Four kinds were STOPPED because the contribution format for each is unsettled -- not because the work was left undone:

  • prompts: store.md says "prompts" while the tree models personas (agent.PersonaCollection, PersonasKind). Which one a contributed prompt becomes is a mapping decision.
  • skills: skills live on host disk (SkillsDir in operational_settings.go), not as org resources. Projecting a contributed skill means writing host files, and that surface is unsettled.
  • MCP server definitions: ToolSettingsKind is ApplyMode "restart-required", so projecting one contradicts em7s.9's own live requirement.
  • defaults: no format exists anywhere -- defaults for what, keyed how, and what precedence against the config seed are all unstated in store.md.

Decide each format (one PRD covering the contribution model, or a decision per kind if they diverge), then implement projection per kind on the machinery em7s.9 landed: storepkg.FamilyProjector/ProjectionLedger, FilesFromLayer, migration 0023, and the collision-refusal rule.

Settle one policy question em7s.9 answered conservatively: a contributed workflow id is refused if an existing entry with that id is not the package's own, which also refuses a package overriding a SHIPPED id. Refusal is the right default until the PRD says otherwise; if shipped-override should be allowed (with restore-on-withdraw), say so there.


Imported from beads archie-core-9gcr · GitHub #1344 · type task · priority P2 · created 2026-09-29

em7s.9 delivered the workflow contribution kind only, live both ways. Four kinds were STOPPED because the contribution format for each is unsettled -- not because the work was left undone: - prompts: store.md says "prompts" while the tree models personas (agent.PersonaCollection, PersonasKind). Which one a contributed prompt becomes is a mapping decision. - skills: skills live on host disk (SkillsDir in operational_settings.go), not as org resources. Projecting a contributed skill means writing host files, and that surface is unsettled. - MCP server definitions: ToolSettingsKind is ApplyMode "restart-required", so projecting one contradicts em7s.9's own live requirement. - defaults: no format exists anywhere -- defaults for what, keyed how, and what precedence against the config seed are all unstated in store.md. Decide each format (one PRD covering the contribution model, or a decision per kind if they diverge), then implement projection per kind on the machinery em7s.9 landed: storepkg.FamilyProjector/ProjectionLedger, FilesFromLayer, migration 0023, and the collision-refusal rule. Settle one policy question em7s.9 answered conservatively: a contributed workflow id is refused if an existing entry with that id is not the package's own, which also refuses a package overriding a SHIPPED id. Refusal is the right default until the PRD says otherwise; if shipped-override should be allowed (with restore-on-withdraw), say so there. --- _Imported from beads `archie-core-9gcr` · GitHub #1344 · type task · priority P2 · created 2026-09-29_
sam added the mediumtask labels 2026-10-27 13:39:26 +00:00
sam self-assigned this 2026-10-27 13:39:26 +00:00
sam added a new dependency 2026-10-27 13:42:20 +00:00
sam added the deferred label 2026-11-15 17:26:21 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1204