Edit the intent from the page

Steps

1. 1 Administrator Open the agent panel 0:03
2. 2 Administrator Mint the reviewer's token 0:05

   end2end owns the journey layer, so it is the agent that applies an edit to a workflow file.

3. 3 Administrator Open the site menu 0:08

   The collapsed bar is one row at every role; the full role-gated navigation lives in this panel and closes as soon as you leave.

4. 4 Administrator Open the knowledge browser from the menu 0:09 ▣

   Plans, workflow files, journeys, rules and the owner's own notes — one browser, because they already share a format.

5. 5 Administrator Open the workflow file 0:10 ▣

   Reported by the agent from its own synced worktree — never read off this server's disk, which is days behind by construction.

6. 6 Administrator Read the 'why' log and find the reasoning wrong 0:13 ▣

   Sections are the unit: the builder writes AS-BUILT, the reviewer writes Journey review. One textarea over a whole file is how two agents and a person clobber each other.

7. 7 Administrator Correct the sentence 0:14 ▣

   Editing a workflow file is editing what the fleet reasons from next, so it needs the control key as well as an admin session.

8. 8 Administrator An agent rewrote that line first — the save is refused 0:16 ▣

   Refused, never merged — a correction landing silently on a paragraph that moved would be applied to text the owner never read. And the draft stays put: re-applying is a copy, not a retype.

9. 9 Administrator Press Save again — the same words, not typed twice 0:17 ▣

   The refusal was about the text, not about the person. Nothing was re-entered — the draft never left the box.

10. 10 Administrator end2end picks it up, commits and pushes 0:20 ▣

    The next agent that searches this workflow reads his correction, not the inference. That is the whole feature.

11. 11 Administrator The command drawer shows it landed 0:22 ▣

    Same drawer plan 123 already renders — one place where everything asked of an agent finishes.