Skip to content

Weekly Lesson Review — Jim's Process

All lessons — VA-submitted via their Claude sessions, and Jim's own from his Claude sessions — queue in the response Sheet for Jim's weekly review. Jim approves or rejects each row, then routes approved lessons into the live knowledge base via scripts/lesson-router.py.

Cadence

Once per week (Monday morning, ~15 min). If volume spikes, do mid-week pass.

Process

  1. Open the response sheet: Knowledge Base — Lesson Submissions

  2. For each row with Status blank or "New":

a. Read the submission. Decide: - Accept as-is → format and route - Edit and route → rewrite for clarity, then route - Reject → mark Status as "Rejected"; reply to the VA explaining (if you want them to know) - Hold for context → ask the VA a clarifying question; mark Status as "Held"

b. For accepted rows, run the router: 

cat <<'EOF' | python3 scripts/lesson-router.py <category-slug> "Lesson title here"
<Body content — usually the "Why" and "How to apply" content from the form, possibly polished>
EOF
Category slugs are documented in scripts/lesson-router.py --help (or peek at the docstring).

c. Mark the row Status as "Routed — ".

  1. Commit + push: 

    git add knowledge/lessons/
git commit -m "knowledge: route N VA-submitted lessons from <date> batch"
git push

  2. VPS cron picks up the change within 10 min. No manual deploy needed.

  3. Optional: thank the VA. A "Hey, your lesson on X is now live at " message goes a long way.

When to Adjust

  • If 80%+ of submissions are getting rejected: the VA-GUIDE may be unclear on what counts as a lesson. Update it.
  • If you keep editing similar lessons for the same VA: give them direct feedback on format.
  • If submissions cluster in one category: consider promoting that category to its own dedicated SOP or sub-category.
  • If submission volume exceeds ~10/week: consider building the embedded form on knowledge.evolvebusiness.com (see plan doc for option B from 2026-05-20 discussion).