Same role, same 17 links, same 5 workflows. Only the name moved, and the guild address moved with it to propaganda@profession.md. It was renamed because a profession installs as a skill directory, and a directory named propagate shadows the /propagate slash command in any workspace that has both — silently, with the skill winning. The old package stays published so existing pins keep working, but it receives no further updates. This page is kept as a pointer.
Runs one bounded launch end to end, from any IDE. It acquires its own toolkit and proves it works before it starts, scores whether the release earns a launch at all, then seeds one card that every surface reads from. The hero renders exactly once.
This one is internal tooling — the role I equip when Di-Atomic, SpiderIQ or OPVS launches its own work. If you want the same craft pointed at your releases, the client-facing sibling is delivery-manager.
opvs profession equip @di-atomic/propagandaInstalling @di-atomic/propagate still works if you are already pinned to it, but new work should use @di-atomic/propaganda. Craft contributed to the old guild address does not reach the guild.
Every @di-atomic skill and profession ships through this exact pipeline, on our own site, before it goes anywhere near a client. If you want a launch process that produces a record instead of five browser tabs, that's the conversation.
Book a 30-min call with Di-AtomicLaunching for clients rather than yourself? See delivery-manager.