Playbooks

Operating manual

Turn recurring situations into repeatable protocols. Playbooks keep good decisions available when energy, attention, or time is tight.

active

review due

partial

missed

Manual

Active playbooks

ProjectsActiveBuild

Clean deploy and domain check

A new Sensei or Foundry layer is ready to publish and must not disturb the domain split.

Steps:

Run lint, build, audit, and a protected-route smoke test
Push a scoped commit to the Melbourne Foundry repo
Deploy the linked Vercel project only
Verify sensei subdomain is protected and public Foundry still renders separately

Success: The new layer is live on Sensei, private access still works, and www remains public Foundry.

Fallback: If Vercel quota blocks deploy, push to GitHub and record the exact blocker.

Review 8 July

Latest: Partial / GitHub updates shipped, but Vercel blocked production deployment because the Hobby team hit its 24-hour deployment quota.

FitnessActiveRecovery

Low energy day

Pulse, sleep, or stress says the body is not available for full-intensity output.

Steps:

Reduce the work list to one must-do and one useful small win
Move hard training to recovery or mobility
Eat a real meal and protect the sleep window
Log the adjustment in Pulse or Recovery

Success: The day stays useful without borrowing from tomorrow's health.

Fallback: Do a 10-minute walk, hydrate, and close one tiny loop.

Review 9 July

PersonalActiveHome

Sunday weekly reset

It is Sunday or the week feels scattered and the operating system needs a clean reset.

Steps:

Review overdue commitments, risks, and role reviews
Clear the inbox into tasks, notes, or archive
Plan meals, training, recovery, and home maintenance
Choose the top three outcomes for the next week

Success: The next week has visible priorities, no hidden urgent admin, and a realistic recovery plan.

Fallback: Run a 20-minute reset: inbox, tomorrow, money obligations, and one home task.

Review 12 July

Latest: Worked / North Star, roles, principles, risks, and commitments are now visible enough to review.

PersonalDraftRelationships

Relationship touchpoint

A person has gone quiet in the system or a role review marks relationships as light.

Steps:

Pick one person from People or Roles
Send a specific low-friction message
Record the touchpoint and next contact date
Avoid turning connection into a large obligation

Success: A meaningful connection is made and the next touchpoint is visible.

Fallback: Send one honest check-in message and schedule the next reminder.

Review 14 July

5 July

Log run

Create

Add playbook

Evidence

Run log

PersonalWorked4 July

Sunday weekly reset

North Star, roles, principles, risks, and commitments are now visible enough to review.

Adjust: Make the dashboard show which playbook should run next.

Worked

ProjectsPartial4 July

Clean deploy and domain check

GitHub updates shipped, but Vercel blocked production deployment because the Hobby team hit its 24-hour deployment quota.

Adjust: Deploy from the linked project folder only and avoid temporary project creation when retrying.

Partial