SOPs

The people who run the process should review the process doc.

The team flags a stale step. Agent connect removes it and renumbers the rest.

Set it up for your agent How agent connect works

livesops/returns-processing.md

Returns processing

Owner: Keisha Grant. Floor: Fernhollow Outdoors. Photos happen at packing.

Returns SOP for the Fernhollow Outdoors floor. Photos happen at the packing bench. The dock 2 camera has been down since July, and this file should match the step the shift actually runs.

Notes

Dock 2 camera: down since July. Do not send a return back out there for a photo.

Photograph at packing. Include the label and any damage in the same frame. That single frame is the only photo this SOP asks for. Do not send the return to dock 2 for a second one.
A return with no photo does not go to restock. Set it aside for the lead.

Steps

Receive the return at the packing bench and scan the label before you open it.
Photograph the item at packing. One frame with the label readable, and the damage in that same frame.
Restock what you can sell. Scrap the rest with a note in the bin log, including the return id.
Email the member when the label prints. Photograph again on the dock 2 camera and file the July sheet.Stop after restock or scrap. The August step, a second photo on the dock 2 camera, is not a step.

Exceptions

Damaged shipments skip restock and go to the scrap bin with a note. Do not photograph them twice.
If the label will not scan, the lead logs it. Do not invent a dock photo.

Dock 2 camera

Rosa Nguyen

The dock 2 camera has been down since July. Photograph at packing is the step we still use.

Dmitri Volkov

Photos happen at packing now. The old step should go.

Photograph again on the dock 2 camera

Dmitri Volkov

@agent we stopped doing step 5 in August, remove it and renumber.

agent

Removed the August step and renumbered. Photos are at packing.

resolved

Start with @agent to ask the agent

ResolveReply

Fictional example: a Fernhollow Outdoors returns SOP in Gander, with a teammate thread and a scripted agent connect reply.

How SOPs get reviewed today

A wiki is a good home for a stable SOP. Comments there do not reach the agent that is rewriting the draft from last month's version.

A floor walk catches the stale step and depends on someone remembering to edit the file. A meeting can do the same, once everyone is off the floor.

Step 5 is gone

Keisha Grant asks her agent to draft Fernhollow Outdoors' returns SOP from the old wiki page. She runs gander watch on sops/returns-processing.md and sends the link to Dmitri Volkov and Rosa Nguyen.

Rosa highlights the photo step and says the camera at dock 2 has been down since July. Dmitri replies that they photograph at packing now. Human thread.

Dmitri starts a new comment: "@agent we stopped doing step 5 in August, remove it and renumber." Keisha's agent deletes the step, renumbers, replies, and resolves the thread. Rosa sees the shorter list on the same link. The SOP can move back to the wiki when the floor agrees.

Who's in the doc

WriterTeam leadTeammateThe author's agent

Writer Ops lead. Sends the draft to the people who run it.

Team lead Knows which step the floor actually skipped.

Teammate Checks the doc against yesterday's shift.

The author's agent Removes the stale step when the lead uses agent connect.

Reviewers only need a browser. Talk to each other in normal threads. Use agent connect when you want the draft changed.

Agents that fit sops

Grok BotA process draft from the old page, with agent connect through MCP.

Claude CodeWhen the SOP lives in a repo, MCP returns agent connect to the author.

Grok BuildA job can drop an updated SOP into a folder the team already watches.

Let the floor delete the stale step on the live SOP, before the wiki says otherwise.

See how it works on the homepage