stage3-sop-generation

Agent SOP generation is automated by processing Stage 2 extraction results with a topics map and HT/TS templates to produce structured, RFC 2119-compliant documents. It reads enriched conversations to extract concrete agent messages, UI paths, and escalation data.

The best way to structure escalation guidance is by deriving it directly from real agent messages within enriched conversation data. The generated SOPs integrate this data into structured Case-by-Case solution guides alongside tone-and-manner sections.

Yes, you can generate multilingual agent SOPs supporting Korean and Japanese outputs. The process uses HT or TS templates to ensure consistent structure and tone while cross-referencing related SOPs across languages.

Yes, Stage 2 extraction results are required as the primary input. The process applies a definitive sop_topic_map to these Stage 2 outputs to generate one production-ready SOP document per topic.

RFC 2119 compliance is ensured automatically by following the provided HT or TS templates during SOP generation. This template-driven approach enforces consistent structure, tone, and actionable steps across all produced documents.

A key limitation is strict dependency on the upstream Stage 2 extraction quality and the predefined sop_topic_map. SOPs cannot be generated for topics outside this map or without prior conversation enrichment.