A compass-maker exposes denoising steps as a call argument so a later experimenter can change it. What skill does that represent?
Select an answer to reveal the explanation.
Short Explanation
Putting a dial on the generator call is wiring, not judging which setting looks prettiest. The knob exists now; the beauty contest is Domain 1 later.
Full Explanation
Exposing denoising steps as a call argument so a later experimenter can change it is implementation: wiring inference-step count as a parameter of the generator call. That skill classification is correct for the compass-maker. Civic generative services should expose such controls in software so Domain 1 beauty bake-offs can reuse the same call path.
Calling it Domain 1: running the beauty bake-off that picks the prettiest step count fails—wiring the parameter is not the bake-off itself. Calling it Domain 3 paired audio–transcript collection fails modality. Calling it Domain 6 replacing the parameter with a Kubernetes autoscaler fails by swapping generation controls for cluster scaling.
Exam caveat: parameterization of generate calls is Domain 4 implementation. Operational check: add step-count (and related) args to civic generate APIs; keep Domain 1 experiments as consumers of those args, not as substitutes for wiring. Align this choice with the agency’s published multimodal runbook so civic operators can audit why the configuration was accepted. Record the civic software choice in the service README—named modules, inputs, and domain—so operators can replay the same path during audits and handoffs.