From fa5d36fa57b6234837a4a7a4928a201e6d1d318a Mon Sep 17 00:00:00 2001 From: Flow Research Date: Tue, 30 Jun 2026 06:15:16 +0200 Subject: [PATCH 1/7] docs: simplify fellow weekly reports --- .github/PULL_REQUEST_TEMPLATE.md | 6 ++-- CONTRIBUTING.md | 11 ++++--- README.md | 4 +-- docs/baseline-start-guide.md | 12 +++---- docs/branching-and-features.md | 4 +-- docs/commit-verification.md | 6 ++-- docs/documentation-guide.md | 14 +++++++- docs/project-structure-guide.md | 4 +-- docs/releases/v0.1-week-01-baseline.md | 2 +- docs/templates/weekly-report-template.md | 41 +++++++++--------------- reports/README.md | 21 ++++++++++++ scripts/verify-contribution.ps1 | 29 +++++++++++++---- 12 files changed, 99 insertions(+), 55 deletions(-) create mode 100644 reports/README.md diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index c437c54..e5df520 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -8,7 +8,7 @@ ## Human Learning - [ ] I can explain what changed without relying only on AI output. -- [ ] I added or updated a weekly report. +- [ ] I added my own `week-YY-fellow-.md` report. - [ ] I added a human learning log if this work involved learning. - [ ] I added a paper note if a paper or technical source shaped the work. @@ -21,7 +21,9 @@ ## Verification - [ ] I ran the relevant tests, script, benchmark, or manual check. -- [ ] I recorded evidence in the weekly report, benchmark results, screenshots, or notes. +- [ ] I linked my commits or pull request in my fellow report. +- [ ] I linked my public post in my fellow report. +- [ ] I recorded verification in benchmark results, screenshots, tests, command output, or notes. - [ ] I ran `scripts/verify-contribution.ps1`. ## AI Use diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 972166d..af9c5df 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -22,25 +22,28 @@ The tag `v0.1-week-01-baseline` marks the immutable Week 1 starter snapshot. | Experiment | `experiment/month-XX-topic` | `experiment/month-08-network-exchange` | | Documentation | `docs/topic` | `docs/fellowship-guide` | | Fix | `fix/topic` | `fix/readme-links` | -| Fellow Work | `fellows//week-XX` | `fellows/ada/week-01` | +| Fellow Work | `fellows//month-XX-week-YY-` | `fellows/ada/month-03-week-02-sync-test` | ## New Fellow Start ```bash git checkout baseline/week-01-starter -git checkout -b fellows//week-01 +git checkout -b fellows//month-01-week-01-setup ``` ## Required Learning Evidence Every weekly branch should include: -- A weekly report in `reports/month-XX/`. +- A short fellow report named `reports/month-XX/week-YY-fellow-.md`. - A human learning log in `research/learning-logs/` when the work involved learning. - A paper note in `research/paper-notes/` when a paper or technical source influenced the work. - A design outcome in `design/outcomes/` when a design, architecture, flow, or data model changed. - A feature brief in `features/active/` or `features/completed/` when a feature was planned or finished. -- Evidence of verification in the weekly report, benchmark output, screenshots, tests, or command output. +- Links to the fellow's commits or pull request and public post in the fellow report. +- Evidence of verification in benchmark output, screenshots, tests, command output, or the pull request. + +Copy `docs/templates/weekly-report-template.md` to create the report. Each fellow owns one file per week, so branches can merge without several people changing the same document. See `reports/README.md` for the naming rule. ## Human Work And AI Assistance diff --git a/README.md b/README.md index eb7f416..338956f 100644 --- a/README.md +++ b/README.md @@ -55,8 +55,8 @@ The verification script checks the baseline structure, but human review is still | `PROJECT_BRIEF.md` | Why the project exists and what is in scope | | `docs/roadmap.md` | The progressive 12-month roadmap | | `docs/` | Architecture notes, benchmarking notes, compute targets, and decisions | -| `reports/` | Weekly learning and build journal | -| `reports/month-01` to `reports/month-12` | Monthly report folders with four weekly reports each | +| `reports/` | Project week overviews and independently mergeable fellow updates | +| `reports/month-01` to `reports/month-12` | Monthly folders containing week overviews and each fellow's short update | | `research/` | Paper notes, reading lists, and learning evidence | | `research/learning-logs/` | Human learning reflections and AI-use notes | | `design/` | Design outcomes, sketches, flows, and decision artifacts | diff --git a/docs/baseline-start-guide.md b/docs/baseline-start-guide.md index e7b28d3..c77aef1 100644 --- a/docs/baseline-start-guide.md +++ b/docs/baseline-start-guide.md @@ -35,14 +35,14 @@ Start from the Week 1 baseline: ```bash git checkout baseline/week-01-starter -git checkout -b fellows//week-01 +git checkout -b fellows//month-01-week-01-setup ``` Example: ```bash git checkout baseline/week-01-starter -git checkout -b fellows/ada/week-01 +git checkout -b fellows/ada/month-01-week-01-setup ``` ## Alternative: Start From The Tag @@ -51,7 +51,7 @@ Use the tag when you want the exact immutable snapshot: ```bash git checkout v0.1-week-01-baseline -git checkout -b fellows//week-01 +git checkout -b fellows//month-01-week-01-setup ``` ## Ongoing Fellow Workflow @@ -59,9 +59,9 @@ git checkout -b fellows//week-01 After Week 1, a fellow can continue their own sequence: ```text -fellows//week-01 -fellows//week-02 -fellows//week-03 +fellows//month-01-week-01-setup +fellows//month-01-week-02-local-storage +fellows//month-01-week-03-local-ai-flow ``` Shared project work still uses the normal branch types: diff --git a/docs/branching-and-features.md b/docs/branching-and-features.md index 15a17b9..cf44c3d 100644 --- a/docs/branching-and-features.md +++ b/docs/branching-and-features.md @@ -19,7 +19,7 @@ New fellows who start from Week 1 should branch from `baseline/week-01-starter`, | `design/` | Architecture, flows, diagrams, and prototypes | `design/month-03-demo-storyboard` | | `experiment/` | Temporary technical trials | `experiment/month-08-network-exchange` | | `fix/` | Small corrections | `fix/readme-links` | -| `fellows/` | Individual fellow learning branches | `fellows/ada/week-01` | +| `fellows/` | Individual fellow learning branches | `fellows/ada/month-03-week-02-sync-test` | | `docs/` | Documentation-only work | `docs/month-01-report-cleanup` | ## Feature Folder Flow @@ -40,7 +40,7 @@ Use `features/` to keep feature thinking separate from final code. 4. Add design outcomes in `design/outcomes/`. 5. Implement the smallest useful code change in `src/`. 6. Add tests, benchmark evidence, screenshots, or command output. -7. Update the weekly report. +7. Add your own `week-YY-fellow-.md` report. 8. Merge back to `master` only when the branch is coherent and documented. ## Merge Checklist diff --git a/docs/commit-verification.md b/docs/commit-verification.md index 48477aa..006e898 100644 --- a/docs/commit-verification.md +++ b/docs/commit-verification.md @@ -33,7 +33,7 @@ The script checks that: - Core docs exist. - All 12 report months exist. -- Each report month has 4 weekly report files. +- Each report month has 4 project week overviews and may also contain one independently mergeable update per fellow per week. - Weekly reports include research, design, and evidence sections. - Contribution and pull request documents exist. @@ -53,7 +53,7 @@ The script is not enough by itself. A reviewer should also check: New work belongs on: -- `fellows//week-XX` +- `fellows//month-XX-week-YY-` - `feature/month-XX-week-YY-topic` - `research/month-XX-topic` - `design/month-XX-topic` @@ -65,7 +65,7 @@ New work belongs on: A good weekly commit usually touches several areas: ```text -reports/month-XX/week-YY.md +reports/month-XX/week-YY-fellow-.md research/paper-notes/... design/outcomes/... features/active or features/completed/... diff --git a/docs/documentation-guide.md b/docs/documentation-guide.md index 0f8a6b5..9907967 100644 --- a/docs/documentation-guide.md +++ b/docs/documentation-guide.md @@ -16,7 +16,7 @@ | `docs/commit-verification.md` | What must be verified before merge | | `docs/branching-and-features.md` | Branch and feature workflow | | `docs/research-and-design-architecture.md` | Research, design, build, and documentation loop | -| `reports/` | Weekly learning journal | +| `reports/` | Project week overviews and short, independently mergeable fellow updates | | `research/paper-notes/` | Notes from papers and technical sources | | `research/learning-logs/` | Human learning reflections | | `design/outcomes/` | Design decisions, sketches, and outcomes | @@ -43,6 +43,18 @@ The question is not only "Did the code change?" The better question is: > Can another fellow understand what was learned, what was decided, what was built, and what was verified? +## Fellow Weekly Update + +Each fellow creates their own file: + +```text +reports/month-XX/week-YY-fellow-.md +``` + +Copy `docs/templates/weekly-report-template.md` and keep the update short. It only needs the fellow's name, topic, what they did, commit or pull request links, a public-post link, and one blocker or next step. + +Do not combine several fellows in one editable file. The files with the same `month-XX` and `week-YY` form that week's report, while keeping each person's branch and commits easy to review. + ## Multi-Language Documentation Rule When work introduces Python, C, C++, or Rust code, the weekly report should say: diff --git a/docs/project-structure-guide.md b/docs/project-structure-guide.md index 5d59e83..2228c9e 100644 --- a/docs/project-structure-guide.md +++ b/docs/project-structure-guide.md @@ -81,7 +81,7 @@ The branch returns to `master` only after learning, design, build output, and ve The `reports/` folder contains `month-01` through `month-12`. -Each month has four weekly report files. This gives the fellowship a complete 48-week learning path. +Each month has four project week overview files. Fellows add their own `week-YY-fellow-.md` updates beside the overview, making individual contributions easy to review and merge. Weekly reports should include: @@ -202,7 +202,7 @@ This makes every merge teachable and reviewable. 5. Create a design outcome if a decision is needed. 6. Build the smallest useful output. 7. Verify it with a test, benchmark, screenshot, command output, or manual review. -8. Update the weekly report. +8. Add your own fellow weekly update. 9. Run the verification script. 10. Open a pull request. 11. Review with another person. diff --git a/docs/releases/v0.1-week-01-baseline.md b/docs/releases/v0.1-week-01-baseline.md index 42611c8..572a0bc 100644 --- a/docs/releases/v0.1-week-01-baseline.md +++ b/docs/releases/v0.1-week-01-baseline.md @@ -16,7 +16,7 @@ git clone https://github.com/Flow-Research/local-first-AI.git cd local-first-AI git checkout v0.1-week-01-baseline -git checkout -b fellows//week-01 +git checkout -b fellows//month-01-week-01-setup ``` ## Related Branch diff --git a/docs/templates/weekly-report-template.md b/docs/templates/weekly-report-template.md index 1c9d433..9c33b5b 100644 --- a/docs/templates/weekly-report-template.md +++ b/docs/templates/weekly-report-template.md @@ -1,35 +1,24 @@ -# Month X Week Y: Title +# Fellow Weekly Update -## 1. Goal for the Week +- **Fellow:** Your name +- **GitHub username:** `your-username` +- **Week:** Month XX, Week YY +- **Topic:** Short topic name -## 2. Research / Learning +## What I Did -Paper or source: +- Describe the main contribution. +- Add another result only if needed. -Key lesson: +## Commits -My explanation in my own words: +- [Short commit description](https://github.com/OWNER/REPOSITORY/commit/COMMIT_SHA) +- **Pull request:** [PR #](https://github.com/OWNER/REPOSITORY/pull/PR_NUMBER) -## 3. Design Outcome +## Public Post -Design artifact: +- [Post title](https://example.com/post) — Medium, X, LinkedIn, or another public platform -Decision: +## Blocker or Next Step -Human input: - -AI assistance: - -## 4. What I Built - -## 5. Files Added or Changed - -## 6. Evidence - -What I personally verified: - -Command, screenshot, benchmark, test, or review evidence: - -## 7. Problems / Blockers - -## 8. Next Step +One short sentence. Write `None` if there is no blocker or next step. diff --git a/reports/README.md b/reports/README.md new file mode 100644 index 0000000..ebe6837 --- /dev/null +++ b/reports/README.md @@ -0,0 +1,21 @@ +# Fellow Weekly Reports + +Each fellow adds one small report file for each week they contribute. Separate files make individual work and commits easy to review and prevent fellows from editing the same report file. + +## Add Your Update + +1. Copy `docs/templates/weekly-report-template.md`. +2. Save it as: + + ```text + reports/month-XX/week-YY-fellow-.md + ``` + + Example: `reports/month-03/week-02-fellow-ada.md` + +3. Fill in what you did, links to your commits or pull request, and a link to your public post. +4. Commit only your own weekly file with the work from your branch. + +Use lowercase letters, numbers, and hyphens in the GitHub username part of the filename. Do not edit another fellow's report. + +The existing weekly files without `-fellow-` in their names are project week overviews. Fellow updates sit beside them and together form the report for that week. diff --git a/scripts/verify-contribution.ps1 b/scripts/verify-contribution.ps1 index fafe5b8..8dfeca7 100644 --- a/scripts/verify-contribution.ps1 +++ b/scripts/verify-contribution.ps1 @@ -37,14 +37,21 @@ for ($month = 1; $month -le 12; $month++) { continue } - $reportCount = (Get-ChildItem -Path $monthPath -Filter "*.md" -File).Count - if ($reportCount -ne 4) { - $failures.Add("Expected 4 weekly reports in reports/$monthName but found $reportCount") + $projectReports = Get-ChildItem -Path $monthPath -Filter "*.md" -File | + Where-Object { $_.Name -notmatch "^week-\d{2}-fellow-" } + if ($projectReports.Count -ne 4) { + $failures.Add("Expected 4 project week overviews in reports/$monthName but found $($projectReports.Count)") } } -$weeklyReports = Get-ChildItem -Path (Join-Path $projectRoot "reports") -Recurse -Filter "*.md" -File -foreach ($report in $weeklyReports) { +$allReports = Get-ChildItem -Path (Join-Path $projectRoot "reports") -Recurse -Filter "*.md" -File | + Where-Object { $_.Name -ne "README.md" } +$projectWeeklyReports = $allReports | + Where-Object { $_.Name -notmatch "^week-\d{2}-fellow-" } +$fellowWeeklyReports = $allReports | + Where-Object { $_.Name -match "^week-\d{2}-fellow-" } + +foreach ($report in $projectWeeklyReports) { $text = Get-Content -Path $report.FullName -Raw foreach ($section in @("Research / Learning", "Design Outcome", "Evidence")) { if ($text -notmatch [regex]::Escape($section)) { @@ -54,6 +61,16 @@ foreach ($report in $weeklyReports) { } } +foreach ($report in $fellowWeeklyReports) { + $text = Get-Content -Path $report.FullName -Raw + foreach ($section in @("Fellow:", "What I Did", "Commits", "Public Post", "Blocker or Next Step")) { + if ($text -notmatch [regex]::Escape($section)) { + $relative = Resolve-Path -Path $report.FullName -Relative + $failures.Add("Missing field or section '$section' in $relative") + } + } +} + if ($failures.Count -gt 0) { Write-Host "Verification failed:" -ForegroundColor Red foreach ($failure in $failures) { @@ -62,4 +79,4 @@ if ($failures.Count -gt 0) { exit 1 } -Write-Host "Verification passed: baseline structure, reports, research/design sections, and contribution docs are present." -ForegroundColor Green +Write-Host "Verification passed: baseline structure, project reports, fellow updates, and contribution docs are present." -ForegroundColor Green From 59aa225e6c32d156470e92dee36f636ad970ec70 Mon Sep 17 00:00:00 2001 From: Flow Research Date: Tue, 30 Jun 2026 06:23:07 +0200 Subject: [PATCH 2/7] docs: use shared weekly fellow reports --- .github/PULL_REQUEST_TEMPLATE.md | 5 +-- CONTRIBUTING.md | 6 +-- README.md | 4 +- docs/branching-and-features.md | 2 +- docs/commit-verification.md | 4 +- docs/documentation-guide.md | 12 +++--- docs/project-structure-guide.md | 2 +- docs/templates/weekly-report-template.md | 29 +++++--------- reports/README.md | 30 ++++++++------- reports/month-01/week-02-local-storage.md | 46 +++++------------------ reports/month-01/week-03-local-ai-flow.md | 46 +++++------------------ reports/month-01/week-04-month-review.md | 46 +++++------------------ reports/month-02/week-01.md | 46 +++++------------------ reports/month-02/week-02.md | 46 +++++------------------ reports/month-02/week-03.md | 46 +++++------------------ reports/month-02/week-04.md | 46 +++++------------------ reports/month-03/week-01.md | 46 +++++------------------ reports/month-03/week-02.md | 46 +++++------------------ reports/month-03/week-03.md | 46 +++++------------------ reports/month-03/week-04.md | 46 +++++------------------ reports/month-04/week-01.md | 46 +++++------------------ reports/month-04/week-02.md | 46 +++++------------------ reports/month-04/week-03.md | 46 +++++------------------ reports/month-04/week-04.md | 46 +++++------------------ reports/month-05/week-01.md | 46 +++++------------------ reports/month-05/week-02.md | 46 +++++------------------ reports/month-05/week-03.md | 46 +++++------------------ reports/month-05/week-04.md | 46 +++++------------------ reports/month-06/week-01.md | 46 +++++------------------ reports/month-06/week-02.md | 46 +++++------------------ reports/month-06/week-03.md | 46 +++++------------------ reports/month-06/week-04.md | 46 +++++------------------ reports/month-07/week-01.md | 46 +++++------------------ reports/month-07/week-02.md | 46 +++++------------------ reports/month-07/week-03.md | 46 +++++------------------ reports/month-07/week-04.md | 46 +++++------------------ reports/month-08/week-01.md | 46 +++++------------------ reports/month-08/week-02.md | 46 +++++------------------ reports/month-08/week-03.md | 46 +++++------------------ reports/month-08/week-04.md | 46 +++++------------------ reports/month-09/week-01.md | 46 +++++------------------ reports/month-09/week-02.md | 46 +++++------------------ reports/month-09/week-03.md | 46 +++++------------------ reports/month-09/week-04.md | 46 +++++------------------ reports/month-10/week-01.md | 46 +++++------------------ reports/month-10/week-02.md | 46 +++++------------------ reports/month-10/week-03.md | 46 +++++------------------ reports/month-10/week-04.md | 46 +++++------------------ reports/month-11/week-01.md | 46 +++++------------------ reports/month-11/week-02.md | 46 +++++------------------ reports/month-11/week-03.md | 46 +++++------------------ reports/month-11/week-04.md | 46 +++++------------------ reports/month-12/week-01.md | 46 +++++------------------ reports/month-12/week-02.md | 46 +++++------------------ reports/month-12/week-03.md | 46 +++++------------------ reports/month-12/week-04.md | 46 +++++------------------ scripts/verify-contribution.ps1 | 39 ++++++++----------- 57 files changed, 529 insertions(+), 1766 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index e5df520..23c0813 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -8,7 +8,7 @@ ## Human Learning - [ ] I can explain what changed without relying only on AI output. -- [ ] I added my own `week-YY-fellow-.md` report. +- [ ] I filled in my named block in the existing weekly report. - [ ] I added a human learning log if this work involved learning. - [ ] I added a paper note if a paper or technical source shaped the work. @@ -21,8 +21,7 @@ ## Verification - [ ] I ran the relevant tests, script, benchmark, or manual check. -- [ ] I linked my commits or pull request in my fellow report. -- [ ] I linked my public post in my fellow report. +- [ ] I included my topic, completed work, and public-output link. - [ ] I recorded verification in benchmark results, screenshots, tests, command output, or notes. - [ ] I ran `scripts/verify-contribution.ps1`. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index af9c5df..e664e68 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -35,15 +35,15 @@ git checkout -b fellows//month-01-week-01-setup Every weekly branch should include: -- A short fellow report named `reports/month-XX/week-YY-fellow-.md`. +- A short named block in the existing `reports/month-XX/week-YY.md` report. - A human learning log in `research/learning-logs/` when the work involved learning. - A paper note in `research/paper-notes/` when a paper or technical source influenced the work. - A design outcome in `design/outcomes/` when a design, architecture, flow, or data model changed. - A feature brief in `features/active/` or `features/completed/` when a feature was planned or finished. -- Links to the fellow's commits or pull request and public post in the fellow report. +- A link to the fellow's public post in the weekly report. - Evidence of verification in benchmark output, screenshots, tests, command output, or the pull request. -Copy `docs/templates/weekly-report-template.md` to create the report. Each fellow owns one file per week, so branches can merge without several people changing the same document. See `reports/README.md` for the naming rule. +Each fellow edits only their numbered block, such as `Fellow 1: Ada`. The block contains the fellow's topic, what they did, and their public-output link. See `reports/README.md` for the format. ## Human Work And AI Assistance diff --git a/README.md b/README.md index 338956f..b9b6431 100644 --- a/README.md +++ b/README.md @@ -55,8 +55,8 @@ The verification script checks the baseline structure, but human review is still | `PROJECT_BRIEF.md` | Why the project exists and what is in scope | | `docs/roadmap.md` | The progressive 12-month roadmap | | `docs/` | Architecture notes, benchmarking notes, compute targets, and decisions | -| `reports/` | Project week overviews and independently mergeable fellow updates | -| `reports/month-01` to `reports/month-12` | Monthly folders containing week overviews and each fellow's short update | +| `reports/` | One shared report per week with a short named block for each fellow | +| `reports/month-01` to `reports/month-12` | Monthly folders containing four weekly reports | | `research/` | Paper notes, reading lists, and learning evidence | | `research/learning-logs/` | Human learning reflections and AI-use notes | | `design/` | Design outcomes, sketches, flows, and decision artifacts | diff --git a/docs/branching-and-features.md b/docs/branching-and-features.md index cf44c3d..0f58ef6 100644 --- a/docs/branching-and-features.md +++ b/docs/branching-and-features.md @@ -40,7 +40,7 @@ Use `features/` to keep feature thinking separate from final code. 4. Add design outcomes in `design/outcomes/`. 5. Implement the smallest useful code change in `src/`. 6. Add tests, benchmark evidence, screenshots, or command output. -7. Add your own `week-YY-fellow-.md` report. +7. Fill in your named fellow block in the existing weekly report. 8. Merge back to `master` only when the branch is coherent and documented. ## Merge Checklist diff --git a/docs/commit-verification.md b/docs/commit-verification.md index 006e898..c0e677b 100644 --- a/docs/commit-verification.md +++ b/docs/commit-verification.md @@ -33,7 +33,7 @@ The script checks that: - Core docs exist. - All 12 report months exist. -- Each report month has 4 project week overviews and may also contain one independently mergeable update per fellow per week. +- Each report month has 4 weekly reports. - Weekly reports include research, design, and evidence sections. - Contribution and pull request documents exist. @@ -65,7 +65,7 @@ New work belongs on: A good weekly commit usually touches several areas: ```text -reports/month-XX/week-YY-fellow-.md +reports/month-XX/week-YY.md research/paper-notes/... design/outcomes/... features/active or features/completed/... diff --git a/docs/documentation-guide.md b/docs/documentation-guide.md index 9907967..2fd2b76 100644 --- a/docs/documentation-guide.md +++ b/docs/documentation-guide.md @@ -16,7 +16,7 @@ | `docs/commit-verification.md` | What must be verified before merge | | `docs/branching-and-features.md` | Branch and feature workflow | | `docs/research-and-design-architecture.md` | Research, design, build, and documentation loop | -| `reports/` | Project week overviews and short, independently mergeable fellow updates | +| `reports/` | One shared report per week with a short block for each fellow | | `research/paper-notes/` | Notes from papers and technical sources | | `research/learning-logs/` | Human learning reflections | | `design/outcomes/` | Design decisions, sketches, and outcomes | @@ -45,19 +45,19 @@ The question is not only "Did the code change?" The better question is: ## Fellow Weekly Update -Each fellow creates their own file: +Each week uses one existing report: ```text -reports/month-XX/week-YY-fellow-.md +reports/month-XX/week-YY.md ``` -Copy `docs/templates/weekly-report-template.md` and keep the update short. It only needs the fellow's name, topic, what they did, commit or pull request links, a public-post link, and one blocker or next step. +Each contributor fills in a numbered block such as `Fellow 1: Full Name`. Keep it short: add only the topic, what the fellow did, and a link to their public output. -Do not combine several fellows in one editable file. The files with the same `month-XX` and `week-YY` form that week's report, while keeping each person's branch and commits easy to review. +Only edit your own fellow block. Git records the contribution through the commit on your branch. ## Multi-Language Documentation Rule -When work introduces Python, C, C++, or Rust code, the weekly report should say: +Keep the weekly report short even when work introduces Python, C, C++, or Rust. Put details such as the following in the relevant feature brief, design outcome, test, or learning log: - Why that language was chosen for the task. - How the code was run or checked. diff --git a/docs/project-structure-guide.md b/docs/project-structure-guide.md index 2228c9e..7aa9387 100644 --- a/docs/project-structure-guide.md +++ b/docs/project-structure-guide.md @@ -81,7 +81,7 @@ The branch returns to `master` only after learning, design, build output, and ve The `reports/` folder contains `month-01` through `month-12`. -Each month has four project week overview files. Fellows add their own `week-YY-fellow-.md` updates beside the overview, making individual contributions easy to review and merge. +Each month has four weekly report files. Every fellow adds a short named block to the relevant shared report. Weekly reports should include: diff --git a/docs/templates/weekly-report-template.md b/docs/templates/weekly-report-template.md index 9c33b5b..900fb84 100644 --- a/docs/templates/weekly-report-template.md +++ b/docs/templates/weekly-report-template.md @@ -1,24 +1,15 @@ -# Fellow Weekly Update +# Month XX Week YY: Weekly Report -- **Fellow:** Your name -- **GitHub username:** `your-username` -- **Week:** Month XX, Week YY -- **Topic:** Short topic name +Add one block for every fellow who contributed. Keep each block short. -## What I Did +## Fellow 1: Full Name -- Describe the main contribution. -- Add another result only if needed. +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -## Commits +## Fellow 2: Full Name -- [Short commit description](https://github.com/OWNER/REPOSITORY/commit/COMMIT_SHA) -- **Pull request:** [PR #](https://github.com/OWNER/REPOSITORY/pull/PR_NUMBER) - -## Public Post - -- [Post title](https://example.com/post) — Medium, X, LinkedIn, or another public platform - -## Blocker or Next Step - -One short sentence. Write `None` if there is no blocker or next step. +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/README.md b/reports/README.md index ebe6837..304e05a 100644 --- a/reports/README.md +++ b/reports/README.md @@ -1,21 +1,25 @@ -# Fellow Weekly Reports +# Weekly Reports -Each fellow adds one small report file for each week they contribute. Separate files make individual work and commits easy to review and prevent fellows from editing the same report file. +The repository has one shared report for each week: -## Add Your Update +```text +reports/month-XX/week-YY.md +``` + +Some Month 1 filenames also include the week's topic. Use the existing file for the correct month and week instead of creating another report. -1. Copy `docs/templates/weekly-report-template.md`. -2. Save it as: +## Add Your Update - ```text - reports/month-XX/week-YY-fellow-.md - ``` +Add or fill in one numbered fellow block: - Example: `reports/month-03/week-02-fellow-ada.md` +```markdown +## Fellow 1: Full Name -3. Fill in what you did, links to your commits or pull request, and a link to your public post. -4. Commit only your own weekly file with the work from your branch. +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform +``` -Use lowercase letters, numbers, and hyphens in the GitHub username part of the filename. Do not edit another fellow's report. +Use the next available number, such as `Fellow 2` or `Fellow 3`. Only edit your own block. Your branch commit will show who added the update. -The existing weekly files without `-fellow-` in their names are project week overviews. Fellow updates sit beside them and together form the report for that week. +The report intentionally asks for only the fellow's name, topic, completed work, and public-output link. diff --git a/reports/month-01/week-02-local-storage.md b/reports/month-01/week-02-local-storage.md index 07cc612..614298e 100644 --- a/reports/month-01/week-02-local-storage.md +++ b/reports/month-01/week-02-local-storage.md @@ -1,41 +1,15 @@ -# Month 1 Week 2: Local Storage Layer +# Month 1 Week 2: Local Storage Layer -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-01/week-03-local-ai-flow.md b/reports/month-01/week-03-local-ai-flow.md index baf306a..c217b67 100644 --- a/reports/month-01/week-03-local-ai-flow.md +++ b/reports/month-01/week-03-local-ai-flow.md @@ -1,41 +1,15 @@ -# Month 1 Week 3: Simple App Flow +# Month 1 Week 3: Simple App Flow -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-01/week-04-month-review.md b/reports/month-01/week-04-month-review.md index 9d9ca43..2403d81 100644 --- a/reports/month-01/week-04-month-review.md +++ b/reports/month-01/week-04-month-review.md @@ -1,41 +1,15 @@ -# Month 1 Week 4: Review and Benchmark Preparation +# Month 1 Week 4: Review and Benchmark Preparation -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-01.md b/reports/month-02/week-01.md index a09b536..5772680 100644 --- a/reports/month-02/week-01.md +++ b/reports/month-02/week-01.md @@ -1,41 +1,15 @@ -# Month 2 Week 1: Local Context Preparation +# Month 2 Week 1: Local Context Preparation -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-02.md b/reports/month-02/week-02.md index e0ed555..38f5f11 100644 --- a/reports/month-02/week-02.md +++ b/reports/month-02/week-02.md @@ -1,41 +1,15 @@ -# Month 2 Week 2: Simple AI Response Flow +# Month 2 Week 2: Simple AI Response Flow -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-03.md b/reports/month-02/week-03.md index 8278071..5b36ae9 100644 --- a/reports/month-02/week-03.md +++ b/reports/month-02/week-03.md @@ -1,41 +1,15 @@ -# Month 2 Week 3: Retrieval and Context Formatting +# Month 2 Week 3: Retrieval and Context Formatting -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-04.md b/reports/month-02/week-04.md index 7e38462..1f413d2 100644 --- a/reports/month-02/week-04.md +++ b/reports/month-02/week-04.md @@ -1,41 +1,15 @@ -# Month 2 Week 4: Local AI Review +# Month 2 Week 4: Local AI Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-01.md b/reports/month-03/week-01.md index 61e079d..9c331df 100644 --- a/reports/month-03/week-01.md +++ b/reports/month-03/week-01.md @@ -1,41 +1,15 @@ -# Month 3 Week 1: Demo Scenario +# Month 3 Week 1: Demo Scenario -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-02.md b/reports/month-03/week-02.md index 41e4748..261d601 100644 --- a/reports/month-03/week-02.md +++ b/reports/month-03/week-02.md @@ -1,41 +1,15 @@ -# Month 3 Week 2: Demo Path +# Month 3 Week 2: Demo Path -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-03.md b/reports/month-03/week-03.md index a129339..a4f146b 100644 --- a/reports/month-03/week-03.md +++ b/reports/month-03/week-03.md @@ -1,41 +1,15 @@ -# Month 3 Week 3: Evidence and Usage Notes +# Month 3 Week 3: Evidence and Usage Notes -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-04.md b/reports/month-03/week-04.md index 3c9eb7b..f9b12d4 100644 --- a/reports/month-03/week-04.md +++ b/reports/month-03/week-04.md @@ -1,41 +1,15 @@ -# Month 3 Week 4: Demo Review +# Month 3 Week 4: Demo Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-01.md b/reports/month-04/week-01.md index ebf83b1..34c4357 100644 --- a/reports/month-04/week-01.md +++ b/reports/month-04/week-01.md @@ -1,41 +1,15 @@ -# Month 4 Week 1: Benchmark Scope +# Month 4 Week 1: Benchmark Scope -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-02.md b/reports/month-04/week-02.md index 170266b..cf691df 100644 --- a/reports/month-04/week-02.md +++ b/reports/month-04/week-02.md @@ -1,41 +1,15 @@ -# Month 4 Week 2: Run Storage Benchmarks +# Month 4 Week 2: Run Storage Benchmarks -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-03.md b/reports/month-04/week-03.md index 9e052b1..500b4e6 100644 --- a/reports/month-04/week-03.md +++ b/reports/month-04/week-03.md @@ -1,41 +1,15 @@ -# Month 4 Week 3: Resource Observations +# Month 4 Week 3: Resource Observations -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-04.md b/reports/month-04/week-04.md index a91a8c5..00b9628 100644 --- a/reports/month-04/week-04.md +++ b/reports/month-04/week-04.md @@ -1,41 +1,15 @@ -# Month 4 Week 4: Constraint Review +# Month 4 Week 4: Constraint Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-01.md b/reports/month-05/week-01.md index a0ed160..e9b4c9f 100644 --- a/reports/month-05/week-01.md +++ b/reports/month-05/week-01.md @@ -1,41 +1,15 @@ -# Month 5 Week 1: Sync Principles +# Month 5 Week 1: Sync Principles -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-02.md b/reports/month-05/week-02.md index 52bf4e8..76e2c46 100644 --- a/reports/month-05/week-02.md +++ b/reports/month-05/week-02.md @@ -1,41 +1,15 @@ -# Month 5 Week 2: Conflict Thinking +# Month 5 Week 2: Conflict Thinking -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-03.md b/reports/month-05/week-03.md index d5a5a36..d0e0b26 100644 --- a/reports/month-05/week-03.md +++ b/reports/month-05/week-03.md @@ -1,41 +1,15 @@ -# Month 5 Week 3: Sync Prototype +# Month 5 Week 3: Sync Prototype -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-04.md b/reports/month-05/week-04.md index d746cfe..0e7acf3 100644 --- a/reports/month-05/week-04.md +++ b/reports/month-05/week-04.md @@ -1,41 +1,15 @@ -# Month 5 Week 4: Sync Review +# Month 5 Week 4: Sync Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-01.md b/reports/month-06/week-01.md index e9f797c..d3ae4de 100644 --- a/reports/month-06/week-01.md +++ b/reports/month-06/week-01.md @@ -1,41 +1,15 @@ -# Month 6 Week 1: Privacy Model +# Month 6 Week 1: Privacy Model -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-02.md b/reports/month-06/week-02.md index 5f56a1d..703b665 100644 --- a/reports/month-06/week-02.md +++ b/reports/month-06/week-02.md @@ -1,41 +1,15 @@ -# Month 6 Week 2: Local Secrets +# Month 6 Week 2: Local Secrets -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-03.md b/reports/month-06/week-03.md index f900884..30dde9b 100644 --- a/reports/month-06/week-03.md +++ b/reports/month-06/week-03.md @@ -1,41 +1,15 @@ -# Month 6 Week 3: Safer Defaults +# Month 6 Week 3: Safer Defaults -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-04.md b/reports/month-06/week-04.md index deaff88..abe194c 100644 --- a/reports/month-06/week-04.md +++ b/reports/month-06/week-04.md @@ -1,41 +1,15 @@ -# Month 6 Week 4: Privacy Review +# Month 6 Week 4: Privacy Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-01.md b/reports/month-07/week-01.md index 11ff22a..4022f94 100644 --- a/reports/month-07/week-01.md +++ b/reports/month-07/week-01.md @@ -1,41 +1,15 @@ -# Month 7 Week 1: Device Choice +# Month 7 Week 1: Device Choice -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-02.md b/reports/month-07/week-02.md index 3c32a78..a021e93 100644 --- a/reports/month-07/week-02.md +++ b/reports/month-07/week-02.md @@ -1,41 +1,15 @@ -# Month 7 Week 2: Environment Setup +# Month 7 Week 2: Environment Setup -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-03.md b/reports/month-07/week-03.md index ac7b583..8997894 100644 --- a/reports/month-07/week-03.md +++ b/reports/month-07/week-03.md @@ -1,41 +1,15 @@ -# Month 7 Week 3: Compatibility Check +# Month 7 Week 3: Compatibility Check -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-04.md b/reports/month-07/week-04.md index e042582..74bfc8e 100644 --- a/reports/month-07/week-04.md +++ b/reports/month-07/week-04.md @@ -1,41 +1,15 @@ -# Month 7 Week 4: Device Review +# Month 7 Week 4: Device Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-01.md b/reports/month-08/week-01.md index 71b7cc2..4b9f7b4 100644 --- a/reports/month-08/week-01.md +++ b/reports/month-08/week-01.md @@ -1,41 +1,15 @@ -# Month 8 Week 1: Local Network Idea +# Month 8 Week 1: Local Network Idea -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-02.md b/reports/month-08/week-02.md index f91b674..ee47e49 100644 --- a/reports/month-08/week-02.md +++ b/reports/month-08/week-02.md @@ -1,41 +1,15 @@ -# Month 8 Week 2: Data Exchange Sketch +# Month 8 Week 2: Data Exchange Sketch -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-03.md b/reports/month-08/week-03.md index d00a9dc..5f2a2d2 100644 --- a/reports/month-08/week-03.md +++ b/reports/month-08/week-03.md @@ -1,41 +1,15 @@ -# Month 8 Week 3: Network Experiment +# Month 8 Week 3: Network Experiment -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-04.md b/reports/month-08/week-04.md index f87ffd8..3751617 100644 --- a/reports/month-08/week-04.md +++ b/reports/month-08/week-04.md @@ -1,41 +1,15 @@ -# Month 8 Week 4: Network Review +# Month 8 Week 4: Network Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-01.md b/reports/month-09/week-01.md index b957be2..0683999 100644 --- a/reports/month-09/week-01.md +++ b/reports/month-09/week-01.md @@ -1,41 +1,15 @@ -# Month 9 Week 1: Agent Task Choice +# Month 9 Week 1: Agent Task Choice -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-02.md b/reports/month-09/week-02.md index 158f5c4..2a9232b 100644 --- a/reports/month-09/week-02.md +++ b/reports/month-09/week-02.md @@ -1,41 +1,15 @@ -# Month 9 Week 2: Agent Flow Design +# Month 9 Week 2: Agent Flow Design -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-03.md b/reports/month-09/week-03.md index f01ad92..64c8ced 100644 --- a/reports/month-09/week-03.md +++ b/reports/month-09/week-03.md @@ -1,41 +1,15 @@ -# Month 9 Week 3: Agent Prototype +# Month 9 Week 3: Agent Prototype -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-04.md b/reports/month-09/week-04.md index bf47a84..9074fa3 100644 --- a/reports/month-09/week-04.md +++ b/reports/month-09/week-04.md @@ -1,41 +1,15 @@ -# Month 9 Week 4: Agent Review +# Month 9 Week 4: Agent Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-01.md b/reports/month-10/week-01.md index e4eaba5..6777d2a 100644 --- a/reports/month-10/week-01.md +++ b/reports/month-10/week-01.md @@ -1,41 +1,15 @@ -# Month 10 Week 1: Evaluation Criteria +# Month 10 Week 1: Evaluation Criteria -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-02.md b/reports/month-10/week-02.md index 0c8aea5..b7a6fc9 100644 --- a/reports/month-10/week-02.md +++ b/reports/month-10/week-02.md @@ -1,41 +1,15 @@ -# Month 10 Week 2: Reliability Testing +# Month 10 Week 2: Reliability Testing -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-03.md b/reports/month-10/week-03.md index d588bb8..e6388cb 100644 --- a/reports/month-10/week-03.md +++ b/reports/month-10/week-03.md @@ -1,41 +1,15 @@ -# Month 10 Week 3: User Experience Review +# Month 10 Week 3: User Experience Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-04.md b/reports/month-10/week-04.md index 9422346..47cc3a0 100644 --- a/reports/month-10/week-04.md +++ b/reports/month-10/week-04.md @@ -1,41 +1,15 @@ -# Month 10 Week 4: Evaluation Report +# Month 10 Week 4: Evaluation Report -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-01.md b/reports/month-11/week-01.md index d43f43c..20537a6 100644 --- a/reports/month-11/week-01.md +++ b/reports/month-11/week-01.md @@ -1,41 +1,15 @@ -# Month 11 Week 1: Documentation Polish +# Month 11 Week 1: Documentation Polish -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-02.md b/reports/month-11/week-02.md index 3cc5aaf..7b56971 100644 --- a/reports/month-11/week-02.md +++ b/reports/month-11/week-02.md @@ -1,41 +1,15 @@ -# Month 11 Week 2: Demo Polish +# Month 11 Week 2: Demo Polish -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-03.md b/reports/month-11/week-03.md index 0d23d3e..0d22460 100644 --- a/reports/month-11/week-03.md +++ b/reports/month-11/week-03.md @@ -1,41 +1,15 @@ -# Month 11 Week 3: Evidence Polish +# Month 11 Week 3: Evidence Polish -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-04.md b/reports/month-11/week-04.md index f98cb76..e8ae3ab 100644 --- a/reports/month-11/week-04.md +++ b/reports/month-11/week-04.md @@ -1,41 +1,15 @@ -# Month 11 Week 4: Presentation Review +# Month 11 Week 4: Presentation Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-01.md b/reports/month-12/week-01.md index cf2d631..5bb8aa7 100644 --- a/reports/month-12/week-01.md +++ b/reports/month-12/week-01.md @@ -1,41 +1,15 @@ -# Month 12 Week 1: Year Review +# Month 12 Week 1: Year Review -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-02.md b/reports/month-12/week-02.md index 70b7fd7..40db8cc 100644 --- a/reports/month-12/week-02.md +++ b/reports/month-12/week-02.md @@ -1,41 +1,15 @@ -# Month 12 Week 2: Lessons Learned +# Month 12 Week 2: Lessons Learned -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-03.md b/reports/month-12/week-03.md index 50e77d7..18936c1 100644 --- a/reports/month-12/week-03.md +++ b/reports/month-12/week-03.md @@ -1,41 +1,15 @@ -# Month 12 Week 3: Next Roadmap +# Month 12 Week 3: Next Roadmap -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-04.md b/reports/month-12/week-04.md index 9aaccaa..e5a3b93 100644 --- a/reports/month-12/week-04.md +++ b/reports/month-12/week-04.md @@ -1,41 +1,15 @@ -# Month 12 Week 4: Final Report +# Month 12 Week 4: Final Report -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -Write the smallest useful goal for this week. +## Fellow 1: Full Name -## 2. Research / Learning +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform -Paper or source: +## Fellow 2: Full Name -Key lesson: - -How it affects the project: - -## 3. Design Outcome - -Design artifact: - -Decision: - -Reason: - -## 4. What I Built - -To be completed during the week. - -## 5. Files Added or Changed - -To be completed during the week. - -## 6. Evidence - -Add screenshots, command output, benchmark results, diagrams, or demo notes. - -## 7. Problems / Blockers - -To be completed during the week. - -## 8. Next Step - -To be completed at the end of the week. \ No newline at end of file +- **Topic:** Topic worked on +- **What I did:** One or two sentences describing the completed work +- **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/scripts/verify-contribution.ps1 b/scripts/verify-contribution.ps1 index 8dfeca7..45834f1 100644 --- a/scripts/verify-contribution.ps1 +++ b/scripts/verify-contribution.ps1 @@ -37,37 +37,28 @@ for ($month = 1; $month -le 12; $month++) { continue } - $projectReports = Get-ChildItem -Path $monthPath -Filter "*.md" -File | - Where-Object { $_.Name -notmatch "^week-\d{2}-fellow-" } - if ($projectReports.Count -ne 4) { - $failures.Add("Expected 4 project week overviews in reports/$monthName but found $($projectReports.Count)") + $reportCount = (Get-ChildItem -Path $monthPath -Filter "*.md" -File).Count + if ($reportCount -ne 4) { + $failures.Add("Expected 4 weekly reports in reports/$monthName but found $reportCount") } } -$allReports = Get-ChildItem -Path (Join-Path $projectRoot "reports") -Recurse -Filter "*.md" -File | +$weeklyReports = Get-ChildItem -Path (Join-Path $projectRoot "reports") -Recurse -Filter "*.md" -File | Where-Object { $_.Name -ne "README.md" } -$projectWeeklyReports = $allReports | - Where-Object { $_.Name -notmatch "^week-\d{2}-fellow-" } -$fellowWeeklyReports = $allReports | - Where-Object { $_.Name -match "^week-\d{2}-fellow-" } -foreach ($report in $projectWeeklyReports) { +foreach ($report in $weeklyReports) { $text = Get-Content -Path $report.FullName -Raw - foreach ($section in @("Research / Learning", "Design Outcome", "Evidence")) { - if ($text -notmatch [regex]::Escape($section)) { - $relative = Resolve-Path -Path $report.FullName -Relative - $failures.Add("Missing section '$section' in $relative") - } - } -} + $usesFellowFormat = $text -match "## Fellow \d+:" -and + $text -match "\*\*Topic:\*\*" -and + $text -match "\*\*What I did:\*\*" -and + $text -match "\*\*Public output:\*\*" + $usesLegacyFormat = $text -match "Research / Learning" -and + $text -match "Design Outcome" -and + $text -match "Evidence" -foreach ($report in $fellowWeeklyReports) { - $text = Get-Content -Path $report.FullName -Raw - foreach ($section in @("Fellow:", "What I Did", "Commits", "Public Post", "Blocker or Next Step")) { - if ($text -notmatch [regex]::Escape($section)) { + if (-not $usesFellowFormat -and -not $usesLegacyFormat) { $relative = Resolve-Path -Path $report.FullName -Relative - $failures.Add("Missing field or section '$section' in $relative") - } + $failures.Add("Weekly report must use the fellow format in $relative") } } @@ -79,4 +70,4 @@ if ($failures.Count -gt 0) { exit 1 } -Write-Host "Verification passed: baseline structure, project reports, fellow updates, and contribution docs are present." -ForegroundColor Green +Write-Host "Verification passed: baseline structure, weekly reports, and contribution docs are present." -ForegroundColor Green From 8618ecfd52d39c00f84e6e1b6648ca1ad35aaa88 Mon Sep 17 00:00:00 2001 From: Flow Research Date: Tue, 30 Jun 2026 06:33:31 +0200 Subject: [PATCH 3/7] ci: validate fellow branches before weekly merge --- .github/PULL_REQUEST_TEMPLATE.md | 3 +- .github/workflows/repository-safety-check.yml | 77 ++++++++++++++++--- CONTRIBUTING.md | 31 ++++++-- docs/architecture.md | 10 ++- docs/baseline-start-guide.md | 21 +++-- docs/branching-and-features.md | 17 +++- docs/commit-verification.md | 5 +- docs/releases/v0.1-week-01-baseline.md | 3 +- 8 files changed, 134 insertions(+), 33 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 23c0813..e7341dc 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -2,7 +2,8 @@ ## Branch -- [ ] This branch was created from the latest `master`. +- [ ] My branch follows `fellows//month-XX-week-YY-`. +- [ ] My branch was created from and targets the matching `weeks/month-XX-week-YY` branch. - [ ] This work is scoped to one feature, research task, design task, documentation task, experiment, or fix. ## Human Learning diff --git a/.github/workflows/repository-safety-check.yml b/.github/workflows/repository-safety-check.yml index 8d14cf7..dee0b47 100644 --- a/.github/workflows/repository-safety-check.yml +++ b/.github/workflows/repository-safety-check.yml @@ -1,31 +1,90 @@ -name: Repository safety checks +name: Fellow contribution checks on: - pull_request: - branches: - - master + # Check work while it is still on a fellow's branch. push: branches: - - master + - "fellows/**" + + # A fellow branch must merge into its matching weekly branch. + pull_request: + branches: + - "weeks/**" + types: [opened, synchronize, reopened, ready_for_review] permissions: contents: read +concurrency: + group: fellow-check-${{ github.workflow }}-${{ github.ref }} + cancel-in-progress: true + jobs: - repo-safety-check: - name: repo-safety-check + fellow-contribution-check: + # Ignore PRs into weeks/** when the source is not a fellow branch. + if: github.event_name == 'push' || startsWith(github.head_ref, 'fellows/') + name: fellow-contribution-check runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v4 with: + fetch-depth: 0 persist-credentials: false - - name: Check README exists - run: test -f README.md + - name: Validate fellow branch name + shell: bash + env: + BRANCH_NAME: ${{ github.event_name == 'pull_request' && github.head_ref || github.ref_name }} + run: | + pattern='^fellows/[a-z0-9]+(-[a-z0-9]+)*/month-(0[1-9]|1[0-2])-week-0[1-4]-[a-z0-9]+(-[a-z0-9]+)*$' + if [[ ! "$BRANCH_NAME" =~ $pattern ]]; then + echo "Invalid fellow branch: $BRANCH_NAME" + echo "Use: fellows//month-XX-week-YY-" + exit 1 + fi + + - name: Validate weekly pull request target + if: github.event_name == 'pull_request' + shell: bash + env: + HEAD_BRANCH: ${{ github.head_ref }} + BASE_BRANCH: ${{ github.base_ref }} + run: | + fellow_week=$(echo "$HEAD_BRANCH" | sed -E 's#^fellows/[^/]+/(month-[0-9]{2}-week-[0-9]{2})-.*$#\1#') + expected_base="weeks/$fellow_week" + + if [[ "$BASE_BRANCH" != "$expected_base" ]]; then + echo "This fellow branch must target: $expected_base" + echo "Current pull request target: $BASE_BRANCH" + exit 1 + fi + + - name: Require the matching weekly report + if: github.event_name == 'pull_request' + shell: bash + env: + HEAD_BRANCH: ${{ github.head_ref }} + BASE_SHA: ${{ github.event.pull_request.base.sha }} + HEAD_SHA: ${{ github.event.pull_request.head.sha }} + run: | + month=$(echo "$HEAD_BRANCH" | sed -E 's#^fellows/[^/]+/month-([0-9]{2})-week-[0-9]{2}-.*$#\1#') + week=$(echo "$HEAD_BRANCH" | sed -E 's#^fellows/[^/]+/month-[0-9]{2}-week-([0-9]{2})-.*$#\1#') + report_pattern="^reports/month-${month}/week-${week}.*\.md$" + + if ! git diff --name-only "$BASE_SHA" "$HEAD_SHA" | grep -Eq "$report_pattern"; then + echo "Update the shared report for Month $month, Week $week." + echo "Expected a changed file matching: reports/month-${month}/week-${week}*.md" + exit 1 + fi + + - name: Verify contribution structure + shell: pwsh + run: ./scripts/verify-contribution.ps1 - name: Check for unresolved merge conflict markers + shell: bash run: | if grep -R -n -E '^(<<<<<<<|=======|>>>>>>>)' . --exclude-dir=.git; then echo "Unresolved merge conflict marker found." diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e664e68..ee9c01d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,9 +6,15 @@ This project is a fellowship-style learning project. The goal is not for AI to d `master` is the evolving stable project branch. Do not work directly on `master`. -Every meaningful contribution should happen on a branch created from `master`. +Each week has an integration branch created from `master`. Fellows create their individual branches from that weekly branch: -New fellows who are starting at Week 1 should branch from `baseline/week-01-starter` instead of the current `master`. +```text +fellows//month-XX-week-YY- + -> weeks/month-XX-week-YY + -> master +``` + +For a new fellowship starting at Week 1, create `weeks/month-01-week-01` from `baseline/week-01-starter`. The tag `v0.1-week-01-baseline` marks the immutable Week 1 starter snapshot. @@ -23,14 +29,25 @@ The tag `v0.1-week-01-baseline` marks the immutable Week 1 starter snapshot. | Documentation | `docs/topic` | `docs/fellowship-guide` | | Fix | `fix/topic` | `fix/readme-links` | | Fellow Work | `fellows//month-XX-week-YY-` | `fellows/ada/month-03-week-02-sync-test` | +| Weekly Integration | `weeks/month-XX-week-YY` | `weeks/month-03-week-02` | + +## Create A Fellow Branch + +```bash +git fetch origin +git switch weeks/month-03-week-02 +git pull origin weeks/month-03-week-02 +git switch -c fellows//month-03-week-02- +``` -## New Fellow Start +Example: ```bash -git checkout baseline/week-01-starter -git checkout -b fellows//month-01-week-01-setup +git switch -c fellows/ada/month-03-week-02-sync-test ``` +Push the fellow branch and open its pull request against `weeks/month-03-week-02`, not `master`. The GitHub Action checks the fellow branch name, matching weekly target, weekly report update, repository structure, and unresolved conflict markers. + ## Required Learning Evidence Every weekly branch should include: @@ -76,10 +93,12 @@ Then fill the pull request checklist in `.github/PULL_REQUEST_TEMPLATE.md`. ## Merge Standard -A branch should only merge back to `master` when another person can understand: +A fellow branch should only merge into its matching `weeks/month-XX-week-YY` branch when another person can understand: - What was learned. - What was designed. - What was built. - What was verified. - What still needs work. + +After all accepted fellow contributions are combined and reviewed, open one pull request from the weekly branch into `master`. diff --git a/docs/architecture.md b/docs/architecture.md index 2758f08..097d62d 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -7,7 +7,9 @@ This repository is organized around a research-to-design-to-build loop. ```text master branch | -new branch +weeks/month-XX-week-YY + | +fellows//month-XX-week-YY-topic | Research input | @@ -19,10 +21,12 @@ Code / benchmark / docs change | Weekly report | -merge back to master +merge into weekly branch + | +weekly branch merges into master ``` -`master` should stay clean. It is the stable baseline used to start each feature, research, design, documentation, experiment, or fix branch. +`master` should stay clean. Weekly integration branches start from it, individual fellow branches start from the matching weekly branch, and only the reviewed weekly branch returns to `master`. ## Repository Architecture diff --git a/docs/baseline-start-guide.md b/docs/baseline-start-guide.md index c77aef1..718f3d3 100644 --- a/docs/baseline-start-guide.md +++ b/docs/baseline-start-guide.md @@ -7,6 +7,7 @@ This project keeps `master` as the evolving stable project, while `baseline/week | Name | Type | Purpose | |---|---|---| | `master` | Branch | Evolving stable project branch | +| `weeks/month-XX-week-YY` | Branch | Combines reviewed fellow contributions for one week | | `baseline/week-01-starter` | Branch | Permanent Week 1 starter baseline | | `v0.1-week-01-baseline` | Tag / release | Immutable snapshot of the Week 1 starter baseline | @@ -31,32 +32,33 @@ git clone https://github.com/Flow-Research/local-first-AI.git cd local-first-AI ``` -Start from the Week 1 baseline: +The coordinator creates the Week 1 integration branch from the baseline: ```bash git checkout baseline/week-01-starter -git checkout -b fellows//month-01-week-01-setup +git checkout -b weeks/month-01-week-01 +git push -u origin weeks/month-01-week-01 ``` -Example: +Each fellow then branches from the weekly integration branch: ```bash -git checkout baseline/week-01-starter -git checkout -b fellows/ada/month-01-week-01-setup +git checkout weeks/month-01-week-01 +git checkout -b fellows//month-01-week-01-setup ``` ## Alternative: Start From The Tag -Use the tag when you want the exact immutable snapshot: +Use the tag when the coordinator needs to create the weekly branch from the exact immutable snapshot: ```bash git checkout v0.1-week-01-baseline -git checkout -b fellows//month-01-week-01-setup +git checkout -b weeks/month-01-week-01 ``` ## Ongoing Fellow Workflow -After Week 1, a fellow can continue their own sequence: +For each later week, create a new fellow branch from the matching weekly branch: ```text fellows//month-01-week-01-setup @@ -79,6 +81,7 @@ fix/topic Do not commit new work directly to: - `master` +- `weeks/month-XX-week-YY` - `baseline/week-01-starter` `baseline/week-01-starter` should only change if the fellowship deliberately decides to publish a new starter baseline. @@ -88,7 +91,9 @@ Do not commit new work directly to: In GitHub branch protection settings: - Protect `master`. +- Protect `weeks/**`. - Protect `baseline/week-01-starter`. - Require pull requests before merging into `master`. +- Require pull requests and the `fellow-contribution-check` before merging fellow work into a weekly branch. - Prevent force pushes. - Prevent deletion of protected branches. diff --git a/docs/branching-and-features.md b/docs/branching-and-features.md index 0f58ef6..e0f8311 100644 --- a/docs/branching-and-features.md +++ b/docs/branching-and-features.md @@ -4,7 +4,13 @@ `master` is the evolving stable project branch. Do not do active work directly on `master`. -Every project task should branch from `master`, stay small, and return to `master` only when the work is documented, reviewed, and safe to build on. +Create one integration branch for the active week from `master`. Each fellow branches from that weekly branch, stays small, and merges back into the same weekly branch after review. + +```text +fellows//month-XX-week-YY- + -> weeks/month-XX-week-YY + -> master +``` The clean Week 1 starter baseline lives at `baseline/week-01-starter` and is also marked by the `v0.1-week-01-baseline` tag. @@ -20,6 +26,7 @@ New fellows who start from Week 1 should branch from `baseline/week-01-starter`, | `experiment/` | Temporary technical trials | `experiment/month-08-network-exchange` | | `fix/` | Small corrections | `fix/readme-links` | | `fellows/` | Individual fellow learning branches | `fellows/ada/month-03-week-02-sync-test` | +| `weeks/` | Reviewed weekly integration branches | `weeks/month-03-week-02` | | `docs/` | Documentation-only work | `docs/month-01-report-cleanup` | ## Feature Folder Flow @@ -34,20 +41,22 @@ Use `features/` to keep feature thinking separate from final code. ## Recommended Feature Lifecycle -1. Branch from `master`. +1. Branch from the matching `weeks/month-XX-week-YY` branch. 2. Create a feature brief in `features/active/`. 3. Add research notes in `research/paper-notes/` if the work depends on a paper or technical source. 4. Add design outcomes in `design/outcomes/`. 5. Implement the smallest useful code change in `src/`. 6. Add tests, benchmark evidence, screenshots, or command output. 7. Fill in your named fellow block in the existing weekly report. -8. Merge back to `master` only when the branch is coherent and documented. +8. Open a pull request into the matching weekly branch. +9. Merge the weekly branch into `master` after all fellow contributions are reviewed together. ## Merge Checklist | Check | Required? | |---|---| -| Branch started from latest `master` | Yes | +| Fellow branch started from the matching weekly branch | Yes | +| Pull request targets the matching weekly branch | Yes | | Weekly report updated | Yes | | Human learning log added when learning happened | Yes | | Design outcome added when UI, flow, architecture, or data model changed | Yes | diff --git a/docs/commit-verification.md b/docs/commit-verification.md index c0e677b..5144464 100644 --- a/docs/commit-verification.md +++ b/docs/commit-verification.md @@ -34,9 +34,11 @@ The script checks that: - Core docs exist. - All 12 report months exist. - Each report month has 4 weekly reports. -- Weekly reports include research, design, and evidence sections. +- Weekly reports use the short fellow format or the preserved legacy format. - Contribution and pull request documents exist. +The GitHub Action runs only for pushes to `fellows/**` and pull requests into `weeks/**`. For a pull request, it also checks that the fellow branch targets the matching month and week and changes that week's shared report. + ## Human Review The script is not enough by itself. A reviewer should also check: @@ -54,6 +56,7 @@ The script is not enough by itself. A reviewer should also check: New work belongs on: - `fellows//month-XX-week-YY-` +- `weeks/month-XX-week-YY` for reviewed weekly integration - `feature/month-XX-week-YY-topic` - `research/month-XX-topic` - `design/month-XX-topic` diff --git a/docs/releases/v0.1-week-01-baseline.md b/docs/releases/v0.1-week-01-baseline.md index 572a0bc..972eea7 100644 --- a/docs/releases/v0.1-week-01-baseline.md +++ b/docs/releases/v0.1-week-01-baseline.md @@ -16,6 +16,7 @@ git clone https://github.com/Flow-Research/local-first-AI.git cd local-first-AI git checkout v0.1-week-01-baseline +git checkout -b weeks/month-01-week-01 git checkout -b fellows//month-01-week-01-setup ``` @@ -40,4 +41,4 @@ baseline/week-01-starter ## Rule -Do not use this release for ongoing shared work. Use it as a starter snapshot only. +Do not use this release for ongoing shared work. Use it to create the Week 1 integration branch, then create fellow branches from that weekly branch. From e14aaa7bc9accf88bd775882125ce545ffb07bbd Mon Sep 17 00:00:00 2001 From: Flow Research Date: Tue, 30 Jun 2026 06:39:30 +0200 Subject: [PATCH 4/7] docs: make weekly report the only required update --- .github/PULL_REQUEST_TEMPLATE.md | 11 ++------- CONTRIBUTING.md | 13 +++++------ docs/branching-and-features.md | 19 +++++++--------- docs/commit-verification.md | 6 +++-- docs/documentation-guide.md | 11 ++++----- docs/project-structure-guide.md | 27 ++++++++++------------- docs/templates/weekly-report-template.md | 14 ++++++++++-- reports/README.md | 9 ++++++-- reports/month-01/week-02-local-storage.md | 16 +++++++++++--- reports/month-01/week-03-local-ai-flow.md | 16 +++++++++++--- reports/month-01/week-04-month-review.md | 16 +++++++++++--- reports/month-02/week-01.md | 16 +++++++++++--- reports/month-02/week-02.md | 16 +++++++++++--- reports/month-02/week-03.md | 16 +++++++++++--- reports/month-02/week-04.md | 16 +++++++++++--- reports/month-03/week-01.md | 16 +++++++++++--- reports/month-03/week-02.md | 16 +++++++++++--- reports/month-03/week-03.md | 16 +++++++++++--- reports/month-03/week-04.md | 16 +++++++++++--- reports/month-04/week-01.md | 16 +++++++++++--- reports/month-04/week-02.md | 16 +++++++++++--- reports/month-04/week-03.md | 16 +++++++++++--- reports/month-04/week-04.md | 16 +++++++++++--- reports/month-05/week-01.md | 16 +++++++++++--- reports/month-05/week-02.md | 16 +++++++++++--- reports/month-05/week-03.md | 16 +++++++++++--- reports/month-05/week-04.md | 16 +++++++++++--- reports/month-06/week-01.md | 16 +++++++++++--- reports/month-06/week-02.md | 16 +++++++++++--- reports/month-06/week-03.md | 16 +++++++++++--- reports/month-06/week-04.md | 16 +++++++++++--- reports/month-07/week-01.md | 16 +++++++++++--- reports/month-07/week-02.md | 16 +++++++++++--- reports/month-07/week-03.md | 16 +++++++++++--- reports/month-07/week-04.md | 16 +++++++++++--- reports/month-08/week-01.md | 16 +++++++++++--- reports/month-08/week-02.md | 16 +++++++++++--- reports/month-08/week-03.md | 16 +++++++++++--- reports/month-08/week-04.md | 16 +++++++++++--- reports/month-09/week-01.md | 16 +++++++++++--- reports/month-09/week-02.md | 16 +++++++++++--- reports/month-09/week-03.md | 16 +++++++++++--- reports/month-09/week-04.md | 16 +++++++++++--- reports/month-10/week-01.md | 16 +++++++++++--- reports/month-10/week-02.md | 16 +++++++++++--- reports/month-10/week-03.md | 16 +++++++++++--- reports/month-10/week-04.md | 16 +++++++++++--- reports/month-11/week-01.md | 16 +++++++++++--- reports/month-11/week-02.md | 16 +++++++++++--- reports/month-11/week-03.md | 16 +++++++++++--- reports/month-11/week-04.md | 16 +++++++++++--- reports/month-12/week-01.md | 16 +++++++++++--- reports/month-12/week-02.md | 16 +++++++++++--- reports/month-12/week-03.md | 16 +++++++++++--- reports/month-12/week-04.md | 16 +++++++++++--- scripts/verify-contribution.ps1 | 7 +++++- 56 files changed, 671 insertions(+), 198 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index e7341dc..b13d7cf 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -10,19 +10,12 @@ - [ ] I can explain what changed without relying only on AI output. - [ ] I filled in my named block in the existing weekly report. -- [ ] I added a human learning log if this work involved learning. -- [ ] I added a paper note if a paper or technical source shaped the work. - -## Design And Research - -- [ ] I added a design outcome if the work changed architecture, flow, data model, interface, or evaluation approach. -- [ ] I linked the relevant paper, article, official documentation, or technical source. -- [ ] I explained the design decision and alternatives considered. +- [ ] I included exactly five sentences describing what I did. +- [ ] I included my topic and public-output link. ## Verification - [ ] I ran the relevant tests, script, benchmark, or manual check. -- [ ] I included my topic, completed work, and public-output link. - [ ] I recorded verification in benchmark results, screenshots, tests, command output, or notes. - [ ] I ran `scripts/verify-contribution.ps1`. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ee9c01d..ec144da 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -48,19 +48,16 @@ git switch -c fellows/ada/month-03-week-02-sync-test Push the fellow branch and open its pull request against `weeks/month-03-week-02`, not `master`. The GitHub Action checks the fellow branch name, matching weekly target, weekly report update, repository structure, and unresolved conflict markers. -## Required Learning Evidence +## Required Weekly Documentation -Every weekly branch should include: +The shared weekly report is the only documentation file every fellow must modify. Each fellow adds: - A short named block in the existing `reports/month-XX/week-YY.md` report. -- A human learning log in `research/learning-logs/` when the work involved learning. -- A paper note in `research/paper-notes/` when a paper or technical source influenced the work. -- A design outcome in `design/outcomes/` when a design, architecture, flow, or data model changed. -- A feature brief in `features/active/` or `features/completed/` when a feature was planned or finished. +- The topic they worked on. +- Exactly five sentences explaining what they did. - A link to the fellow's public post in the weekly report. -- Evidence of verification in benchmark output, screenshots, tests, command output, or the pull request. -Each fellow edits only their numbered block, such as `Fellow 1: Ada`. The block contains the fellow's topic, what they did, and their public-output link. See `reports/README.md` for the format. +Each fellow edits only their numbered block, such as `Fellow 1: Ada`. Separate learning logs, paper notes, design outcomes, and feature briefs are not required unless the assigned task specifically asks for them. Code, tests, or other project files may still change when needed to complete the work. See `reports/README.md` for the report format. ## Human Work And AI Assistance diff --git a/docs/branching-and-features.md b/docs/branching-and-features.md index e0f8311..bbfec07 100644 --- a/docs/branching-and-features.md +++ b/docs/branching-and-features.md @@ -42,14 +42,13 @@ Use `features/` to keep feature thinking separate from final code. ## Recommended Feature Lifecycle 1. Branch from the matching `weeks/month-XX-week-YY` branch. -2. Create a feature brief in `features/active/`. -3. Add research notes in `research/paper-notes/` if the work depends on a paper or technical source. -4. Add design outcomes in `design/outcomes/`. -5. Implement the smallest useful code change in `src/`. -6. Add tests, benchmark evidence, screenshots, or command output. -7. Fill in your named fellow block in the existing weekly report. -8. Open a pull request into the matching weekly branch. -9. Merge the weekly branch into `master` after all fellow contributions are reviewed together. +2. Implement the assigned work in the relevant project files. +3. Add or run the relevant verification. +4. Fill in your named block in the existing weekly report using exactly five sentences. +5. Open a pull request into the matching weekly branch. +6. Merge the weekly branch into `master` after all fellow contributions are reviewed together. + +The weekly report is the only required documentation file. Research notes, design outcomes, learning logs, and feature briefs are optional unless the assigned task specifically requires one. ## Merge Checklist @@ -58,9 +57,7 @@ Use `features/` to keep feature thinking separate from final code. | Fellow branch started from the matching weekly branch | Yes | | Pull request targets the matching weekly branch | Yes | | Weekly report updated | Yes | -| Human learning log added when learning happened | Yes | -| Design outcome added when UI, flow, architecture, or data model changed | Yes | -| Research note added when a paper influenced the work | Yes | +| Fellow block contains name, topic, five sentences, and public-output link | Yes | | Tests or manual verification recorded | Yes | | README changed only when the public project overview changed | Yes | diff --git a/docs/commit-verification.md b/docs/commit-verification.md index 5144464..554a618 100644 --- a/docs/commit-verification.md +++ b/docs/commit-verification.md @@ -6,13 +6,15 @@ The project uses verification to make sure commits show real learning, design, a Verification does not mean the project is perfect. It means each contribution leaves enough evidence for another person to understand and review it. -## Required Evidence By Work Type +## Supporting Evidence By Work Type + +The shared weekly report is the only documentation file fellows must update. The items below are examples of useful supporting evidence when they are relevant to the assigned task; they are not mandatory extra documentation. | Work Type | Required Evidence | |---|---| | Research | Paper note, source link, human summary, project implication | | Design | Design outcome, options considered, chosen direction, risk | -| Feature | Feature brief, code change, verification evidence, weekly report | +| Feature | Code change, verification evidence, weekly report | | Benchmark | Runner or method, result file, interpretation note | | Documentation | Updated doc, reason for change, reviewer-readable explanation | | Experiment | Hypothesis, method, result, decision on whether to continue | diff --git a/docs/documentation-guide.md b/docs/documentation-guide.md index 2fd2b76..4ff8e8a 100644 --- a/docs/documentation-guide.md +++ b/docs/documentation-guide.md @@ -51,15 +51,12 @@ Each week uses one existing report: reports/month-XX/week-YY.md ``` -Each contributor fills in a numbered block such as `Fellow 1: Full Name`. Keep it short: add only the topic, what the fellow did, and a link to their public output. +Each contributor fills in a numbered block such as `Fellow 1: Full Name`. Add only the topic, exactly five sentences explaining what the fellow did, and a link to their public output. -Only edit your own fellow block. Git records the contribution through the commit on your branch. +The weekly report is the only required documentation change for fellows. Only edit your own fellow block. Git records the contribution through the commit on your branch. Other project files only need to change when the assigned work requires them. ## Multi-Language Documentation Rule -Keep the weekly report short even when work introduces Python, C, C++, or Rust. Put details such as the following in the relevant feature brief, design outcome, test, or learning log: +Keep the weekly report to the required five sentences even when work introduces Python, C, C++, or Rust. Additional documentation is optional unless the assigned task requires it. -- Why that language was chosen for the task. -- How the code was run or checked. -- What tradeoff the language introduced. -- Whether the code is prototype, experiment, or stable baseline. +The five sentences can summarize the language choice, how the work was checked, an important tradeoff, the result, and the next lesson. diff --git a/docs/project-structure-guide.md b/docs/project-structure-guide.md index 7aa9387..7abb66c 100644 --- a/docs/project-structure-guide.md +++ b/docs/project-structure-guide.md @@ -183,11 +183,8 @@ A reviewer should ask: The pull request template requires: -- Branch from `master`. +- Branch from the matching `weeks/month-XX-week-YY` branch. - Weekly report update. -- Human learning evidence. -- Research note if a paper shaped the work. -- Design outcome if the architecture, data model, flow, or interface changed. - Verification evidence. - AI-use review. @@ -195,18 +192,18 @@ This makes every merge teachable and reviewable. ## How A Fellow Should Work Each Week -1. Start from `master`. -2. Create a focused branch. +1. Start from the matching weekly branch. +2. Create a focused fellow branch. 3. Read the weekly paper or technical source. -4. Write a paper note or learning log. -5. Create a design outcome if a decision is needed. -6. Build the smallest useful output. -7. Verify it with a test, benchmark, screenshot, command output, or manual review. -8. Add your own fellow weekly update. -9. Run the verification script. -10. Open a pull request. -11. Review with another person. -12. Merge only when the work is understandable. +4. Build the smallest useful output. +5. Verify it with a test, benchmark, screenshot, command output, or manual review. +6. Add your name, topic, five sentences, and public-output link to the weekly report. +7. Run the verification script. +8. Open a pull request to the matching weekly branch. +9. Review with another person. +10. Merge only when the work is understandable. + +The weekly report is the only documentation file fellows must update. Extra research, design, feature, or learning documents are optional unless the task explicitly requires them. ## What Good Progress Looks Like diff --git a/docs/templates/weekly-report-template.md b/docs/templates/weekly-report-template.md index 900fb84..608fd61 100644 --- a/docs/templates/weekly-report-template.md +++ b/docs/templates/weekly-report-template.md @@ -5,11 +5,21 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/README.md b/reports/README.md index 304e05a..32e11a1 100644 --- a/reports/README.md +++ b/reports/README.md @@ -16,10 +16,15 @@ Add or fill in one numbered fellow block: ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ``` Use the next available number, such as `Fellow 2` or `Fellow 3`. Only edit your own block. Your branch commit will show who added the update. -The report intentionally asks for only the fellow's name, topic, completed work, and public-output link. +The weekly report is the only documentation file a fellow is required to modify. It asks only for the fellow's name, topic, exactly five sentences about completed work, and public-output link. Fellows may still change code, tests, research, or other project files when those changes are part of the actual task. diff --git a/reports/month-01/week-02-local-storage.md b/reports/month-01/week-02-local-storage.md index 614298e..a1f3921 100644 --- a/reports/month-01/week-02-local-storage.md +++ b/reports/month-01/week-02-local-storage.md @@ -1,15 +1,25 @@ -# Month 1 Week 2: Local Storage Layer +# Month 1 Week 2: Local Storage Layer Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-01/week-03-local-ai-flow.md b/reports/month-01/week-03-local-ai-flow.md index c217b67..c624067 100644 --- a/reports/month-01/week-03-local-ai-flow.md +++ b/reports/month-01/week-03-local-ai-flow.md @@ -1,15 +1,25 @@ -# Month 1 Week 3: Simple App Flow +# Month 1 Week 3: Simple App Flow Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-01/week-04-month-review.md b/reports/month-01/week-04-month-review.md index 2403d81..376f6d6 100644 --- a/reports/month-01/week-04-month-review.md +++ b/reports/month-01/week-04-month-review.md @@ -1,15 +1,25 @@ -# Month 1 Week 4: Review and Benchmark Preparation +# Month 1 Week 4: Review and Benchmark Preparation Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-01.md b/reports/month-02/week-01.md index 5772680..b829669 100644 --- a/reports/month-02/week-01.md +++ b/reports/month-02/week-01.md @@ -1,15 +1,25 @@ -# Month 2 Week 1: Local Context Preparation +# Month 2 Week 1: Local Context Preparation Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-02.md b/reports/month-02/week-02.md index 38f5f11..3119ac2 100644 --- a/reports/month-02/week-02.md +++ b/reports/month-02/week-02.md @@ -1,15 +1,25 @@ -# Month 2 Week 2: Simple AI Response Flow +# Month 2 Week 2: Simple AI Response Flow Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-03.md b/reports/month-02/week-03.md index 5b36ae9..68c476c 100644 --- a/reports/month-02/week-03.md +++ b/reports/month-02/week-03.md @@ -1,15 +1,25 @@ -# Month 2 Week 3: Retrieval and Context Formatting +# Month 2 Week 3: Retrieval and Context Formatting Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-04.md b/reports/month-02/week-04.md index 1f413d2..2907167 100644 --- a/reports/month-02/week-04.md +++ b/reports/month-02/week-04.md @@ -1,15 +1,25 @@ -# Month 2 Week 4: Local AI Review +# Month 2 Week 4: Local AI Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-01.md b/reports/month-03/week-01.md index 9c331df..3792cde 100644 --- a/reports/month-03/week-01.md +++ b/reports/month-03/week-01.md @@ -1,15 +1,25 @@ -# Month 3 Week 1: Demo Scenario +# Month 3 Week 1: Demo Scenario Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-02.md b/reports/month-03/week-02.md index 261d601..ca26539 100644 --- a/reports/month-03/week-02.md +++ b/reports/month-03/week-02.md @@ -1,15 +1,25 @@ -# Month 3 Week 2: Demo Path +# Month 3 Week 2: Demo Path Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-03.md b/reports/month-03/week-03.md index a4f146b..02e995a 100644 --- a/reports/month-03/week-03.md +++ b/reports/month-03/week-03.md @@ -1,15 +1,25 @@ -# Month 3 Week 3: Evidence and Usage Notes +# Month 3 Week 3: Evidence and Usage Notes Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-04.md b/reports/month-03/week-04.md index f9b12d4..dab33eb 100644 --- a/reports/month-03/week-04.md +++ b/reports/month-03/week-04.md @@ -1,15 +1,25 @@ -# Month 3 Week 4: Demo Review +# Month 3 Week 4: Demo Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-01.md b/reports/month-04/week-01.md index 34c4357..a9121d8 100644 --- a/reports/month-04/week-01.md +++ b/reports/month-04/week-01.md @@ -1,15 +1,25 @@ -# Month 4 Week 1: Benchmark Scope +# Month 4 Week 1: Benchmark Scope Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-02.md b/reports/month-04/week-02.md index cf691df..b89285a 100644 --- a/reports/month-04/week-02.md +++ b/reports/month-04/week-02.md @@ -1,15 +1,25 @@ -# Month 4 Week 2: Run Storage Benchmarks +# Month 4 Week 2: Run Storage Benchmarks Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-03.md b/reports/month-04/week-03.md index 500b4e6..2cf641a 100644 --- a/reports/month-04/week-03.md +++ b/reports/month-04/week-03.md @@ -1,15 +1,25 @@ -# Month 4 Week 3: Resource Observations +# Month 4 Week 3: Resource Observations Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-04.md b/reports/month-04/week-04.md index 00b9628..562a22e 100644 --- a/reports/month-04/week-04.md +++ b/reports/month-04/week-04.md @@ -1,15 +1,25 @@ -# Month 4 Week 4: Constraint Review +# Month 4 Week 4: Constraint Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-01.md b/reports/month-05/week-01.md index e9b4c9f..0b15ecb 100644 --- a/reports/month-05/week-01.md +++ b/reports/month-05/week-01.md @@ -1,15 +1,25 @@ -# Month 5 Week 1: Sync Principles +# Month 5 Week 1: Sync Principles Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-02.md b/reports/month-05/week-02.md index 76e2c46..eb0ad51 100644 --- a/reports/month-05/week-02.md +++ b/reports/month-05/week-02.md @@ -1,15 +1,25 @@ -# Month 5 Week 2: Conflict Thinking +# Month 5 Week 2: Conflict Thinking Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-03.md b/reports/month-05/week-03.md index d0e0b26..e110c30 100644 --- a/reports/month-05/week-03.md +++ b/reports/month-05/week-03.md @@ -1,15 +1,25 @@ -# Month 5 Week 3: Sync Prototype +# Month 5 Week 3: Sync Prototype Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-04.md b/reports/month-05/week-04.md index 0e7acf3..342b559 100644 --- a/reports/month-05/week-04.md +++ b/reports/month-05/week-04.md @@ -1,15 +1,25 @@ -# Month 5 Week 4: Sync Review +# Month 5 Week 4: Sync Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-01.md b/reports/month-06/week-01.md index d3ae4de..ad3abfe 100644 --- a/reports/month-06/week-01.md +++ b/reports/month-06/week-01.md @@ -1,15 +1,25 @@ -# Month 6 Week 1: Privacy Model +# Month 6 Week 1: Privacy Model Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-02.md b/reports/month-06/week-02.md index 703b665..c4242bd 100644 --- a/reports/month-06/week-02.md +++ b/reports/month-06/week-02.md @@ -1,15 +1,25 @@ -# Month 6 Week 2: Local Secrets +# Month 6 Week 2: Local Secrets Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-03.md b/reports/month-06/week-03.md index 30dde9b..5798b35 100644 --- a/reports/month-06/week-03.md +++ b/reports/month-06/week-03.md @@ -1,15 +1,25 @@ -# Month 6 Week 3: Safer Defaults +# Month 6 Week 3: Safer Defaults Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-04.md b/reports/month-06/week-04.md index abe194c..46a0ee4 100644 --- a/reports/month-06/week-04.md +++ b/reports/month-06/week-04.md @@ -1,15 +1,25 @@ -# Month 6 Week 4: Privacy Review +# Month 6 Week 4: Privacy Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-01.md b/reports/month-07/week-01.md index 4022f94..dcf81d5 100644 --- a/reports/month-07/week-01.md +++ b/reports/month-07/week-01.md @@ -1,15 +1,25 @@ -# Month 7 Week 1: Device Choice +# Month 7 Week 1: Device Choice Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-02.md b/reports/month-07/week-02.md index a021e93..e38ab1b 100644 --- a/reports/month-07/week-02.md +++ b/reports/month-07/week-02.md @@ -1,15 +1,25 @@ -# Month 7 Week 2: Environment Setup +# Month 7 Week 2: Environment Setup Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-03.md b/reports/month-07/week-03.md index 8997894..d6398d5 100644 --- a/reports/month-07/week-03.md +++ b/reports/month-07/week-03.md @@ -1,15 +1,25 @@ -# Month 7 Week 3: Compatibility Check +# Month 7 Week 3: Compatibility Check Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-04.md b/reports/month-07/week-04.md index 74bfc8e..eb17ce7 100644 --- a/reports/month-07/week-04.md +++ b/reports/month-07/week-04.md @@ -1,15 +1,25 @@ -# Month 7 Week 4: Device Review +# Month 7 Week 4: Device Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-01.md b/reports/month-08/week-01.md index 4b9f7b4..555f560 100644 --- a/reports/month-08/week-01.md +++ b/reports/month-08/week-01.md @@ -1,15 +1,25 @@ -# Month 8 Week 1: Local Network Idea +# Month 8 Week 1: Local Network Idea Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-02.md b/reports/month-08/week-02.md index ee47e49..52d7b71 100644 --- a/reports/month-08/week-02.md +++ b/reports/month-08/week-02.md @@ -1,15 +1,25 @@ -# Month 8 Week 2: Data Exchange Sketch +# Month 8 Week 2: Data Exchange Sketch Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-03.md b/reports/month-08/week-03.md index 5f2a2d2..37eea47 100644 --- a/reports/month-08/week-03.md +++ b/reports/month-08/week-03.md @@ -1,15 +1,25 @@ -# Month 8 Week 3: Network Experiment +# Month 8 Week 3: Network Experiment Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-04.md b/reports/month-08/week-04.md index 3751617..dfa0927 100644 --- a/reports/month-08/week-04.md +++ b/reports/month-08/week-04.md @@ -1,15 +1,25 @@ -# Month 8 Week 4: Network Review +# Month 8 Week 4: Network Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-01.md b/reports/month-09/week-01.md index 0683999..3a3989d 100644 --- a/reports/month-09/week-01.md +++ b/reports/month-09/week-01.md @@ -1,15 +1,25 @@ -# Month 9 Week 1: Agent Task Choice +# Month 9 Week 1: Agent Task Choice Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-02.md b/reports/month-09/week-02.md index 2a9232b..2d58e2d 100644 --- a/reports/month-09/week-02.md +++ b/reports/month-09/week-02.md @@ -1,15 +1,25 @@ -# Month 9 Week 2: Agent Flow Design +# Month 9 Week 2: Agent Flow Design Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-03.md b/reports/month-09/week-03.md index 64c8ced..d9973f6 100644 --- a/reports/month-09/week-03.md +++ b/reports/month-09/week-03.md @@ -1,15 +1,25 @@ -# Month 9 Week 3: Agent Prototype +# Month 9 Week 3: Agent Prototype Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-04.md b/reports/month-09/week-04.md index 9074fa3..f1f1f23 100644 --- a/reports/month-09/week-04.md +++ b/reports/month-09/week-04.md @@ -1,15 +1,25 @@ -# Month 9 Week 4: Agent Review +# Month 9 Week 4: Agent Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-01.md b/reports/month-10/week-01.md index 6777d2a..3bbe28d 100644 --- a/reports/month-10/week-01.md +++ b/reports/month-10/week-01.md @@ -1,15 +1,25 @@ -# Month 10 Week 1: Evaluation Criteria +# Month 10 Week 1: Evaluation Criteria Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-02.md b/reports/month-10/week-02.md index b7a6fc9..03ec3a4 100644 --- a/reports/month-10/week-02.md +++ b/reports/month-10/week-02.md @@ -1,15 +1,25 @@ -# Month 10 Week 2: Reliability Testing +# Month 10 Week 2: Reliability Testing Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-03.md b/reports/month-10/week-03.md index e6388cb..786221c 100644 --- a/reports/month-10/week-03.md +++ b/reports/month-10/week-03.md @@ -1,15 +1,25 @@ -# Month 10 Week 3: User Experience Review +# Month 10 Week 3: User Experience Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-04.md b/reports/month-10/week-04.md index 47cc3a0..d1cea84 100644 --- a/reports/month-10/week-04.md +++ b/reports/month-10/week-04.md @@ -1,15 +1,25 @@ -# Month 10 Week 4: Evaluation Report +# Month 10 Week 4: Evaluation Report Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-01.md b/reports/month-11/week-01.md index 20537a6..6a27105 100644 --- a/reports/month-11/week-01.md +++ b/reports/month-11/week-01.md @@ -1,15 +1,25 @@ -# Month 11 Week 1: Documentation Polish +# Month 11 Week 1: Documentation Polish Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-02.md b/reports/month-11/week-02.md index 7b56971..7caddd6 100644 --- a/reports/month-11/week-02.md +++ b/reports/month-11/week-02.md @@ -1,15 +1,25 @@ -# Month 11 Week 2: Demo Polish +# Month 11 Week 2: Demo Polish Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-03.md b/reports/month-11/week-03.md index 0d22460..6e69592 100644 --- a/reports/month-11/week-03.md +++ b/reports/month-11/week-03.md @@ -1,15 +1,25 @@ -# Month 11 Week 3: Evidence Polish +# Month 11 Week 3: Evidence Polish Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-04.md b/reports/month-11/week-04.md index e8ae3ab..b04dc21 100644 --- a/reports/month-11/week-04.md +++ b/reports/month-11/week-04.md @@ -1,15 +1,25 @@ -# Month 11 Week 4: Presentation Review +# Month 11 Week 4: Presentation Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-01.md b/reports/month-12/week-01.md index 5bb8aa7..d00a586 100644 --- a/reports/month-12/week-01.md +++ b/reports/month-12/week-01.md @@ -1,15 +1,25 @@ -# Month 12 Week 1: Year Review +# Month 12 Week 1: Year Review Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-02.md b/reports/month-12/week-02.md index 40db8cc..55aa6d8 100644 --- a/reports/month-12/week-02.md +++ b/reports/month-12/week-02.md @@ -1,15 +1,25 @@ -# Month 12 Week 2: Lessons Learned +# Month 12 Week 2: Lessons Learned Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-03.md b/reports/month-12/week-03.md index 18936c1..4def1a9 100644 --- a/reports/month-12/week-03.md +++ b/reports/month-12/week-03.md @@ -1,15 +1,25 @@ -# Month 12 Week 3: Next Roadmap +# Month 12 Week 3: Next Roadmap Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-04.md b/reports/month-12/week-04.md index e5a3b93..4a47544 100644 --- a/reports/month-12/week-04.md +++ b/reports/month-12/week-04.md @@ -1,15 +1,25 @@ -# Month 12 Week 4: Final Report +# Month 12 Week 4: Final Report Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did:** One or two sentences describing the completed work +- **What I did (five sentences):** + 1. First completed action or result. + 2. Second completed action or result. + 3. Third completed action or result. + 4. Fourth completed action or result. + 5. Fifth completed action, result, or lesson. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/scripts/verify-contribution.ps1 b/scripts/verify-contribution.ps1 index 45834f1..314667c 100644 --- a/scripts/verify-contribution.ps1 +++ b/scripts/verify-contribution.ps1 @@ -50,7 +50,12 @@ foreach ($report in $weeklyReports) { $text = Get-Content -Path $report.FullName -Raw $usesFellowFormat = $text -match "## Fellow \d+:" -and $text -match "\*\*Topic:\*\*" -and - $text -match "\*\*What I did:\*\*" -and + $text -match "\*\*What I did \(five sentences\):\*\*" -and + $text -match "(?m)^\s+1\.\s+" -and + $text -match "(?m)^\s+2\.\s+" -and + $text -match "(?m)^\s+3\.\s+" -and + $text -match "(?m)^\s+4\.\s+" -and + $text -match "(?m)^\s+5\.\s+" -and $text -match "\*\*Public output:\*\*" $usesLegacyFormat = $text -match "Research / Learning" -and $text -match "Design Outcome" -and From 8b06d3ecb4777e2d39147f3c15441ffcb3063198 Mon Sep 17 00:00:00 2001 From: Chibundu Ogbonnia <78664825+Dumken1@users.noreply.github.com> Date: Wed, 1 Jul 2026 05:59:30 +0200 Subject: [PATCH 5/7] Update .github/workflows/repository-safety-check.yml Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- .github/workflows/repository-safety-check.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/repository-safety-check.yml b/.github/workflows/repository-safety-check.yml index dee0b47..be1a466 100644 --- a/.github/workflows/repository-safety-check.yml +++ b/.github/workflows/repository-safety-check.yml @@ -73,7 +73,8 @@ jobs: week=$(echo "$HEAD_BRANCH" | sed -E 's#^fellows/[^/]+/month-[0-9]{2}-week-([0-9]{2})-.*$#\1#') report_pattern="^reports/month-${month}/week-${week}.*\.md$" - if ! git diff --name-only "$BASE_SHA" "$HEAD_SHA" | grep -Eq "$report_pattern"; then + merge_base=$(git merge-base "$BASE_SHA" "$HEAD_SHA") + if ! git diff --name-only "$merge_base" "$HEAD_SHA" | grep -Eq "$report_pattern"; then echo "Update the shared report for Month $month, Week $week." echo "Expected a changed file matching: reports/month-${month}/week-${week}*.md" exit 1 From 4a86175979ade65866727f040f0e58c93d5c391b Mon Sep 17 00:00:00 2001 From: Chibundu Ogbonnia <78664825+Dumken1@users.noreply.github.com> Date: Wed, 1 Jul 2026 05:59:49 +0200 Subject: [PATCH 6/7] Update .github/workflows/repository-safety-check.yml Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --- .github/workflows/repository-safety-check.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/repository-safety-check.yml b/.github/workflows/repository-safety-check.yml index be1a466..8a270b7 100644 --- a/.github/workflows/repository-safety-check.yml +++ b/.github/workflows/repository-safety-check.yml @@ -10,7 +10,7 @@ on: pull_request: branches: - "weeks/**" - types: [opened, synchronize, reopened, ready_for_review] + types: [opened, synchronize, reopened, ready_for_review, edited] permissions: contents: read From a2f91fd4203e430205fd84973a8ee783620c9b98 Mon Sep 17 00:00:00 2001 From: Flow Research Date: Wed, 1 Jul 2026 06:11:26 +0200 Subject: [PATCH 7/7] ci: require 20 words in fellow reports --- .github/PULL_REQUEST_TEMPLATE.md | 2 +- .github/workflows/repository-safety-check.yml | 2 +- CONTRIBUTING.md | 2 +- docs/branching-and-features.md | 4 +- docs/documentation-guide.md | 6 +-- docs/project-structure-guide.md | 2 +- docs/templates/weekly-report-template.md | 14 +---- reports/README.md | 9 +--- reports/month-01/week-02-local-storage.md | 14 +---- reports/month-01/week-03-local-ai-flow.md | 14 +---- reports/month-01/week-04-month-review.md | 14 +---- reports/month-02/week-01.md | 14 +---- reports/month-02/week-02.md | 14 +---- reports/month-02/week-03.md | 14 +---- reports/month-02/week-04.md | 14 +---- reports/month-03/week-01.md | 14 +---- reports/month-03/week-02.md | 14 +---- reports/month-03/week-03.md | 14 +---- reports/month-03/week-04.md | 14 +---- reports/month-04/week-01.md | 14 +---- reports/month-04/week-02.md | 14 +---- reports/month-04/week-03.md | 14 +---- reports/month-04/week-04.md | 14 +---- reports/month-05/week-01.md | 14 +---- reports/month-05/week-02.md | 14 +---- reports/month-05/week-03.md | 14 +---- reports/month-05/week-04.md | 14 +---- reports/month-06/week-01.md | 14 +---- reports/month-06/week-02.md | 14 +---- reports/month-06/week-03.md | 14 +---- reports/month-06/week-04.md | 14 +---- reports/month-07/week-01.md | 14 +---- reports/month-07/week-02.md | 14 +---- reports/month-07/week-03.md | 14 +---- reports/month-07/week-04.md | 14 +---- reports/month-08/week-01.md | 14 +---- reports/month-08/week-02.md | 14 +---- reports/month-08/week-03.md | 14 +---- reports/month-08/week-04.md | 14 +---- reports/month-09/week-01.md | 14 +---- reports/month-09/week-02.md | 14 +---- reports/month-09/week-03.md | 14 +---- reports/month-09/week-04.md | 14 +---- reports/month-10/week-01.md | 14 +---- reports/month-10/week-02.md | 14 +---- reports/month-10/week-03.md | 14 +---- reports/month-10/week-04.md | 14 +---- reports/month-11/week-01.md | 14 +---- reports/month-11/week-02.md | 14 +---- reports/month-11/week-03.md | 14 +---- reports/month-11/week-04.md | 14 +---- reports/month-12/week-01.md | 14 +---- reports/month-12/week-02.md | 14 +---- reports/month-12/week-03.md | 14 +---- reports/month-12/week-04.md | 14 +---- scripts/verify-contribution.ps1 | 54 +++++++++++++++---- 56 files changed, 151 insertions(+), 602 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index b13d7cf..83085d4 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -10,7 +10,7 @@ - [ ] I can explain what changed without relying only on AI output. - [ ] I filled in my named block in the existing weekly report. -- [ ] I included exactly five sentences describing what I did. +- [ ] I included at least 20 words describing what I did. - [ ] I included my topic and public-output link. ## Verification diff --git a/.github/workflows/repository-safety-check.yml b/.github/workflows/repository-safety-check.yml index 8a270b7..0766f48 100644 --- a/.github/workflows/repository-safety-check.yml +++ b/.github/workflows/repository-safety-check.yml @@ -80,7 +80,7 @@ jobs: exit 1 fi - - name: Verify contribution structure + - name: Verify report structure and 20-word minimum shell: pwsh run: ./scripts/verify-contribution.ps1 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index ec144da..2d35f36 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -54,7 +54,7 @@ The shared weekly report is the only documentation file every fellow must modify - A short named block in the existing `reports/month-XX/week-YY.md` report. - The topic they worked on. -- Exactly five sentences explaining what they did. +- At least 20 words explaining what they did. - A link to the fellow's public post in the weekly report. Each fellow edits only their numbered block, such as `Fellow 1: Ada`. Separate learning logs, paper notes, design outcomes, and feature briefs are not required unless the assigned task specifically asks for them. Code, tests, or other project files may still change when needed to complete the work. See `reports/README.md` for the report format. diff --git a/docs/branching-and-features.md b/docs/branching-and-features.md index bbfec07..cff6eab 100644 --- a/docs/branching-and-features.md +++ b/docs/branching-and-features.md @@ -44,7 +44,7 @@ Use `features/` to keep feature thinking separate from final code. 1. Branch from the matching `weeks/month-XX-week-YY` branch. 2. Implement the assigned work in the relevant project files. 3. Add or run the relevant verification. -4. Fill in your named block in the existing weekly report using exactly five sentences. +4. Fill in your named block in the existing weekly report using at least 20 words for what you did. 5. Open a pull request into the matching weekly branch. 6. Merge the weekly branch into `master` after all fellow contributions are reviewed together. @@ -57,7 +57,7 @@ The weekly report is the only required documentation file. Research notes, desig | Fellow branch started from the matching weekly branch | Yes | | Pull request targets the matching weekly branch | Yes | | Weekly report updated | Yes | -| Fellow block contains name, topic, five sentences, and public-output link | Yes | +| Fellow block contains name, topic, at least 20 words, and public-output link | Yes | | Tests or manual verification recorded | Yes | | README changed only when the public project overview changed | Yes | diff --git a/docs/documentation-guide.md b/docs/documentation-guide.md index 4ff8e8a..6ea8671 100644 --- a/docs/documentation-guide.md +++ b/docs/documentation-guide.md @@ -51,12 +51,12 @@ Each week uses one existing report: reports/month-XX/week-YY.md ``` -Each contributor fills in a numbered block such as `Fellow 1: Full Name`. Add only the topic, exactly five sentences explaining what the fellow did, and a link to their public output. +Each contributor fills in a numbered block such as `Fellow 1: Full Name`. Add only the topic, at least 20 words explaining what the fellow did, and a link to their public output. The weekly report is the only required documentation change for fellows. Only edit your own fellow block. Git records the contribution through the commit on your branch. Other project files only need to change when the assigned work requires them. ## Multi-Language Documentation Rule -Keep the weekly report to the required five sentences even when work introduces Python, C, C++, or Rust. Additional documentation is optional unless the assigned task requires it. +Keep the weekly report concise while meeting the 20-word minimum even when work introduces Python, C, C++, or Rust. Additional documentation is optional unless the assigned task requires it. -The five sentences can summarize the language choice, how the work was checked, an important tradeoff, the result, and the next lesson. +The description can summarize the language choice, how the work was checked, an important tradeoff, the result, and the next lesson. diff --git a/docs/project-structure-guide.md b/docs/project-structure-guide.md index 7abb66c..67adbf8 100644 --- a/docs/project-structure-guide.md +++ b/docs/project-structure-guide.md @@ -197,7 +197,7 @@ This makes every merge teachable and reviewable. 3. Read the weekly paper or technical source. 4. Build the smallest useful output. 5. Verify it with a test, benchmark, screenshot, command output, or manual review. -6. Add your name, topic, five sentences, and public-output link to the weekly report. +6. Add your name, topic, at least 20 words about what you did, and public-output link to the weekly report. 7. Run the verification script. 8. Open a pull request to the matching weekly branch. 9. Review with another person. diff --git a/docs/templates/weekly-report-template.md b/docs/templates/weekly-report-template.md index 608fd61..3ddfefe 100644 --- a/docs/templates/weekly-report-template.md +++ b/docs/templates/weekly-report-template.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/README.md b/reports/README.md index 32e11a1..8aabac7 100644 --- a/reports/README.md +++ b/reports/README.md @@ -16,15 +16,10 @@ Add or fill in one numbered fellow block: ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ``` Use the next available number, such as `Fellow 2` or `Fellow 3`. Only edit your own block. Your branch commit will show who added the update. -The weekly report is the only documentation file a fellow is required to modify. It asks only for the fellow's name, topic, exactly five sentences about completed work, and public-output link. Fellows may still change code, tests, research, or other project files when those changes are part of the actual task. +The weekly report is the only documentation file a fellow is required to modify. It asks only for the fellow's name, topic, at least 20 words about completed work, and public-output link. Fellows may still change code, tests, research, or other project files when those changes are part of the actual task. diff --git a/reports/month-01/week-02-local-storage.md b/reports/month-01/week-02-local-storage.md index a1f3921..f3bfdf1 100644 --- a/reports/month-01/week-02-local-storage.md +++ b/reports/month-01/week-02-local-storage.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-01/week-03-local-ai-flow.md b/reports/month-01/week-03-local-ai-flow.md index c624067..e22ef7d 100644 --- a/reports/month-01/week-03-local-ai-flow.md +++ b/reports/month-01/week-03-local-ai-flow.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-01/week-04-month-review.md b/reports/month-01/week-04-month-review.md index 376f6d6..7d14662 100644 --- a/reports/month-01/week-04-month-review.md +++ b/reports/month-01/week-04-month-review.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-01.md b/reports/month-02/week-01.md index b829669..def3535 100644 --- a/reports/month-02/week-01.md +++ b/reports/month-02/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-02.md b/reports/month-02/week-02.md index 3119ac2..188daf7 100644 --- a/reports/month-02/week-02.md +++ b/reports/month-02/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-03.md b/reports/month-02/week-03.md index 68c476c..4567243 100644 --- a/reports/month-02/week-03.md +++ b/reports/month-02/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-02/week-04.md b/reports/month-02/week-04.md index 2907167..219fc4f 100644 --- a/reports/month-02/week-04.md +++ b/reports/month-02/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-01.md b/reports/month-03/week-01.md index 3792cde..2b1b577 100644 --- a/reports/month-03/week-01.md +++ b/reports/month-03/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-02.md b/reports/month-03/week-02.md index ca26539..3c5e3b6 100644 --- a/reports/month-03/week-02.md +++ b/reports/month-03/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-03.md b/reports/month-03/week-03.md index 02e995a..19cd6d9 100644 --- a/reports/month-03/week-03.md +++ b/reports/month-03/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-03/week-04.md b/reports/month-03/week-04.md index dab33eb..6263106 100644 --- a/reports/month-03/week-04.md +++ b/reports/month-03/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-01.md b/reports/month-04/week-01.md index a9121d8..aacc346 100644 --- a/reports/month-04/week-01.md +++ b/reports/month-04/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-02.md b/reports/month-04/week-02.md index b89285a..f8d898a 100644 --- a/reports/month-04/week-02.md +++ b/reports/month-04/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-03.md b/reports/month-04/week-03.md index 2cf641a..2d34880 100644 --- a/reports/month-04/week-03.md +++ b/reports/month-04/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-04/week-04.md b/reports/month-04/week-04.md index 562a22e..7cf67c1 100644 --- a/reports/month-04/week-04.md +++ b/reports/month-04/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-01.md b/reports/month-05/week-01.md index 0b15ecb..f83480b 100644 --- a/reports/month-05/week-01.md +++ b/reports/month-05/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-02.md b/reports/month-05/week-02.md index eb0ad51..6305820 100644 --- a/reports/month-05/week-02.md +++ b/reports/month-05/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-03.md b/reports/month-05/week-03.md index e110c30..ee66ade 100644 --- a/reports/month-05/week-03.md +++ b/reports/month-05/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-05/week-04.md b/reports/month-05/week-04.md index 342b559..344c41a 100644 --- a/reports/month-05/week-04.md +++ b/reports/month-05/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-01.md b/reports/month-06/week-01.md index ad3abfe..10e3c96 100644 --- a/reports/month-06/week-01.md +++ b/reports/month-06/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-02.md b/reports/month-06/week-02.md index c4242bd..883c462 100644 --- a/reports/month-06/week-02.md +++ b/reports/month-06/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-03.md b/reports/month-06/week-03.md index 5798b35..5dbb816 100644 --- a/reports/month-06/week-03.md +++ b/reports/month-06/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-06/week-04.md b/reports/month-06/week-04.md index 46a0ee4..f4d7efa 100644 --- a/reports/month-06/week-04.md +++ b/reports/month-06/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-01.md b/reports/month-07/week-01.md index dcf81d5..269143d 100644 --- a/reports/month-07/week-01.md +++ b/reports/month-07/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-02.md b/reports/month-07/week-02.md index e38ab1b..34c32a4 100644 --- a/reports/month-07/week-02.md +++ b/reports/month-07/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-03.md b/reports/month-07/week-03.md index d6398d5..96c2c80 100644 --- a/reports/month-07/week-03.md +++ b/reports/month-07/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-07/week-04.md b/reports/month-07/week-04.md index eb17ce7..f192b63 100644 --- a/reports/month-07/week-04.md +++ b/reports/month-07/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-01.md b/reports/month-08/week-01.md index 555f560..fa4c92b 100644 --- a/reports/month-08/week-01.md +++ b/reports/month-08/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-02.md b/reports/month-08/week-02.md index 52d7b71..d0a255f 100644 --- a/reports/month-08/week-02.md +++ b/reports/month-08/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-03.md b/reports/month-08/week-03.md index 37eea47..47c0b8e 100644 --- a/reports/month-08/week-03.md +++ b/reports/month-08/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-08/week-04.md b/reports/month-08/week-04.md index dfa0927..cdcf461 100644 --- a/reports/month-08/week-04.md +++ b/reports/month-08/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-01.md b/reports/month-09/week-01.md index 3a3989d..d6806b3 100644 --- a/reports/month-09/week-01.md +++ b/reports/month-09/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-02.md b/reports/month-09/week-02.md index 2d58e2d..a355344 100644 --- a/reports/month-09/week-02.md +++ b/reports/month-09/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-03.md b/reports/month-09/week-03.md index d9973f6..e76c7b7 100644 --- a/reports/month-09/week-03.md +++ b/reports/month-09/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-09/week-04.md b/reports/month-09/week-04.md index f1f1f23..56b50fc 100644 --- a/reports/month-09/week-04.md +++ b/reports/month-09/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-01.md b/reports/month-10/week-01.md index 3bbe28d..0ccc600 100644 --- a/reports/month-10/week-01.md +++ b/reports/month-10/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-02.md b/reports/month-10/week-02.md index 03ec3a4..e585f48 100644 --- a/reports/month-10/week-02.md +++ b/reports/month-10/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-03.md b/reports/month-10/week-03.md index 786221c..74771c4 100644 --- a/reports/month-10/week-03.md +++ b/reports/month-10/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-10/week-04.md b/reports/month-10/week-04.md index d1cea84..4f00707 100644 --- a/reports/month-10/week-04.md +++ b/reports/month-10/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-01.md b/reports/month-11/week-01.md index 6a27105..09d5c56 100644 --- a/reports/month-11/week-01.md +++ b/reports/month-11/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-02.md b/reports/month-11/week-02.md index 7caddd6..d95894a 100644 --- a/reports/month-11/week-02.md +++ b/reports/month-11/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-03.md b/reports/month-11/week-03.md index 6e69592..c396a87 100644 --- a/reports/month-11/week-03.md +++ b/reports/month-11/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-11/week-04.md b/reports/month-11/week-04.md index b04dc21..040733d 100644 --- a/reports/month-11/week-04.md +++ b/reports/month-11/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-01.md b/reports/month-12/week-01.md index d00a586..7da5ae2 100644 --- a/reports/month-12/week-01.md +++ b/reports/month-12/week-01.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-02.md b/reports/month-12/week-02.md index 55aa6d8..263a0f5 100644 --- a/reports/month-12/week-02.md +++ b/reports/month-12/week-02.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-03.md b/reports/month-12/week-03.md index 4def1a9..1501259 100644 --- a/reports/month-12/week-03.md +++ b/reports/month-12/week-03.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/reports/month-12/week-04.md b/reports/month-12/week-04.md index 4a47544..1db5526 100644 --- a/reports/month-12/week-04.md +++ b/reports/month-12/week-04.md @@ -5,21 +5,11 @@ Add one block for every fellow who contributed. Keep each block short. ## Fellow 1: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform ## Fellow 2: Full Name - **Topic:** Topic worked on -- **What I did (five sentences):** - 1. First completed action or result. - 2. Second completed action or result. - 3. Third completed action or result. - 4. Fourth completed action or result. - 5. Fifth completed action, result, or lesson. +- **What I did:** Describe the work you completed, the result you achieved, how you verified it, one challenge you addressed, and the main lesson you learned this week. Use at least 20 words. - **Public output:** [Post title](https://example.com/post) - Medium, X, LinkedIn, or another public platform diff --git a/scripts/verify-contribution.ps1 b/scripts/verify-contribution.ps1 index 314667c..a1212a4 100644 --- a/scripts/verify-contribution.ps1 +++ b/scripts/verify-contribution.ps1 @@ -48,22 +48,56 @@ $weeklyReports = Get-ChildItem -Path (Join-Path $projectRoot "reports") -Recurse foreach ($report in $weeklyReports) { $text = Get-Content -Path $report.FullName -Raw - $usesFellowFormat = $text -match "## Fellow \d+:" -and - $text -match "\*\*Topic:\*\*" -and - $text -match "\*\*What I did \(five sentences\):\*\*" -and - $text -match "(?m)^\s+1\.\s+" -and - $text -match "(?m)^\s+2\.\s+" -and - $text -match "(?m)^\s+3\.\s+" -and - $text -match "(?m)^\s+4\.\s+" -and - $text -match "(?m)^\s+5\.\s+" -and - $text -match "\*\*Public output:\*\*" $usesLegacyFormat = $text -match "Research / Learning" -and $text -match "Design Outcome" -and $text -match "Evidence" + $fellowBlocks = [regex]::Matches( + $text, + "(?ms)^## Fellow \d+:[^\r\n]*\r?\n(?.*?)(?=^## Fellow \d+:|\z)" + ) + $usesFellowFormat = $fellowBlocks.Count -gt 0 if (-not $usesFellowFormat -and -not $usesLegacyFormat) { + $relative = Resolve-Path -Path $report.FullName -Relative + $failures.Add("Weekly report must use the fellow format in $relative") + continue + } + + if ($usesFellowFormat) { + $blockNumber = 0 + foreach ($fellowBlock in $fellowBlocks) { + $blockNumber++ + $block = $fellowBlock.Groups["block"].Value $relative = Resolve-Path -Path $report.FullName -Relative - $failures.Add("Weekly report must use the fellow format in $relative") + + if ($block -notmatch "(?m)^\s*-\s+\*\*Topic:\*\*\s+\S") { + $failures.Add("Missing topic in fellow block $blockNumber of $relative") + } + + if ($block -notmatch "(?m)^\s*-\s+\*\*Public output:\*\*\s+\S") { + $failures.Add("Missing public output in fellow block $blockNumber of $relative") + } + + $workMatch = [regex]::Match( + $block, + "(?ms)^\s*-\s+\*\*What I did:\*\*\s*(?.*?)(?=^\s*-\s+\*\*Public output:\*\*)" + ) + if (-not $workMatch.Success) { + $failures.Add("Missing 'What I did' in fellow block $blockNumber of $relative") + continue + } + + $work = $workMatch.Groups["work"].Value + $wordCount = [regex]::Matches( + $work, + "\b[\p{L}\p{N}][\p{L}\p{N}'’-]*\b" + ).Count + if ($wordCount -lt 20) { + $failures.Add( + "'What I did' needs at least 20 words in fellow block $blockNumber of $relative; found $wordCount" + ) + } + } } }