execution-plan/weeks/week-00-cockpit-and-positioning/commitment.md · UPDATED 2026-09-16
Week 00 commitment
3 parts436 words
6 checkboxes — tick them, they save to the file
State: UNCONFIRMED. Owner: Peter Ciancaglini. Specification
Start date: not set. End date: not set. Available hours: confirm (planned ceiling 10).
Primary outcome: cockpit and positioning.
Minimum that keeps the next gate alive: the cockpit repo with TODAY.md filled for Monday.
0101
Deliverables to commit
01
Deliverables to commit
-
profile-baseline.md: Five next actions and an evidence-backed skills baseline exist. -
environment-checklist.md: A future model has exact setup steps, success checks, and a CPU fallback. -
positioning.md: Every experience claim is supported or marked for Peter to confirm. - Bounded learning exercise and personal teach-back.
- Evidence-backed branding and opportunity pack.
- Sunday review and next physical action.
0202
Proposed calendar
02
Proposed calendar
| Day | Minutes | Physical action / outcome | Actual slot | Done |
|---|---|---|---|---|
| Mon | 90 | Create the five cockpit files and record a truthful baseline of Python, statistics, biology, portfolio links, and available time. | Not set | [ ] |
| Tue | 90 | A five-line account of the operating rules and the next physical action. | Not set | [ ] |
| Wed | 90 | Specify repository skeletons, environment smoke checks, offline fake mode, secrets handling, and local hardware inventory. Last ten minutes: optional note. | Not set | [ ] |
| Thu | 90 | A five-line account of the operating rules and the next physical action. Include relevant founder-paper work within this block. | Not set | [ ] |
| Fri | 90 | Draft LinkedIn headline/About, GitHub bio, ORCID setup checklist, and two target-role narratives: applied scientist and scientific AI lead. | Not set | [ ] |
| Sat | 90 | Resolve critical spillover; long-form draft if due; sandbox only if done. | Not set | [ ] |
| Sun | 60 | Build log, evidence, gap review, next actions. | Not set | [ ] |
0303
Dependency and capacity check
03
Dependency and capacity check
- Missing essential inputs: not yet inspected.
- Human/external dependency, owner and expected date: not yet inspected.
- Week-specific constraint: Do not install an entire infrastructure stack to start learning. Verify Peter's preferred public name and experience claims; dates stay relative until a start Monday is chosen.
- Existing session authorization for external actions or spending: not assessed; local planning only at scaffold creation.
- Scope to cut first: optional polish/additional examples; preserve scientific validity.
- If the forecast exceeds available time: record a concrete reduced scope or revised delivery proposal before committing.
Peter's commitment / adjustments: pending. Reviewing model and date: pending.