Systems owner

10 docs · updated 2026-08-11

Last 90 days · showing 10 of 10 ·
Explainers
Applying agentic coding practices to knowledge workHow the agentic coding course's practices map onto knowledge work: what transfers unchanged, what needs adaptation, what to leave alone.2026-08-11→
Reference
Systems hubIndex of the business systems hub: doctrine, system folder anatomy, and how to add a system.2026-08-01→
LinkedIn
LinkedIn system: appointment settingThe conversation engine: openers, the A-K follow-up decision table, the numbers, CRM fields.2026-08-01→LinkedIn system: finding people in ICPThe fill lane: ICP definition, the leads.db well, daily connection requests, weekly withdraw.2026-08-01→LinkedIn system: commentingThe 10-a-day comment rep: two buckets, the NocoDB Comment Queue routine, and comment craft.2026-08-01→LinkedIn system: posting contentDaily rep and per-post procedure: cadence, locked inputs, hook and body pass checks, the five templates.2026-08-01→LinkedIn systemGoal, full-system graph, four subsystems, and the roadmap for the LinkedIn outreach system.2026-08-01→
YouTube
YouTube: automation roadmapThree candidate machine parts, none specced until 2+ weeks of manual reps; reuses the Vision151 silence-cut prototype.2026-08-01→YouTube: manual layerWeekly and daily YouTube reps plus three build-once foundations. Three open inputs: operator, cadence, slot days.2026-08-01→YouTube: big pictureConstraint, input, process, and output of the YouTube system, on a slow compounding loop.2026-08-01→