A finding is not yet a change. "The page needs clearer structure" is useful, but an editor still needs to know what might change, where, why, what risk is involved and whether the change should move forward. Sam converts worker findings into structured proposed changes. He prepares the review layer without editing the page or applying anything.
For content analysis, approval preparation, review queues and safe-edit planning.
A worker may identify a real issue, but the next step should not be automatic editing. The proposed change needs context: what area is affected, why the change matters, how risky it is and what benefit is expected. Sam creates that decision layer.
↘ plan the change before editingThe page needs a stronger introduction and clearer next step.
Revise the introduction to clarify the page promise and add a relevant next step after the first section.
Sam maps findings to proposed changes. He does not rewrite, apply or publish. He prepares a human-reviewable plan that can move into Riley's queue or a later approval workflow.
SAM → Sam turns them into proposed changes the editor can evaluate.
He creates a planning layer before any content is touched.
Sam flags risk and evidence needs before it moves forward.
He prepares the structured items Riley can organise.
Sam labels what matters most and why.
He keeps proposed changes in review-only state until approved.
Sam does not edit the page, draft safe edits, apply changes or publish. He prepares proposed changes for human decision.
Sam turns findings into structured proposed changes so human editors can approve, reject or defer with context.
