Hotspot Block

When To Use It

Use a Hotspot block whenever the team is unsure. Do not let uncertainty disappear into meeting notes. Hotspots preserve context and make it clear what must be resolved before generation, deployment, or business sign-off.

Required Data

• Title: short question or risk label.
• Description: what is unknown or contested.
• Related blocks: commands, events, policies, aggregates, or integrations affected.
• Owner: person or role responsible for resolving it.
• Resolution status: open, researching, decided, accepted risk, or blocked.

Recommended Data

• Decision deadline: when the hotspot must be resolved.
• Impact: generation blocker, compliance risk, user experience risk, integration risk, or business ambiguity.
• Options considered: alternatives and trade-offs.
• Decision record: final answer and why it was chosen.

Examples

• Can a supervisor approve a claim without all evidence?
• Which system owns customer contact preferences?
• What happens when the payment gateway authorizes but capture fails?
• Does “cancelled” mean user cancelled, system expired, or vendor rejected?

Generation Notes

Code Genie should treat unresolved generation-blocking hotspots as review warnings. Some hotspots can remain as accepted risks, but unresolved business rules should be closed before generating production-ready code.