Relationships
#4472 Ops: package the dossier workflows; give access:* a git path
Opened by swamp_lord · 11/6/2026· Shipped 11/6/2026
Problem
After lab #4353, everything on ops.swamp-club.com ships from git except:
- Two workflows still defined only on ops:
dossier-publish(Mondays 12:10 UTC, publishes@swamp/platform-health/axiom-weekly-report's document as theswamp-club-platform-reportdossier) anddossier-app-publish(publishes a static app behind an approval gate). They are mirrored in platform-swampops/workflows/but not packaged, and nothing applies them. They were deferred from #4353 on purpose. access:*(grants and tokens): grants already ship fromops/grants/(Release ops config), but nothing stops a principal withadminonaccess:*creating grants or minting tokens with the CLI, so it isn't denied inops/grants/no-direct-edits.yaml.
Plan
- Package both dossier workflows (likely
@swamp/platform-ops, or@swamp/platform-healthfordossier-publishbesideaxiom-weekly-report). Pointdossier-publishat the packaged report by name, then add both toops/retired-workflows.yamlso Release extensions deletes the ops-local copies. - Decide how tokens are minted (they create models and secrets on ops) and how a break-glass works, then deny
access:*writes to people. Grants already come from files.
Done when
swamp workflow searchon ops shows no workflow without a collective.- Nobody but the pipelines can change grants, tokens or definitions on ops.
Shipped
Click a lifecycle step above to view its details.
swamp_lord commented 11/6/2026, 2:08:44 PM
Part 1 done (#314): dossier-publish and dossier-app-publish were retired as unused rather than packaged (the only recent dossier-publish run had failed; dossier-app-publish never ran) and deleted from ops by Release extensions. All 153 workflows on ops now come from extensions. Publishing to dossier still works through the swamp-club-dossier-v2 model. Remaining: a git path and deny for access:* (token minting and break-glass to decide first).
swamp_lord commented 11/6/2026, 2:18:58 PM
Done. Part 2: access:* (grants and tokens) stays open by design. The break-glass is direct access to the ops VM over IAP SSH, documented in the new ops-break-glass skill (#315): lift the no-direct-edits deny for one person, reload, make the change, PR it into git, then restore the deny by running Release ops config (any later config merge or a reboot also restores it). Token minting stays a manual serve-admin action, recorded in the issue that needs it. With #314, every workflow, model, vault definition and grant on ops ships from git.
Sign in to post a ripple.