How to Use Node-RED Flow Map from Flows Inventory (No Invented Entity States)

This guide shows how to run the PromptDig prompt Node-RED Flow Map from Flows Inventory (No Invented Entity States) from a locked source packet so you get a usable draft without invented citations, stats, or identifiers. The prompt is built for ChatGPT, Claude, and Gemini. Open it on PromptDig, paste your Inputs, and keep every claim auditable.

What this prompt is for

The job titled Node-RED Flow Map from Flows Inventory (No Invented Entity States) is a narrow domain workflow. It asks the model to work only from your Inputs, mark gaps as NOT IN INPUTS or UNKNOWN, and refuse to invent evidence. That matters when you need a first draft that a human can audit against a packet, not a polished story with fake footnotes. Goal: Turn a Node-RED flows inventory into a flow map only. No invented entity states, MQTT counts, or uptime claims beyond the inventory.

Node-RED uses flows, inject, function, mqtt in/out, and dashboard rather than a generic automation dance. Lock Version so the flow map does not claim FlowFuse the 3.1 era does not support. Paste flow stubs and node cues only. If entity states are missing, write NOT IN INPUTS instead of guessing MQTT counts.

Before you open the model

1. Gather the Inventory packet you will lock (notes, requirements, outcomes, inventory lines, or baselines). Prefer plain text you can paste.
2. Lock Version for the tool named in the title. If unnamed, write unknown.
3. List Banned words and a Never invent list that matches the title boundary (no invented rates, IDs, scores, or owners).
4. Choose Format and Language. Keep Extra fields UNKNOWN if you do not have an escalation path yet.
5. Confirm the deliverable boundary matches the title so the model does not drift into captions, exam dumps, or advice.

Step-by-step run

1. Open Node-RED Flow Map from Flows Inventory (No Invented Entity States) on PromptDig and copy the prompt text.
2. Replace every [bracket] field with your real Inputs. Do not leave sample nouns in place.
3. Paste into your model of choice. If the model starts inventing, stop and restate the Never invent list at the top of a follow-up.
4. Read the honesty ledger first. Confirm Version, Workspace, SpecNames, Lang, and Forbidden items match what you locked.
5. Accept only the map or checklist rows that quote Inventory nouns. Anything that cannot be traced should be cut or marked NOT IN INPUTS.
6. Use the gaps list as your homework. Fill those five owed fields before a second pass.
7. Run the compliance pass: quote Banned and Never hits, cut them, and print counts when Cap is numeric.

Quality checks

• No invented citations, DOIs, CTR, attendance, reviews, nutrition facts, part numbers, scores, or owners.
• No emojis in the deliverable unless your Format explicitly allows them.
• Cap honored with printed counts when Cap is numeric.
• Domain banners present for clinical, legal, insurance, education-plan, or veterinary jobs (not advice, de-identify).
• Banned and Never hits quoted and removed.
• Missing fields stay NOT IN INPUTS or NO_DATA rather than guessed.
• Tool-specific steps stay inside the named product (not a swap-title skeleton).

Related links

• Node-RED Flow Map from Flows Inventory (No Invented Entity States)
• Browse more prompts
• Share a prompt

Closing notes

Use this prompt when you want a structured first pass that stays faithful to a locked inventory. Keep the model inside the job boundary named in the title. If you need a different deliverable, pick another PromptDig prompt rather than stretching this one. After you fill the gaps list, rerun with only the new Inputs. That habit keeps drafts short, auditable, and ready for human review without invented evidence.

Keep every claim auditable against Inputs. Prefer short sections over fluff. If a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs. Character and byte caps in the job are hard; print counts when relevant. End every pass with the five-bullet gaps list so the next human edit has a clear queue. When you rerun, paste only the missing Inputs rather than rewriting the whole brief. A second pass should shrink invention risk, not expand scope into captions or advice.