The Signal runs on the AI-Generative Platform.See the platform →

Troubleshooting

Turn conflicting rules into a bug ticket

Why now: Muse’s spaces centers on describing custom experiences; checking whether a description contradicts itself is a useful first step.

Prompted by today's lead: Custom, app-like experiences are coming to Muse

What you'll need

  • A short, non-sensitive description of an app-like experience or recurring task, including its rules.

Steps

  1. Paste your description into the prompt.
  2. Compare the identified conflict with your original rules.
  3. Accept or reject the proposed fix before changing your description.

The prompt

Read these notes for a custom experience and look for one contradiction between explicit rules. Return plain text with no Markdown formatting, under 120 words. Write one bug ticket with exactly four labeled fields: Conflict, Trigger, Consequence, Proposed fix. In Conflict, quote the two conflicting rules. In Trigger, describe the smallest scenario that activates both. In Consequence, explain why both cannot be satisfied. In Proposed fix, suggest the smallest wording change and label it as a suggestion, not an agreed requirement. Do not invent features. If no contradiction is supported, write 'Not established' in each field. Notes: [paste your experience notes]

What you should get

One ticket under 120 words with four labeled fields, two quoted conflicting rules, a triggering scenario, the incompatible outcome, and a minimal wording change explicitly labeled as a suggestion.

Tested example: Tested on sample input

Input

I want a simple houseplant watering screen. Show every plant due for watering today. When I mark a plant watered, immediately hide it from today's screen. Keep every plant watered today visible on that same screen until evening so I can review what I finished. I will enter the watering dates myself; the screen should not estimate them.

Output

Conflict: “When I mark a plant watered, immediately hide it from today's screen.” conflicts with “Keep every plant watered today visible on that same screen until evening so I can review what I finished.”
Trigger: Before evening, I mark one plant on today’s screen as watered.
Consequence: That plant must immediately disappear and remain visible on the same screen until evening; both cannot be satisfied.
Proposed fix: Suggestion: Replace “immediately hide it from today's screen” with “hide it from today's screen at evening.”

How we tested it: How we checked this: an AI model ran this prompt on the sample input on November 7, 2026, and a separate model call checked the result against what the Move promises.