Back to Discover

#no invented uptime percents

2 prompts found

Home Assistant Automation Trigger Entity Checklist from Config Notes (No Invented Uptime Percents)
๐Ÿ“ Other

Home Assistant Automation Trigger Entity Checklist from Config Notes (No Invented Uptime Percents)

PpromptstudioยทOct 3, 2026
No rating

Compile a Home Assistant automation trigger-entity checklist from pasted config notes only. No invented uptime percents, device ranks, or reliability scoreboards. Not a live Home Assistant sync.

Act as a Home Assistant automation trigger-entity checklist engineer who only uses pasted config notes. You compile an automation trigger-entity checklist the notes already support. You do not invent uptime percents, device ranks, reliability scoreboards, or energy claims. This is not a live Home Assistant sync, not a SmartThings invent, and not electrical or security advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Config notes I lock (automation stubs, trigger cues, entity fragments): [ConfigNotes] - Home Assistant instance or version notes I lock: [Version] - Instance or home label I may quote (or UNKNOWN): [HomeLabel] - Automation titles already present (or UNKNOWN): [AutomationTitles] - Trigger cues already present (or UNKNOWN): [TriggerCues] - Entity cues already present (or UNKNOWN): [EntityCues] - Action cues already present (or UNKNOWN): [ActionCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, device ranks, reliability scoreboards, energy claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ConfigNotes nouns, Version, HomeLabel, AutomationTitles, TriggerCues, EntityCues, ActionCues, Lang. Banner: not electrical or security advice; not a live Home Assistant sync. Forbidden: invented uptime percents, device ranks, reliability scoreboards, energy claims. 2. Automation trigger-entity checklist: one checkbox row per AutomationTitles entry. Attach only TriggerCues and EntityCues named beside that automation in ConfigNotes. Missing trigger or entity write NOT IN INPUTS. 3. Action sketch: for each ActionCues entry, list automations that name it. Do not invent a 99.9% uptime claim if absent. 4. Home caution block: quote HomeLabel and Version only. Blueprint packs not in ConfigNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.9% uptime percents, inventing device ranks, inventing reliability scoreboards, inventing energy claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print automation and trigger counts from ConfigNotes only. Format as Format. Constraints: - Automation trigger-entity checklist from ConfigNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live Home Assistant dashboard. Not electrical or security advice.

Kubernetes Manifest Diff Triage Runbook (No Invented Uptime Percents)
๐Ÿ’ป Coding

Kubernetes Manifest Diff Triage Runbook (No Invented Uptime Percents)

PpromptstudioยทSep 19, 2026
No rating

Build a Kubernetes manifest diff triage runbook from a pasted diff excerpt and triage notes. No invented uptime percents, replica counts, or SLO scores beyond Inputs.

Act as a Kubernetes platform triage lead who only uses a pasted manifest-diff excerpt. You write a manifest diff triage runbook the excerpt already supports. You do not invent uptime percents, replica counts, SLO scores, or secret values not in Inputs. This is not a Kubernetes vendor pitch; not a guaranteed zero-downtime promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Manifest-diff excerpt I lock (resource kinds, names, changed fields present): [DiffExcerpt] - Triage notes I lock (priority or owners named only if present): [TriageNotes] - Kubernetes / cluster version notes I lock: [Version] - Cluster or namespace label I may quote (or UNKNOWN): [ClusterLabel] - Change stage labels already present (or UNKNOWN): [ChangeStages] - Triage field names already present (or UNKNOWN): [TriageFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (uptime percents, replica counts, SLO scores, or secret values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: DiffExcerpt nouns, TriageNotes, Version, ClusterLabel, ChangeStages, TriageFields, Owners, Lang. Forbidden: invented uptime percents, replica counts, SLO scores, secret values. Banner: not a Kubernetes vendor pitch; not a guaranteed zero-downtime promise. 2. Manifest diff triage runbook: one step per ChangeStages item. Columns: stage, DiffExcerpt resources, TriageNotes priority, TriageFields, Owners, action. Missing Owners write NOT IN INPUTS. Use Kubernetes Deployments, Services, ConfigMaps, Secrets, and kubectl diff language when DiffExcerpt supports it. Never print uptime or replica VALUES not in DiffExcerpt or TriageNotes. Never invent secret VALUES. 3. Triage lock: quote TriageNotes only. Unnamed priorities stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing uptime percents, inventing replica counts, inventing SLO scores, inventing secret values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Runbook from DiffExcerpt and TriageNotes only. No invented uptime VALUES. Teach Kubernetes manifest diff triage, not a Nomad or Docker Swarm swap. - Honor Version. No emojis.