Live-state extraction pipeline for enterprise Azure infrastructure. Auto-generated SDDs and PlantUML from the actual subscription state - not stale manual exports.
Azure infrastructure documentation required manual extraction from subscription exports - 2–3 days per project. PlantUML diagrams were authored by hand from memory or stale exports. Documented architecture drifted from live infrastructure with no mechanism to detect or correct divergence. At 104 resource groups per engagement, the manual approach couldn't scale - every new deployment meant the documentation was already out of date before it was finished.
Live-state extraction pipeline: the engine accepts a subscription ID and automatically produces system design documents and PlantUML diagrams via automated inventory extraction, network flow mapping, security configuration analysis, and dependency graph construction. Few-shot LLM prompting grounds architecture rationale in extracted inventory - every generated component maps to a verified live resource.
Validation guardrails cross-check every generated component against extracted inventory before the document is produced. Hallucinated topology cannot reach governance documents - the guardrail layer rejects any component without a matching live resource match. Outputs are regenerated from live subscription state each run, with no cached snapshots.
Documentation turnaround: 2–3 days → ~2–3 hours. Average 104 resource groups per engagement handled automatically via subscription scan. Manual PlantUML authoring eliminated. Zero fabricated components - live-state grounding replaced manual transcription across every generated artifact.