Overview
Health check, key numbers, active flags and the team's running to-do list.
Resolve decision
Amend strategy doc
Manual process to keep the human in the loop. Update the .md file, then run the helper script to archive + register the new version.
Next steps after you save:
- Edit
data/nimble_strategy.md, update the YAML frontmatterversionto your new value + edit the body. - Run locally:
python3 archive_strategy.py --reason "…" --summary "…"
Then commit + push. This dialog marks the selected learnings as decided in Supabase so they leave the "Needs decision" list.
Edit section
Edits save immediately and are logged with your user + timestamp. Add a one-line reason if you want it captured.
Edit history
Explain this change
Overarching strategy
Activity Hub
Your attention inbox, team discussion, tasks, decisions, and the audit trail · everything operational in one place.
Full campaign playbook lives in Performance → Timeline. Tasks sync live across the team via Supabase.
Performance
Targets, timeline, milestones, and the numbers behind them.
Website
General site performance, everything outside the audit campaign LP. Helpful for organic + total brand picture.
Library
Reference docs for the team and the agent. Edit any doc directly, saves to Supabase and exports to data/ on next cron run.
Chat
Ask the agent about the campaign, the strategy, or anything in Library. The same analyst that writes the morning report answers here.
Setup
How the Nimble Growth OS works, what's connected, what we measure, what the agent does, what's on the roadmap. For the team to understand the system + for future developers to extend it.