dagster-orchestration-adapterlisted

Run the medallion sequence UNATTENDED / in CI as a Dagster asset graph -- the scheduler sibling of the retail-orchestrate conductor -- running ONLY already-approved steps behind every gate, and recording what each asset DID as DERIVED run-evidence. Use when someone asks to schedule the pipeline, run the medallion in CI, "orchestrate unattended", or wire Dagster in the Seshat BI repo. Dagster RUNS approved steps; Tower BI (the gate exit code + the named human) decides whether a stage passed. This skill READS committed approvals as the GO signal, EXECUTES approved steps behind STOP / HUMAN-SEAM edges, and WRITES run-evidence; it never defines meaning, never moves a stage to pass, never publishes Power BI (it only TRIGGERS F016), and HARD-STOPS at every human judgment call.
Kemetra/Seshat-BI · ★ 2 · AI & Automation · score 68

Install: claude install-skill Kemetra/Seshat-BI

# dagster-orchestration-adapter - **Authority category (F024):** Execution Adapter / `DB-connected` (NOT publish-capable; it TRIGGERS F016, it never publishes). The F024 enumerated declaration -- see `docs/architecture/product-modules.md`. - **Roadmap feature:** F030 **On-disk spec:** `specs/024-dagster-orchestration-adapter` (dir 024 == F030; when the dir number and the F-number disagree, the roadmap F-number wins). Dagster is the unattended / CI RUNTIME for the medallion sequence: a scheduler / pipeline runs the asset graph so a human does not re-type each step. `retail-orchestrate` (F005) is the INTERACTIVE conductor of the SAME sequence; Dagster is its unattended sibling -- same medallion sequence, same gate-exit authority, same two human seams, neither self-approving. Tower BI (the gate exit code + the named human) is the brain; Dagster is the runner. This skill is how the agent reasons about running the medallion unattended without letting the orchestrator become the brain. You (the agent reading this) ARE the design surface; this skill is procedure, not an engine -- the engine, when built, is the separate Dagster project. See `docs/decisions/0010-dagster-is-orchestration-adapter.md` and `docs/integrations/dagster-adapter.md`. > STATUS: the Dagster PROJECT is BUILT (spec 134, activation slice of F030; > the dbt engine seam is ACTIVATED per spec 135). `orchestration/dagster/` > exists -- `definitions.py`, the 11-asset graph, `jobs`, one STOPPED schedule, > one