Q3 / July - September 2026
Scorecard
Track whether the important domains are improving, steady, or drifting. Scorecard turns scattered evidence into a weekly operating picture.
average
6/10
watch
2
check due
3
declined
1
Signals
Consistent energy available for work, training, and relationships
score 7/10 / target 8/10 / Daily pulse plus Sunday review
Leading: Sleep window protected, recovery plan followed, meals not skipped.
Lagging: Training adherence and build output stay steady without late-day collapse.
Check 5 July
Cash, obligations, and next decisions are visible before they are urgent
score 7/10 / target 9/10 / Friday money review
Leading: Upcoming obligations and runway are reviewed before the week closes.
Lagging: No surprise bills, no avoidant money decisions, and savings progress is visible.
Check 10 July
Important people get small consistent touchpoints
score 5/10 / target 8/10 / Sunday reset
Leading: A specific touchpoint is scheduled before the week fills up.
Lagging: Family and friends feel present in the system rather than remembered late.
Check 5 July
Latest: Declined / Roles and attention budgets show relationships are visible but still lightly loaded.
Protected build blocks happen before reactive admin
score 6/10 / target 8/10 / Daily attention log
Leading: Deep build block starts before dashboards, inboxes, or admin loops.
Lagging: Complete useful product slices reach GitHub without repeated context switching.
Check 5 July
Latest: Steady / Multiple complete Sensei layers reached GitHub, but deployment quota checks caused repeated context switching.
5 July
Create
Evidence
Roles and attention budgets show relationships are visible but still lightly loaded.
Next: Run the relationship touchpoint playbook during the next Sunday reset.
Multiple complete Sensei layers reached GitHub, but deployment quota checks caused repeated context switching.
Next: Use one bounded Vercel check per work cycle, then return to product progress if blocked.