Overview
GrokBot is a planned assistant that drafts updates (a Now entry, a note, a project change) from my own notes and submits them as proposals. A person reviews and approves every one.
The problem
Keeping a site current takes small, regular edits. The risk with automating them is publishing something wrong or private.
Context and motivation
I am exploring agent workflows where the AI proposes and a human decides.
My role
Design and build.
Approach
Every change is a pull request. The agent never has permission to publish, only to propose.
Technical architecture
Planned: read allowlisted Notion fields, validate them against the site's schemas, write a draft file, and open a pull request with an audit trail.
Implementation
Not started. The site's docs/GROKBOT.md describes the interface it will use.
Trade-offs and decisions
Human approval makes publishing slower and makes it safe. That trade is deliberate.
Results and impact
Not applicable yet.
Lessons learned
To write.
What's next
Define the proposal format, then prototype against the validation script.
Links and resources
To add.