Version: v0.1
Date: 2026-08-26
Status: Drafted in-session under completion-program P-1 (ruled: yes).
Occasion: B-100 (standing-notes/dunin7-build-list-v1_07), rank 6 of the completion program's Wave 1, clause 1. Filed 2026-08-14 from the E0128 walk. The filing's own sequencing ruling: "placement first, it needs no design ruling" — the composer-recognition alternative brushes B-98 face 2 and stays unbuilt.
Cites: CR-2026-212 (B-98 face 3 — the panel itself); the walk observation (the answer pasted into the composer twice, captured as duplicate held notes with no finding linkage).
CandidateFindingsPanel mounts above InEngagementHeader — the very top of the page, visually severed from the conversation surface the Operator worked in all session. The composer is the trained input habit; the observed result was the finding's answer typed into the composer twice.
The move: the panel renders inside the working surface — in the wide layout, at the top of the conversation column (the same column the composer lives in); in the narrow layout, directly above the mobile surface, below the header. The CandidateCommitBanner stays where it is: it is a banner, not an answer box, and nobody typed a commit into the composer. No behavior, fence, or content change to the panel itself — same props, same candidate + viewer-is-creator gate; only the mount moves.
Tests: the existing panel behavior tests stand unchanged (component-level, mount-agnostic); the surface test asserts the panel renders within the conversation column container rather than above the header.
DUNIN7 — Done In Seven LLC — Miami, Florida CR-2026-240 — The Findings Answer Box Moves to the Working Surface — v0.1 — 2026-08-26