Live
Powered by

Ownership Map

Shared Files

  • Owner: shared team doctrine
  • Writable by: human operator only when revising system doctrine
  • Readable by: all agents

Coordinator-Owned Areas

  • athlete/
  • intake/
  • team/coach-luca/

Coach Luca writes coordinator-owned athlete files under athlete/, including identity, settings, delivery, intake, planning, data, athlete-notes/, team/coach-luca/, and coordinator planning drafts. Specialists may read coordinator planning inputs when useful.

Coach Luca also owns the athlete calendar layer under athlete/calendar/, including live daily calendar files and archived calendar reference files.

Shared Canonical Log

  • athlete/logs/daily/
  • athlete/logs/weekly/

These files are shared at the section level, not owned as single-writer documents.

  • Coach Luca owns the file shell plus ## Summary, ## Activities, ## Coach Luca, ## Messages, ## System, ## Notes, and ## Open items.
  • Endurance owns ## Endurance.
  • Recovery owns ## Recovery.
  • Strength owns ## Strength.
  • Nutrition agent owns ## Nutrition.
  • Section ownership is defined here in this ownership map.
  • The live section-writing contract is governed by skills/athlete-daily-log/.

Endurance-Owned Areas

  • team/endurance/

The endurance specialist writes only in this workspace.

Nutrition-Owned Areas

  • team/nutrition/

The nutrition agent writes inside team/nutrition/ for shared domain material, inside athlete/logs/media/ for athlete-specific nutrition media, and inside the canonical athlete daily log for athlete-day nutrition records.

Recovery-Owned Areas

  • team/recovery/

The recovery specialist writes inside team/recovery/ for shared domain material and inside athlete/team/recovery/ for athlete-specific daily logs.

Strength-Owned Areas

  • team/strength/

The strength specialist writes inside team/strength/ for shared domain material and inside athlete/team/strength/ for athlete-specific daily logs.

Endurance-Owned Athlete Areas

  • athlete/team/endurance/

The endurance specialist writes athlete-specific durable logs in this area while keeping shared doctrine and domain files under team/endurance/.

Athlete Communication Boundary

  • Athlete communication coordinator: Coach Luca
  • Final outbound language-review and delivery gate: athlete-comms
  • Specialist outputs: internal only
  • Final integrated recommendations: Coach Luca only
  • Any outbound athlete message that does not pass through athlete-comms is a workflow failure in the current workspace implementation

Knowledge Layer Ownership

  • Each agent owns their own knowledgebase/ directory and PHILOSOPHY.md.
  • Coach Luca owns the cross-agent synthesis in team/coach-luca/PHILOSOPHY.md.
  • The weekly philosophy review protocol lives at team/coach-luca/synthesis/weekly-philosophy-review-protocol.md.

Change Propagation Rules

When a knowledgebase entry or philosophy revision materially changes practice:

  1. If it affects macro load structure → update athlete/planning/season-plan.md or athlete/rolling-3-week.md.
  2. If it affects day-to-day monitoring or thresholds → update team/coach-luca/synthesis/readiness-protocol.md.
  3. If it affects athlete briefing content or tone → update the relevant skill document.
  4. If it is informative but does not change current practice → record that explicitly in the philosophy review log.

A philosophy update is not complete until downstream impact has been assessed.