presort

To generate a read-only proposal for inbox classification without mutating bead state, use non-mutating read commands such as bd list, bd show, and bd find-duplicates to inspect open beads. The system outputs a per-bead proposal table with drop, grill, ready, or needs-input decisions for human action.

A pre-sort operation is a disinterested, read-only first pass over the UNREFINED inbox to surface provisional bead dispositions without mutating any state. It analyzes raw captures lacking a stage:ready marker and proposes drop, grill, ready, or needs-input actions for human review.

Yes, you can inspect raw captures in the UNREFINED inbox without changing their stage by relying on non-mutating read commands. The pre-sort mechanism scopes specifically to beads without a stage:ready marker, ensuring all body inspections and duplicate checks leave bead state intact.

To find duplicate beads in an unrefined inbox before deciding what to drop or grill, use the bd find-duplicates command. This read-only inspection identifies duplicates across raw captures and includes them in a per-bead proposal table to guide human disposition actions.

The limitation of using a proposal table for bead classification is that it only provides read-only suggestions and does not execute any state changes. Users must manually perform the proposed drop, grill, ready, or needs-input actions, as the pre-sort process strictly avoids mutating bead data.