lane_review

Category: jobs_lanes
Access: write
Audience: advanced (ordinary users do not normally call this directly)

Purpose

Reviews one lane for coordination only. Call it to submit finished lane work for approval, or to approve or request changes, without moving the lane's execution standing.

Arguments

Required: lane_id, decision.

lane_id.
decision. Note: submit, approve, or request-changes. submit is by conductor or the lane assignee; approve and request-changes are conductor-only.

Result

JSON object with lane_id and review_state (pending, approved, or changes_requested).

Boundaries

Verdict privilege is checked before entry access, so denied verdicts reveal nothing about the entry. Submit loads the entry first (parent-quorum visibility applies) and then needs conductor standing or assignee match. Review records authority and never moves execution standing. The pump never writes review standing.

Lifecycle / side effects

Moves review standing (empty or changes_requested to pending on submit; pending to approved or changes_requested on verdict) and records an audit/history event. Completing a job never moves review standing.

Errors

Missing, malformed, or inaccessible lane reads as unknown_lane. Submit by a caller who is neither conductor nor assignee is denied. Re-submit over a decided review is rejected as review closed; verdicts with nothing pending are rejected as nothing under review.

Example

{
  "decision": "approve",
  "lane_id": "<uuid>"
}

Result shape:

{
  "lane_id": "<uuid>",
  "review_state": "approved"
}