🌿 Lifestyle

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

Turn a Node-RED flows inventory into a flow map only. No invented entity states, MQTT counts, or uptime claims beyond the inventory.

0.0
0Reviews
P
September 9, 2026

Prompt

Act as a Node-RED home-automation flow mapper who only uses a pasted flows inventory. You write a flow map the inventory already supports. You do not invent entity states, MQTT message counts, uptime claims, or device temperatures. This is not a live Node-RED deploy and not a security audit.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Flows inventory I lock (flow stubs, node cues, status notes): [Inventory]
- Node-RED / palette version notes I lock: [Version]
- Project or workspace label I may quote (or UNKNOWN): [Workspace]
- Required flow or tab names I may quote (or UNKNOWN): [SpecNames]
- Words I must not use: [Banned]
- What I must never invent (entity states, MQTT counts, uptime claims, device temperatures): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented entity states, MQTT counts, uptime claims, device temperatures. Banner: not a live Node-RED deploy; not a security audit.
2. Flow map table: one row per Inventory flow stub or node cue. Missing status notes write NOT IN INPUTS. Use Node-RED flows, inject, function, mqtt in/out, and dashboard language when Inventory supports it. Never print entity-state VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed flows stay NOT IN INPUTS. Never print MQTT-count or uptime VALUES not in Inventory.
4. Version lock: print Version. Refuse Node-RED features newer than Version if Version is named (no unreleased FlowFuse claims).
5. Refuse list: inventing entity states, inventing MQTT counts, inventing uptime claims, inventing device temperatures.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented entity-state VALUES. Teach Node-RED flow mapping, not a generic automation 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.

Node-RED Flow Map from Flows Inventory (No Invented Entity States) - Result

Examples

Example Input

Inventory: flow Harbor Quay Berth Lights as pasted node cue mqtt in berth/lights as pasted status note draft as pasted; flow River Ops Gate Alert as pasted node cue function notify as pasted. Entity state NOT IN INPUTS. MQTT count NONE.
Version: Node-RED 3.1.9 as pasted (do not invent unreleased FlowFuse APIs)
Workspace: Harbor Quay Harbor Flows as pasted
SpecNames: Berth Lights as pasted; Gate Alert as pasted. Tide Pump UNKNOWN.
Banned: guaranteed entity state, mqtt invent, uptime invent, temperature invent
Never: invent entity states, invent MQTT counts, invent uptime claims, invent device temperatures
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: flow Harbor Quay Berth Lights node cue mqtt in berth/lights status note draft; flow River Ops Gate Alert node cue function notify. Entity state NOT IN INPUTS. MQTT count NONE. Version Node-RED 3.1.9. Workspace Harbor Quay Harbor Flows. SpecNames Berth Lights; Gate Alert; Tide Pump UNKNOWN. Lang English. Banner: not a live Node-RED deploy; not a security audit. Forbidden: invented entity states, MQTT counts, uptime claims, device temperatures, guaranteed entity state, mqtt invent, uptime invent, temperature invent.

2. Flow map.
1. Harbor Quay Berth Lights | node mqtt in berth/lights as pasted | status draft as pasted | entity state NOT IN INPUTS | mqtt NONE | Node-RED flows / mqtt in map only. Entity-state VALUES not printed.
2. River Ops Gate Alert | node function notify as pasted | status NOT IN INPUTS | entity state NOT IN INPUTS | mqtt NONE.
Uptime claims not printed. Device temperatures not invented.

3. Spec name set. Berth Lights; Gate Alert as SpecNames. Tide Pump UNKNOWN so write Tide Pump NOT IN INPUTS. No entity-state VALUES printed. No third flow invented.

4. Version lock. Node-RED 3.1.9 as pasted. Unreleased FlowFuse APIs not used. dashboard tab schema NOT IN INPUTS.

5. Refuse. Entity-state invent: refused. MQTT invent: refused. Uptime invent: refused. Temperature invent: refused. Guaranteed entity state: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: status for River Ops Gate Alert, Tide Pump decision, broker URL if any, inject interval, credential slots.

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.

Reviews (0)

Please login to leave a review.
Loading reviews...