krites verdict¶
Description¶
Override krites' verdict for a single frame, recording it as a manual decision that survives a re-cull. This is the CLI counterpart to flipping a verdict in the studio.
A verdict is a label, never a file operation: the override is
written to .krites/verdicts.yaml with an override: true flag, and the original
is never touched. The machine's reasons are kept beneath the override,
recording why krites had ruled as it did. A subsequent krites cull
keeps your override rather than overwriting it.
Re-culling does, however, refresh what the machine thinks. Your verdict,
rating and decided_at are yours and never move, but proposed and reasons
are rewritten to the current ruling under the current profile. That is deliberate:
it is what lets you see krites come to agree with you as you tune a profile, which
a frozen proposed would hide — and it stops the stored reasons describing
thresholds that are no longer in force.
The shoot must already be registered with krites ingest.
Usage¶
<frame> is the frame's name as listed in the shoot manifest. The shoot is taken
from --shoot, or the current working directory if omitted.
Flags¶
| Flag | Description | Default |
|---|---|---|
--shoot |
Shoot directory to scope to | the current directory |
--output |
Output format: text or json |
text |
Examples¶
# Rescue a frame krites rejected
krites verdict --shoot ~/shoots/smith-wedding 03-dark.jpg keep
# Demote a keeper to review-later
krites verdict 11-candid.jpg maybe
An invalid verdict value, or a frame not in the shoot, fails cleanly before any write.
See also¶
krites reset— clear an override, returning a frame to its post-ingest state.krites cull— (re-)judge the shoot; overrides survive.