A cabinetmaker’s customized Blueprint answers a typed question about a short joinery clip. How should that software outcome be counted?
Select an answer to reveal the explanation.
Short Explanation
When the Blueprint answers the question about the clip, the software path is live. Charting comes later; authenticity is a different desk—Domain 4 can call this done.
Full Explanation
When a cabinetmaker’s customized Blueprint answers a typed question about a short joinery clip, count that software outcome as Domain 4 done: a working customized video+text Blueprint is the implementation goal. Charts, authenticity reviews, and CLIP still regeneration are separate desks. Civic go-live for Domain 4 can declare the path live when answers return for clip+question.
Calling it unfinished until Domain 5 charts every answer in a dashboard fails by holding implementation hostage to evaluation packaging. Calling it Domain 7 authenticity clearance required before any answer may appear misorders domains. Calling it incomplete until CLIP regenerate replaces every clip frame with a still fails the video job.
Exam caveat: Domain 4 completes on a working customized VIA Blueprint answering video+text. Operational check: accept civic Domain 4 done when customized VIA answers clip questions; schedule Domain 5 charts and Domain 7 authenticity as separate workstreams. Align this choice with the agency’s published multimodal runbook so civic operators can audit why the configuration was accepted. Document the VIA Blueprint customization (inputs, query shape, host) in the civic runbook and verify one clip-plus-question answer end-to-end before any scale discussion.