Review record fields
- reviewer_visible_candidate_route
- reviewer_visible_candidate_id
- reviewer_visible_candidate_file
- reviewer_visible_candidate_zones
- reviewer_visible_constraints
- reviewer_visible_blocked_conversions
- reviewer_selected_result
Human Review Result For Change Candidate
Records the human-result boundary for the root Workbench change candidate. This page does not modify the root Workbench.
Root Workbench · Root Workbench Change Candidate Receipt · JSON
result_scope: change_candidate_human_result_onlyselected_result: pendingresult_can_change_root: falseresult_can_place_panel: falseroot_patch_allowed_now: falsepanel_placement_allowed_now: falseStill blocked
- human candidate result -> root patch permission
- candidate slot result -> panel placement
Allowed review results
- pending
- candidate_visible_enough_for_route_change_receipt
- needs_candidate_zone_repair
- needs_candidate_constraint_repair
- needs_blocked_conversion_repair
- held_before_root_patch
- refused_for_authority_drift
Blocked conversions
- human candidate result -> root patch permission
- candidate visible enough -> route change
- review result -> implementation authority
- candidate slot result -> panel placement
- static Muse panel -> active guide
- candidate result visibility -> deployment readiness
Required before root patch
- root_route_change_receipt
Human review question
Can a human reviewer record a result for the root change candidate while root route change and panel placement remain blocked until a separate route-change receipt exists?
Seal
This receipt records a human result boundary for the root change candidate only. It does not change root, place a panel, activate Muse, open prompts, execute rungs, mutate state, deploy, approve work, or replace human review.