capture's triage routes (defect fix / promote to intent / brief fix / wontfix) force frame-level unease into artefact-level fixes: there is no hold route for a finding whose real content is that the framing itself cannot yet be articulated. A hold-with-axes route is missing — non-articulation is data, holds carry axes and exit by articulation. Candidate RFC or intent; decompose before filing. Ties to the 03-evidence placeholder resolution (where would a hold-register-shaped record live?).

capture's triage routes (defect fix / promote to intent / brief fix / wontfix) force frame-level unease into artefact-level fixes: there is no hold route for a finding whose real content is that the framing itself cannot yet be articulated. A hold-with-axes route is missing — non-articulation is data, holds carry axes and exit by articulation. Candidate RFC or intent; decompose before filing. Ties to the 03-evidence placeholder resolution (where would a hold-register-shaped record live?).

Narrowed 2026-08-27 by the cold-reading workstream: the disposition record reserves the two-axis hold field (frame-location × MoSCoW), present in its schema and unpopulated, and its held state carries a required exit_condition — directional, exiting by articulation. When this triage route is filed it adopts those axes and that state vocabulary (typed link refines the detection-and-disposition-records intent) so the interview's hold register, the disposition record, and the triage route carry one taxonomy, not three. The home question stays open.

Remedy grounds (2026-09-29)

• The cold-reading workstream already reserved the axes and the held state (itd-180), so the route adopts one taxonomy rather than a third; the shape is local and no outside practice was consulted.
• Rejected: a new hold folder in the issue ledger, since folder membership is the ledger's status signal and a new folder changes every reader.