STORM Document Generator

// Research Depth Options
{
  shallow: {
    documents: 5-10,
    timeSeconds: 15-30,
    detail: "Quick overview, limited depth"
  },
  moderate: {
    documents: 15-25,
    timeSeconds: 45-60,
    detail: "Balanced coverage, good for most reports"
  },
  deep: {
    documents: 30-50,
    timeSeconds: 90-120,
    detail: "Comprehensive, exhaustive research"
  }
}

In-text: (Smith, 2024, p. 15)
Reference: Smith, J. (2024). Risk Assessment Methodologies. 
           Insurance Journal, 45(3), 123-145.

In-text: (Smith 15)
Reference: Smith, John. "Risk Assessment Methodologies." 
           Insurance Journal, vol. 45, no. 3, 2024, pp. 123-145.

In-text: Smith 2024, 15
Reference: Smith, John. 2024. "Risk Assessment Methodologies." 
           Insurance Journal 45 (3): 123-145.

In-text: [1]
Reference: [1] J. Smith, "Risk Assessment Methodologies," 
           Insurance Journal, vol. 45, no. 3, pp. 123-145, 2024.

// Available Models
const models = {
  "gpt-4-turbo": {
    quality: "Highest",
    speed: "Slower (15-20 min)",
    cost: "$$$",
    bestFor: "Critical reports, grant applications, legal documents"
  },
  "claude-3-sonnet": {
    quality: "Very High",
    speed: "Moderate (10-15 min)",
    cost: "$$",
    bestFor: "Most reports (recommended), policy documents"
  },
  "gpt-3.5-turbo": {
    quality: "Good",
    speed: "Fast (5-8 min)",
    cost: "$",
    bestFor: "Draft documents, quick summaries, internal memos"
  }
};

// Example: Risk Assessment Report
Topic: "Comprehensive property risk assessment for 123 Main Street, 
San Francisco, CA. Property value: $2.5M, built 1965, wood frame 
construction. Analyze flood, earthquake, and wildfire risks using 
FEMA HAZUS methodology."

// Example: Compliance Report
Topic: "SOX 404 compliance audit for Q4 2024. Focus on internal 
controls over financial reporting for publicly traded manufacturing 
company. Identify gaps in current controls and provide remediation 
plan with timeline."

// Example: Policy Document
Topic: "IT Security Policy for municipal government. Cover data 
classification, access controls, incident response, acceptable use, 
and BYOD guidelines. Align with NIST Cybersecurity Framework and 
state data protection regulations."

Key Points:
1. Earthquake risk is primary concern due to proximity to San Andreas Fault
2. Property is in FEMA Flood Zone X (minimal flood risk)
3. VHFHSZ wildfire zone designation requires mitigation analysis
4. 1965 construction predates modern seismic codes
5. Estimated annual loss must include all three hazards
6. Mitigation recommendations should prioritize seismic retrofit

Key Points:
1. Current SOX 404 controls documented but not tested in 18 months
2. Three material weaknesses identified in previous audit
3. Management representation letters lack required sign-offs
4. IT general controls need strengthening (access provisioning)
5. Remediation must be complete before Q1 2025 audit

🔍 Researching: "earthquake risk assessment methodologies"
📄 Found 47 relevant documents
📊 Analyzing: FEMA HAZUS documentation (relevance: 0.95)
📊 Analyzing: California seismic codes (relevance: 0.89)
✅ Research complete: 47 sources identified

# STORM's semantic search approach
def research_phase(topic, key_points, depth):
    # 1. Extract search queries from topic
    queries = generate_search_queries(topic, key_points)
    
    # 2. Semantic search with vector embeddings
    results = []
    for query in queries:
        embeddings = encode_query(query)
        matches = vector_search(embeddings, top_k=50)
        results.extend(matches)
    
    # 3. Deduplicate and rank by relevance
    sources = deduplicate(results)
    ranked = rank_by_relevance(sources, topic)
    
    # 4. Return top N based on depth setting
    return ranked[:depth_to_count[depth]]

1. Executive Summary
   - Overall risk assessment
   - Key findings
   - Critical recommendations

2. Property Overview
   2.1. Location & Description
   2.2. Construction Details
   2.3. Occupancy & Use

3. Hazard Analysis
   3.1. Earthquake Risk
       - Fault proximity analysis
       - PGA assessment
       - Ground motion estimates
   3.2. Flood Risk
       - FEMA zone designation
       - Base flood elevation
       - Flood depth analysis
   3.3. Wildfire Risk
       - VHFHSZ designation
       - Ignition probability
       - Fuel load assessment

4. Loss Estimation
   4.1. HAZUS Damage Functions
   4.2. Expected Annual Loss
   4.3. Probable Maximum Loss

5. Mitigation Recommendations
   5.1. Immediate Actions (0-30 days)
   5.2. Short-term Initiatives (1-6 months)
   5.3. Long-term Improvements (6-12 months)

6. Implementation Plan
   6.1. Cost Estimates
   6.2. Timeline & Milestones
   6.3. Resource Requirements

7. Conclusion

8. Appendices
   8.1. HAZUS Methodology
   8.2. Source Documents
   8.3. Glossary

// STORM's outline generation logic
function generateOutline(sources, key_points, template) {
  // 1. Extract topics from sources
  const topics = extractTopics(sources);
  
  // 2. Cluster related topics
  const clusters = clusterTopics(topics);
  
  // 3. Map clusters to template sections
  const sections = mapToTemplate(clusters, template);
  
  // 4. Ensure all key points are covered
  sections = ensureKeyPoints(sections, key_points);
  
  // 5. Order logically
  const ordered = orderSections(sections);
  
  // 6. Add subsections for depth
  const detailed = addSubsections(ordered);
  
  return formatOutline(detailed);
}

📋 Generated Outline (8 sections, estimated 15 pages)

✓ All 6 key points covered
⚠ Section 3.2 (Flood Risk) may be brief due to limited sources
✓ Balance: Even distribution across sections

[View Detailed Outline]
[Edit Outline Manually]
[Regenerate Outline]
[Approve & Continue]

Click: [+ Add Section]
Title: "Cost-Benefit Analysis"
Position: After "Mitigation Recommendations"
Depth: Moderate

Click: [✗] next to "Appendices"
Confirm: "Remove this section? Content won't be generated."

Drag and drop sections to reorder
Or use ↑↓ arrows

Section: "Hazard Analysis"
Current: Comprehensive (5 subsections, 6 pages)
Change to: Brief (2 subsections, 2 pages)

📝 Writing Section 1/8: Executive Summary (15% complete)
📝 Writing Section 2/8: Property Overview (27% complete)
📝 Writing Section 3/8: Hazard Analysis (41% complete)
   └─ 3.1 Earthquake Risk ✓
   └─ 3.2 Flood Risk ✓
   └─ 3.3 Wildfire Risk (in progress...)
📝 Writing Section 4/8: Loss Estimation (55% complete)

Estimated time remaining: 8 minutes
[Pause] [Cancel]

# STORM's content writing approach
def write_section(section, sources, context):
    # 1. Filter sources relevant to this section
    relevant_sources = filter_by_relevance(sources, section.topic)
    
    # 2. Extract key information
    key_info = extract_information(relevant_sources)
    
    # 3. Generate section outline
    section_outline = create_section_outline(key_info)
    
    # 4. Write introduction
    intro = write_introduction(section, context)
    
    # 5. Write each subsection
    content = []
    for subsection in section_outline:
        text = generate_text(subsection, relevant_sources)
        citations = add_citations(text, relevant_sources)
        content.append(text + citations)
    
    # 6. Write conclusion/transition
    conclusion = write_conclusion(section, context)
    
    return combine(intro, content, conclusion)

// STORM's quality review checklist
const qualityChecks = {
  citations: {
    allValid: boolean,        // All citations link to real sources
    properlyFormatted: boolean, // APA/MLA/Chicago format correct
    noOrphans: boolean        // No citations without sources
  },
  consistency: {
    terminology: boolean,     // "risk assessment" not "risk eval"
    abbreviations: boolean,   // Define before using
    formatting: boolean       // Heading styles uniform
  },
  completeness: {
    allSectionsWritten: boolean,
    keyPointsCovered: boolean,
    minimumLength: boolean
  },
  coherence: {
    logicalFlow: boolean,
    noContradictions: boolean,
    transitionsSmooth: boolean
  }
};

⚠ Issue: Section 3.1 uses "PGA" without defining
✓ Fixed: Added definition "(Peak Ground Acceleration, PGA)" at first use

⚠ Issue: Section 4.2 references "Table 3" but table not included
✓ Fixed: Added Table 3 with loss estimates

⚠ Issue: Inconsistent citation format in Section 5
✓ Fixed: Standardized all citations to APA format

Risk Assessment Report.pdf (23 pages)

├─ Cover Page
├─ Table of Contents
├─ Executive Summary (2 pages)
├─ 1. Introduction (1 page)
├─ 2. Property Overview (2 pages)
├─ 3. Hazard Analysis (8 pages)
│  ├─ 3.1 Earthquake Risk
│  ├─ 3.2 Flood Risk
│  └─ 3.3 Wildfire Risk
├─ 4. Loss Estimation (3 pages)
├─ 5. Mitigation Recommendations (4 pages)
├─ 6. Implementation Plan (2 pages)
├─ 7. Conclusion (1 page)
├─ References (47 sources)
└─ Appendices
   ├─ A. HAZUS Methodology
   └─ B. Source Documents

// Edit specific section
editor.selectSection("3.1 Earthquake Risk");
editor.insertParagraph(
  "Recent USGS updates indicate increased seismic activity in the region.",
  position: "after:paragraph:2"
);

// Add table
editor.insertTable({
  section: "4.2 Expected Annual Loss",
  rows: 4,
  columns: 3,
  headers: ["Hazard", "Loss Estimate", "Probability"]
});

// Modify citation
editor.updateCitation({
  oldSource: "FEMA 2023",
  newSource: "FEMA 2024 (Updated)"
});

{
  pageSize: "Letter" | "A4",
  margins: {
    top: "1in",
    bottom: "1in",
    left: "1in",
    right: "1in"
  },
  fontSize: 11 | 12,
  font: "Times New Roman" | "Arial" | "Calibri",
  colorMode: "color" | "grayscale"
}

# Risk Assessment Report

## Executive Summary

The property at 123 Main Street faces significant seismic risk...

## 1. Introduction

### 1.1 Purpose and Scope

This comprehensive risk assessment evaluates...

[Source: FEMA HAZUS 5.1 Documentation, 2024]

{
  vectorStore: "ChromaDB",
  embeddingModel: "nomic-embed-text",
  dimensions: 768,
  topK: 50,                    // Return top 50 matches
  similarityThreshold: 0.7,    // Minimum relevance score
  chunkSize: 1000,            // Characters per document chunk
  chunkOverlap: 200           // Overlap between chunks
}

// If generation is slow, switch to faster model
if (generationTime > 15 * 60) {
  storm.switchModel("gpt-3.5-turbo");
  storm.resume();
}

{
  "name": "Municipal Risk Assessment",
  "description": "Standard risk assessment for city properties",
  "sections": [
    {
      "title": "Executive Summary",
      "required": true,
      "maxLength": 500,
      "subsections": []
    },
    {
      "title": "Property Information",
      "required": true,
      "subsections": [
        {"title": "Location Details"},
        {"title": "Building Description"},
        {"title": "Occupancy Type"}
      ]
    },
    {
      "title": "Hazard Analysis",
      "required": true,
      "subsections": [
        {"title": "Flood Risk", "sources": ["FEMA NFHL"]},
        {"title": "Earthquake Risk", "sources": ["USGS NSHM"]},
        {"title": "Wildfire Risk", "sources": ["NIFC"]}
      ]
    }
  ],
  "requiredFields": ["propertyAddress", "propertyValue", "yearBuilt"],
  "citationStyle": "APA",
  "defaultLength": "standard"
}

✅ "Comprehensive flood risk assessment for 123 Oak Street, Houston, TX. 
Property is in FEMA Zone AE with BFE of 52 feet. Analyze structure 
vulnerability (wood frame, 1985 construction) and estimate expected 
annual loss using HAZUS depth-damage curves."

✅ "SOX 404 internal controls audit for Q4 2024. Focus on IT general 
controls (access provisioning, change management, backup procedures). 
Identify deficiencies compared to COSO framework and provide remediation 
timeline with resource requirements."

✅ "IT Security Policy for 500-employee manufacturing company. Cover 
data classification, access controls, incident response, acceptable use, 
BYOD, and remote work. Align with NIST Cybersecurity Framework and 
include enforcement procedures."

❌ "Write about flood risk" 
   (Too vague - which property? what level of detail?)

❌ "Insurance policy document"
   (No context - what type? for whom? what coverage?)

❌ "glp exc CA 2024"
   (Unclear abbreviations - spell out "general liability policy exclusions")

Error: "Could not find enough sources on this topic"

Solution:
- Upload more relevant documents to your RAG library
- Broaden your topic to match available sources
- Use "Shallow" research depth if sources are limited

Error: "Generation timeout after 30 minutes"

Solution:
- Reduce document length setting
- Switch to faster model (GPT-3.5)
- Simplify topic and key points
- Retry with "Resume" button (progress is saved)

Error: "Rate limit exceeded. Please wait."

Solution:
- Wait 1-2 minutes and click "Retry"
- Switch to different model provider
- Contact admin to increase rate limits

Before: "Risk assessment for property"

After: "Comprehensive seismic risk assessment for 2-story wood-frame 
commercial building at 456 Elm St, San Francisco. Built 1972, no 
seismic retrofits. Analyze expected damage from M7.0 earthquake on 
San Andreas Fault using HAZUS building vulnerability curves for W1 
construction type."

Issue: Citations reference documents not in your library

Solution:
- Upload all referenced documents to RAG Management
- Wait for processing to complete
- Regenerate document

Issue: Citations formatted incorrectly

Solution:
- Select correct citation style in settings (APA, MLA, Chicago)
- Regenerate affected sections

Issue: Citation links don't work

Solution:
- Ensure documents are still in your library (not deleted)
- Re-upload documents if needed
- Use "Refresh Citations" in document editor