Approval Workflow Comments Block for Ark UI

Edit GATES and PEOPLE. A gate has an id, a name, an owner (a person's id) and two alternates the owner may hand it to; the order of the list is the order of the gates, and the status words and the log are all worked out from it. PROPOSAL holds the title and text, and AUTHOR is the person who resubmits. Names are made up here.

Approve advances the proposal one gate and clears the note. Request changes needs a note, sets the proposal back with the author and logs the note; until the author presses Resubmit the other buttons stay in place but refuse, and say so. Hand over changes the gate's owner and logs who gave it to whom. Once the third gate is approved the primary reads Approved and the rest refuse.

The stage, the owners and the log live in the page, and the times in the log are a fixed step after a typed moment, not the clock. Nothing is sent, so nobody is told. To wire it, send each decision from the three handlers, check on the server that the person deciding owns the open gate, store the decision with its real timestamp and return the new stage; the page then shows what the server answered.

The gates are an ordered list and the open one carries aria-current set to step; state is written in words (Approved, Waiting for a decision, Back with the author), never by colour alone. The note field has a visible label and its problem is tied to it with aria-describedby. Disabled-looking buttons use aria-disabled so they stay focusable and a press explains itself, and the status line is read out politely.

The gates stack above the proposal as a short vertical list, the buttons wrap, and the log keeps its height with its own scroll. The select and Hand over button sit on one row when there is room and wrap otherwise.

That block routes a single review through checks. This one is about owners: each gate has a named person, a gate can be handed to someone else, and sending the proposal back needs a note that lands in the log.