THE PROBLEM
Why this system existed
Plain-English infrastructure requests must become consistent, policy-compliant configurations without allowing uncontrolled production changes.
IaC · Tool Use · Policy
InfraSpeak — Network Infrastructure Provisioning
A three-stage pipeline from structured intent to allowlist checks to configuration generation, with secrets masking and policy controls.
MY ROLENatural-language provisioning, policy validation, and controlled execution
SCOPEA natural-language interface that converts infrastructure intent into validated Terraform and Ansible configuration with mandatory engineer approval.
EVIDENCEProfessional experience · public-safe summary
60%faster provisioning
74%fewer template errors
0credential exposures reported
OUTCOME
What changed
Cut infrastructure provisioning cycle time by 60% and manual template errors by 74%.
REFERENCE ARCHITECTURE
Controls around the model
01Classify
02Route
03Retrieve
04Rerank
05Generate
06Validate
07Observe
DECISIONS
Trade-offs considered
Intent before generation
Topology allowlist checks
Secrets masking
Mandatory network-engineer approval
FAILURE CASE
What did not work
Domain-specific telecom vocabulary caused intent errors; a retrieval-backed glossary reduced ambiguity before configuration generation.
SECURITY BOUNDARY
Public-safe by design
This case study exposes patterns, not employer architecture. It uses synthetic data, no client identifiers, no internal prompts, no proprietary datasets, and no production endpoints.