An analyst keeps creativity settings low when factual permit checklists must stay deterministic. What technique awareness is shown?

Factual civic checklists need stable generation behavior. Keeping creativity settings low when permit checklists must stay deterministic shows awareness of controlling creativity versus determinism: lower randomness favors consistent step lists that match code and SOP wording. Permit applicants and reviewers are harmed when tuning frequency penalty to control creativity versus determinism in civic checklist tasks is mistaken for determinism control, because repetition handling cannot ensure stable step lists.

Tuning frequency penalty to control creativity versus determinism in civic checklist tasks fails because frequency penalty adjusts token repetition, not the creativity setting that keeps factual checklist generation deterministic. Applying retrieval augmentation to control creativity versus determinism in civic checklist tasks fails because it grounds content but does not control the randomness that legal checklists cannot tolerate. Structuring detailed prompts to control creativity versus determinism in civic checklist tasks fails for the same determinism reason—detailed instructions do not prevent creative paraphrase from altering enforceable meaning if randomness stays high.

Exam caveat: low creativity reduces variance; it does not update the checklist when the code changes. Deterministic settings must be paired with versioned source requirements from the current ordinance or SOP.

Operational check: set generation parameters to low creativity for checklist tasks; pin prompts to a named code version; compare outputs across sample runs for drift before publishing the checklist to the permitting portal.