Proposal before execution.
Pattern recognition does not grant permission to act.
04 / AUTOMATIONS
Automate repetition.
Not judgment.
A repeated process can become a suggestion—not a surprise action. The planned automation layer begins with something you can inspect.
FROM PATTERN TO PROPOSALShow the work
Show the work
before doing it.
01Recognize a repeated procedure.
02Make the proposed steps visible.
03Ask for the exact scope needed.
04Keep consequential actions gated.
Example candidate
Weekly competitive scan
A repeatable research process, ready for you to review.
Read selected sourcesOptional
Create a draftOptional
Publish or sendNot permitted
Access other accountsNot connected
Concept only. No tools connected; nothing will run.
An inspectable boundary.
The demonstration keeps read access, drafts, and external writes visibly separate.
Not now is a valid choice.
Review a candidate without turning it into an obligation.
BEFORE ACTION
A proposal should answer the obvious questions first.
The planned automation layer should expose the same information a careful person would want before granting permission.
01What repeated?
The pattern or workflow that caused the suggestion.
02What will it read?
The specific inputs and sources required.
03What will it do?
The steps and tools involved, before execution.
04Where can it stop?
Approval checkpoints and boundaries for consequential actions.
05What happened afterward?
A reviewable record of the approved run.
The next step is yours.
Follow progress without enabling any automation.