Live
Powered by

Weekly Philosophy Review Protocol

  • Owner: Coach Luca (coordinator)
  • Triggers: Sunday evening or Monday morning, before the rolling 3-week outline is reviewed
  • Frequency: Weekly, non-skippable

Purpose

This protocol ensures that the knowledge layer (knowledgebase entries and PHILOSOPHY.md files) remains current and connected to live coaching decisions. It runs as an explicit step in the weekly planning cycle, before the rolling 3-week outline and 7-day schedule are set.

Sequence

Step 1: Check for new or revised knowledgebase entries

Scan all five workspace-{agent}/knowledgebase/ directories for entries added or modified since the last review. Note any new entries.

Step 2: Review specialist philosophy files

Read each specialist PHILOSOPHY.md:

  • team/endurance/PHILOSOPHY.md
  • team/nutrition/PHILOSOPHY.md
  • team/recovery/PHILOSOPHY.md
  • team/strength/PHILOSOPHY.md

For each, check:

  • Has anything changed since the last review?
  • Are the "Current application to Sidney" sections still accurate?
  • Are any open questions now answerable?
  • Have any decision rules been contradicted by recent coaching experience?

Step 3: Update specialist philosophy files if needed

If a specialist's PHILOSOPHY.md needs updating based on new knowledge, coaching experience, or changed athlete context:

  • Update the relevant sections.
  • Record the change in the "What changed since last review" section with today's date.
  • Note whether the change is informational or operationally significant.

Step 4: Coordinator synthesis check

Read team/coach-luca/PHILOSOPHY.md cross-agent synthesis section.

  • Are the identified tensions still accurate?
  • Have governing rules been tested by recent decisions? Did they hold?
  • Does a new tension need to be surfaced?
  • Does an existing governing rule need revision?

Update Coach Luca's PHILOSOPHY.md if needed.

Step 5: Downstream impact assessment

For any material philosophy change (not cosmetic or informational):

  • Does this affect the season plan? → Update athlete/season-plan.md.
  • Does this affect the rolling 3-week outline? → Update athlete/rolling-3-week.md.
  • Does this affect the rolling 7-day schedule? → Update athlete/rolling-7-day.md.
  • Does this affect readiness monitoring? → Update team/coach-luca/synthesis/readiness-protocol.md.
  • Does this affect morning/evening notes? → Update the relevant skill document.
  • If no downstream impact → Record "reviewed, no operational change" in the philosophy file's change log.

Step 6: Record review completion

Update the "Last reviewed" date in each PHILOSOPHY.md that was reviewed.

Review output categories

  • Unchanged: All philosophy files remain current. No downstream edits needed.
  • Refined: Minor updates to wording, open questions, or current application. No operational impact.
  • Materially changed: A belief, decision rule, or governing tension was modified. Downstream planning review is required before the 3-week outline is set.

Gate

The weekly planning cycle is incomplete if this review has not been performed. The rolling 3-week outline must not be reviewed or updated until this protocol has run.

Staleness rule

Any knowledgebase entry not reviewed in 12 months must be flagged as stale in its review status field. Any stale entry that still influences live planning must be refreshed before that influence continues.