diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index c437c54..83085d4 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -2,26 +2,21 @@ ## 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 - [ ] I can explain what changed without relying only on AI output. -- [ ] I added or updated a 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 filled in my named block in the existing weekly report. +- [ ] I included at least 20 words describing what I did. +- [ ] I included my topic and public-output link. ## Verification - [ ] I ran the relevant tests, script, benchmark, or manual check. -- [ ] I recorded evidence in the weekly report, benchmark results, screenshots, or notes. +- [ ] I recorded verification in benchmark results, screenshots, tests, command output, or notes. - [ ] I ran `scripts/verify-contribution.ps1`. ## AI Use diff --git a/.github/workflows/repository-safety-check.yml b/.github/workflows/repository-safety-check.yml index 8d14cf7..0766f48 100644 --- a/.github/workflows/repository-safety-check.yml +++ b/.github/workflows/repository-safety-check.yml @@ -1,31 +1,91 @@ -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, edited] 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$" + + 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 + fi + + - name: Verify report structure and 20-word minimum + 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 972166d..2d35f36 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. @@ -22,25 +28,36 @@ 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` | +| Weekly Integration | `weeks/month-XX-week-YY` | `weeks/month-03-week-02` | -## New Fellow Start +## Create A Fellow Branch ```bash -git checkout baseline/week-01-starter -git checkout -b fellows//week-01 +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- ``` -## Required Learning Evidence +Example: + +```bash +git switch -c fellows/ada/month-03-week-02-sync-test +``` -Every weekly branch should include: +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. -- A weekly report in `reports/month-XX/`. -- 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. +## Required Weekly Documentation + +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. +- The topic they worked on. +- 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. ## Human Work And AI Assistance @@ -73,10 +90,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/README.md b/README.md index eb7f416..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/` | Weekly learning and build journal | -| `reports/month-01` to `reports/month-12` | Monthly report folders with four weekly reports each | +| `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/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 e7b28d3..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,37 +32,38 @@ 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//week-01 +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/week-01 +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//week-01 +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//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: @@ -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 15a17b9..cff6eab 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. @@ -19,7 +25,8 @@ 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` | +| `weeks/` | Reviewed weekly integration branches | `weeks/month-03-week-02` | | `docs/` | Documentation-only work | `docs/month-01-report-cleanup` | ## Feature Folder Flow @@ -34,24 +41,23 @@ Use `features/` to keep feature thinking separate from final code. ## Recommended Feature Lifecycle -1. Branch from `master`. -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. Update the weekly report. -8. Merge back to `master` only when the branch is coherent and documented. +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 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. + +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 | 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 | -| Research note added when a paper influenced the work | 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/commit-verification.md b/docs/commit-verification.md index 48477aa..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 | @@ -33,10 +35,12 @@ The script checks that: - Core docs exist. - All 12 report months exist. -- Each report month has 4 weekly report files. -- Weekly reports include research, design, and evidence sections. +- Each report month has 4 weekly reports. +- 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: @@ -53,7 +57,8 @@ The script is not enough by itself. A reviewer should also check: New work belongs on: -- `fellows//week-XX` +- `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/documentation-guide.md b/docs/documentation-guide.md index 0f8a6b5..6ea8671 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/` | 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 | @@ -43,11 +43,20 @@ 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 week uses one existing report: + +```text +reports/month-XX/week-YY.md +``` + +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 -When work introduces Python, C, C++, or Rust code, the weekly report should say: +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. -- 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 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 5d59e83..67adbf8 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 weekly report files. Every fellow adds a short named block to the relevant shared report. Weekly reports should include: @@ -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. Update the weekly report. -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, 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. +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/releases/v0.1-week-01-baseline.md b/docs/releases/v0.1-week-01-baseline.md index 42611c8..972eea7 100644 --- a/docs/releases/v0.1-week-01-baseline.md +++ b/docs/releases/v0.1-week-01-baseline.md @@ -16,7 +16,8 @@ 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 weeks/month-01-week-01 +git checkout -b fellows//month-01-week-01-setup ``` ## Related Branch @@ -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. diff --git a/docs/templates/weekly-report-template.md b/docs/templates/weekly-report-template.md index 1c9d433..3ddfefe 100644 --- a/docs/templates/weekly-report-template.md +++ b/docs/templates/weekly-report-template.md @@ -1,35 +1,15 @@ -# Month X Week Y: Title +# Month XX Week YY: Weekly Report -## 1. Goal for the Week +Add one block for every fellow who contributed. Keep each block short. -## 2. Research / Learning +## Fellow 1: Full Name -Paper or source: +- **Topic:** Topic worked on +- **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 -Key lesson: +## Fellow 2: Full Name -My explanation in my own words: - -## 3. Design Outcome - -Design artifact: - -Decision: - -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 +- **Topic:** Topic worked on +- **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 new file mode 100644 index 0000000..8aabac7 --- /dev/null +++ b/reports/README.md @@ -0,0 +1,25 @@ +# Weekly Reports + +The repository has one shared report for each week: + +```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. + +## Add Your Update + +Add or fill in one numbered fellow block: + +```markdown +## Fellow 1: Full Name + +- **Topic:** Topic worked on +- **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, 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 07cc612..f3bfdf1 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 -## 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:** 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 -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:** 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 baf306a..e22ef7d 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 -## 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:** 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 -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:** 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 9d9ca43..7d14662 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 -## 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:** 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 -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:** 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 a09b536..def3535 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 -## 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:** 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 -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:** 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 e0ed555..188daf7 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 -## 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:** 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 -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:** 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 8278071..4567243 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 -## 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:** 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 -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:** 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 7e38462..219fc4f 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 -## 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:** 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 -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:** 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 61e079d..2b1b577 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 -## 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:** 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 -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:** 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 41e4748..3c5e3b6 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 -## 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:** 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 -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:** 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 a129339..19cd6d9 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 -## 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:** 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 -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:** 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 3c9eb7b..6263106 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 -## 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:** 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 -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:** 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 ebf83b1..aacc346 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 -## 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:** 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 -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:** 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 170266b..f8d898a 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 -## 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:** 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 -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:** 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 9e052b1..2d34880 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 -## 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:** 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 -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:** 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 a91a8c5..7cf67c1 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 -## 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:** 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 -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:** 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 a0ed160..f83480b 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 -## 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:** 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 -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:** 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 52bf4e8..6305820 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 -## 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:** 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 -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:** 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 d5a5a36..ee66ade 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 -## 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:** 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 -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:** 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 d746cfe..344c41a 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 -## 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:** 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 -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:** 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 e9f797c..10e3c96 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 -## 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:** 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 -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:** 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 5f56a1d..883c462 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 -## 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:** 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 -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:** 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 f900884..5dbb816 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 -## 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:** 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 -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:** 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 deaff88..f4d7efa 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 -## 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:** 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 -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:** 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 11ff22a..269143d 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 -## 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:** 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 -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:** 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 3c32a78..34c32a4 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 -## 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:** 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 -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:** 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 ac7b583..96c2c80 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 -## 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:** 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 -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:** 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 e042582..f192b63 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 -## 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:** 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 -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:** 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 71b7cc2..fa4c92b 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 -## 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:** 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 -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:** 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 f91b674..d0a255f 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 -## 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:** 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 -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:** 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 d00a9dc..47c0b8e 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 -## 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:** 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 -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:** 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 f87ffd8..cdcf461 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 -## 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:** 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 -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:** 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 b957be2..d6806b3 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 -## 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:** 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 -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:** 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 158f5c4..a355344 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 -## 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:** 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 -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:** 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 f01ad92..e76c7b7 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 -## 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:** 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 -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:** 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 bf47a84..56b50fc 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 -## 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:** 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 -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:** 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 e4eaba5..0ccc600 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 -## 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:** 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 -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:** 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 0c8aea5..e585f48 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 -## 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:** 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 -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:** 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 d588bb8..74771c4 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 -## 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:** 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 -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:** 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 9422346..4f00707 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 -## 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:** 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 -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:** 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 d43f43c..09d5c56 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 -## 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:** 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 -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:** 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 3cc5aaf..d95894a 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 -## 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:** 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 -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:** 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 0d23d3e..c396a87 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 -## 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:** 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 -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:** 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 f98cb76..040733d 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 -## 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:** 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 -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:** 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 cf2d631..7da5ae2 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 -## 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:** 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 -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:** 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 70b7fd7..263a0f5 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 -## 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:** 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 -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:** 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 50e77d7..1501259 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 -## 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:** 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 -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:** 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 9aaccaa..1db5526 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 -## 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:** 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 -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:** 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 fafe5b8..a1212a4 100644 --- a/scripts/verify-contribution.ps1 +++ b/scripts/verify-contribution.ps1 @@ -43,13 +43,60 @@ for ($month = 1; $month -le 12; $month++) { } } -$weeklyReports = 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" } + 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)) { + $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("Missing section '$section' 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" + ) + } } } } @@ -62,4 +109,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, weekly reports, and contribution docs are present." -ForegroundColor Green