Skip to main content

Documentation Index

Fetch the complete documentation index at: https://suprmind.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Generate a Decision Record

What it creates: A documented decision with context, alternatives considered, trade-offs analyzed, and rationale for the chosen option.

When to Use This

  • You’ve debated options with the AIs and reached a conclusion
  • You need to document why a decision was made (for future reference)
  • You want to show stakeholders that alternatives were properly evaluated
  • You’re following ADR (Architecture Decision Record) practices

What You Get

A Decision Record typically includes:
  • Decision - The clear statement of what was decided
  • Status - Proposed / Accepted / Deprecated / Superseded
  • Context - Why this decision was needed
  • Options Considered - Each alternative with pros and cons
  • Decision Rationale - Why the chosen option won
  • Consequences - What changes as a result
  • Trade-offs Accepted - What you’re giving up
  • Review Triggers - When to revisit this decision

Example

Conversation context: You debated whether to use WebSockets or Server-Sent Events for real-time features, with the AIs analyzing performance, complexity, and browser support. Generated Decision Record excerpt:
Decision: Use Server-Sent Events (SSE) for real-time updates Status: Accepted Context The platform needs real-time delivery of AI responses and Scribe updates. Users expect to see streaming text as AIs generate responses. We need a solution that works reliably across browsers and scales with our infrastructure. Options Considered
WebSocketsSSELong Polling
ComplexityHighLowLow
BidirectionalYesNo (one-way)No
Browser supportAll modernAll modernAll
Proxy/CDN compatibilityProblematicGoodGood
Connection managementManualAutomatic reconnectManual
ScalingStateful, complexStateless, simpleStateless, simple
Decision Rationale Our use case is predominantly server-to-client (AI streaming responses). We don’t need client-to-server real-time (regular HTTP POST handles message sending). SSE gives us automatic reconnection, works well with our Cloudflare CDN, and keeps infrastructure stateless. Trade-offs Accepted
  • No bidirectional real-time (acceptable - we use HTTP for client-to-server)
  • No binary data support (acceptable - all our data is text/JSON)
Review Triggers
  • If we add collaborative editing (multiple users typing simultaneously)
  • If we need client-to-server streaming (voice input, screen sharing)

Tips for Best Results

  • Use Debate mode before generating - it naturally surfaces arguments for each option
  • Ask the AIs to be explicit about trade-offs: “What do we give up with each option?”
  • Include constraints: budget, timeline, team skills, existing infrastructure
  • Ask for failure scenarios: “What could go wrong with each option?”
  • Generate after you’ve reached a conclusion, so the document captures the full reasoning

Best AI Engine for This Type

Claude - Excels at articulating nuanced rationale, trade-offs, and the reasoning behind complex decisions. GPT - Good alternative when the decision is highly technical and needs precise comparison tables.

Export & Delivery

Your generated document streams in real time - you watch sections build as they are written. Once complete, you can:
  • Copy to clipboard for pasting into any app
  • Download as PDF - charts from the conversation are automatically embedded
  • Download as DOCX (Word) - charts are embedded here too
The download button is in the modal header bar. When you copy or download, the document is automatically saved to your project’s knowledge base for future AI reference.

Still Need Help?

Reach out to us at support@suprmind.ai or use the feedback button in the app.