An organ-pipe shop wants a single program that reads a pipe photo and a pitch note, then produces one output. How should that minimal multimodal path be sketched?
Select an answer to reveal the explanation.
Short Explanation
One program, one trip: load the photo and the note, encode them, optionally fuse, then hit the head. Keep it a thin forward path, not a textbook.
Full Explanation
A minimal multimodal path that reads a pipe photo and a pitch note then produces one output should be sketched as load → encode → (optional fuse) → head inside one framework project. That sketch is correct for the organ-pipe shop: one forward path joins the arms rather than two unrelated scripts. Civic multimodal services need the same single-project spine so operators can trace outputs to joined inputs.
Two unrelated scripts that never share a forward pass fail joint multimodal inference. A full training textbook covering every loss schedule before any load call fails by blocking implementation with curriculum. A Helm chart that replaces the need for encoders and a head fails: packaging is not a model path.
Exam caveat: associate multimodal apps are one framework forward path, optionally fused. Operational check: implement civic load/encode/(fuse)/head in one project and verify both modalities reach the head before packaging talks. 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.