💻 Coding
Dagster Asset Job Map from Definitions Inventory (No Invented Materializations)
Turn a Dagster definitions inventory into an asset job map only. No invented materialization counts, run durations, or partition sizes beyond the inventory.
0Reviews
Prompt
Act as a Dagster asset engineer who only uses a pasted definitions inventory. You write an asset job map the inventory already supports. You do not invent materialization counts, run durations, partition sizes, or SLA targets. This is not a live Dagster Cloud run and not an SLA report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Definitions inventory I lock (asset stubs, job cues, status notes): [Inventory] - Dagster / SDK version notes I lock: [Version] - Code location or workspace label I may quote (or UNKNOWN): [Workspace] - Required asset or job names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (materialization counts, run durations, partition sizes, SLA targets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented materialization counts, run durations, partition sizes, SLA targets. Banner: not a live Dagster Cloud run; not an SLA report. 2. Asset job map table: one row per Inventory asset stub or job cue. Missing status notes write NOT IN INPUTS. Use Dagster Definitions, Assets, Jobs, and Sensors language when Inventory supports it. Never print materialize() counts not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed assets stay NOT IN INPUTS. Never print duration or partition VALUES not in Inventory. 4. Version lock: print Version. Refuse Dagster APIs newer than Version if Version is named (no unreleased Pipes claims). 5. Refuse list: inventing materialization counts, inventing run durations, inventing partition sizes, inventing SLA targets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented materialization VALUES. Teach Dagster asset and job mapping, not a generic DAG swap. - Honor Version. No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Inventory: asset Harbor Quay Tide Events as pasted job cue tide_daily as pasted status note draft as pasted; asset River Ops Gate Metrics as pasted job cue gate_hourly as pasted. Materialization count NOT IN INPUTS. Run duration NONE. Version: Dagster 1.8 as pasted (do not invent unreleased Pipes APIs) Workspace: Harbor Quay Analytics Code Location as pasted SpecNames: Tide Events as pasted; Gate Metrics as pasted. Berth Backfill UNKNOWN. Banned: guaranteed materialization, duration invent, partition invent, SLA invent Never: invent materialization counts, invent run durations, invent partition sizes, invent SLA targets Format: ledger + table + specs + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: asset Harbor Quay Tide Events job cue tide_daily status note draft; asset River Ops Gate Metrics job cue gate_hourly. Materialization count NOT IN INPUTS. Run duration NONE. Version Dagster 1.8. Workspace Harbor Quay Analytics Code Location. SpecNames Tide Events; Gate Metrics; Berth Backfill UNKNOWN. Lang English. Banner: not a live Dagster Cloud run; not an SLA report. Forbidden: invented materialization counts, run durations, partition sizes, SLA targets, guaranteed materialization, duration invent, partition invent, SLA invent. 2. Asset job map. 1. Harbor Quay Tide Events | job tide_daily as pasted | status draft as pasted | materializations NOT IN INPUTS | duration NONE | Dagster Definitions / Assets map only. materialize() counts not printed. 2. River Ops Gate Metrics | job gate_hourly as pasted | status NOT IN INPUTS | materializations NOT IN INPUTS | duration NONE. Partition sizes not printed. SLA targets not invented. 3. Spec name set. Tide Events; Gate Metrics as SpecNames. Berth Backfill UNKNOWN so write Berth Backfill NOT IN INPUTS. No materialization VALUES printed. No third asset invented. 4. Version lock. Dagster 1.8 as pasted. Unreleased Pipes APIs not used. sensor schema NOT IN INPUTS. 5. Refuse. Materialization invent: refused. Duration invent: refused. Partition invent: refused. SLA invent: refused. Guaranteed materialization: refused. 6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: status for River Ops Gate Metrics, Berth Backfill decision, partition def, IO manager, freshness policy if any. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.