Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
AssigneesNone

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 the swamp-club-platform-report dossier) and dossier-app-publish (publishes a static app behind an approval gate). They are mirrored in platform-swamp ops/workflows/ but not packaged, and nothing applies them. They were deferred from #4353 on purpose.
  • access:* (grants and tokens): grants already ship from ops/grants/ (Release ops config), but nothing stops a principal with admin on access:* creating grants or minting tokens with the CLI, so it isn't denied in ops/grants/no-direct-edits.yaml.

Plan

  1. Package both dossier workflows (likely @swamp/platform-ops, or @swamp/platform-health for dossier-publish beside axiom-weekly-report). Point dossier-publish at the packaged report by name, then add both to ops/retired-workflows.yaml so Release extensions deletes the ops-local copies.
  2. 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 search on ops shows no workflow without a collective.
  • Nobody but the pipelines can change grants, tokens or definitions on ops.
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPEDCOMPLETE

Shipped

11/6/2026, 2:22:18 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
Editable. Press Enter to edit.

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.