Cathy Miller

Cathy Miller is the new operations coordinator at Brightfield Commerce, three weeks into her role when Issue 1 opens. She receives an unusual return request — a customer wants to return a $340 gift order and the original purchaser is unreachable. She opens the operations wiki. She finds a Notion page titled "Returns Handling SOP v2 FINAL (updated)." She reads all seven pages. She still does not know what to do. She messages her manager. Her manager messages Maya Chen. Maya answers in two sentences. Cathy is back on track in four minutes.

She is the publication's opening scene and its founding argument — the evidence, stated once and in full before Issue 1's framework section begins, that documentation built for the person who wrote it rather than for the person who needs it is not operational infrastructure. It is institutional decoration.

The seven-page SOP she read contained the standard return process, the holiday return policy, the process for damaged items, and a section called "edge cases" that listed seven exceptions. It did not contain the answer to her question. It was, in the strictest technical sense, complete. It had failed the only test that matters: a person who needed an answer in under two minutes read it for an unspecified period and still did not have the answer.

Maya Chen deletes the documentation system and starts over partly because of Cathy. But the pattern she represents is the analytical starting point for everything the SOP Library framework recommends. The documentation was built for the author, not for the user. Specifically, the user who needs it when the author is unavailable. That distinction is the mechanism Issue 1 names as the root cause. Cathy is the mechanism expressed as a person.

What she is known for: Being the inciting character of Issue 1 and the publication — the new hire who reads seven pages of technically complete documentation and still cannot answer a customer's question, establishing in a single scene why the SOP Library framework exists.