Input Fields

Beyond requirements and documents, a design needs a handful of structured facts. The input fields capture them once, in one place, and each one has a concrete downstream effect; none of them is decorative.

Field	What It Does Downstream
Solution summary and narrative	The primary statement of what to build and what is in or out of scope; generation designs to it and respects stated exclusions
Data classes (PHI, PCI, PII, ...)	Sensitive classes force the security tiers: dedicated identity and secrets/key-management appear in the design, and flows carrying those classes are held to encryption expectations
Data residency	Recorded as a constraint the design and its documents carry
Threat profile	Sets the risk posture the design and its review are judged against
Resilience targets (RTO / RPO / availability)	Shape deployment choices, including replica counts where targets imply them

Say It in the Field, Not in Prose

Anything with a field belongs in the field. "We handle cardholder data" buried in the narrative is a hint; PCI selected as a data class is a rule the whole pipeline enforces: generation, compliance scoring, review, and the documents.

Scope Statements

The narrative's out-of-scope statements are honored end to end: what you exclude is recorded in the design's metadata, generation will not add it, and a re-run that tries is caught by the scope guard.