How to use: this is the one place to answer three questions. What does each of us want to work on? What have we found? What have we decided? Everything else in the repository links back here.
Question
Where to read it
How to add to it
What do I want to work on?
WORK_SIGNUP.md (workstreams, rules, assignment matrix), the project board, and DIGEST.md (current sign-ups and who holds which issue)
Issues need no pull request, so anyone can add a sign-up, finding, or decision request in two minutes, even with main protected. The Markdown logs are the curated record the rubric asks for ("the repository must contain a record of decisions, blockers, completed work, and changes to scope"). The Scrum Master moves items from issues into the logs at the Thursday check-in, in one small pull request that another member reviews.
Turn sign-ups into the assignment matrix in WORK_SIGNUP.md; members assign themselves to issues
Product Owner, Scrum Master
Monday, Wednesday, Friday
Stand-up rows in docs/meeting-notes/
everyone
Thursday check-in
Run python scripts/workspace_digest.py; review new findings (keep, re-check, or discard); decide open decision issues that are due; copy results into FINDINGS_LOG.md and DECISION_LOG.md
Scrum Master
Sprint review and retrospective
Findings that changed the research question, method, or scope are listed in retrospective.md with links here
Observation and interpretation stay separate. A finding states what was seen and how to reproduce it. Opinions go in the interpretation field.
Every number has a command. If a finding has no reproducible evidence, its confidence is "Hypothesis, needs checking".
Nothing is "decided" until the team agrees. A decision proposed by one person is logged as Proposed until it is confirmed at a ceremony or in a reviewed pull request, then Agreed with the date.
Nothing is deleted. Wrong findings are marked Refuted with the reason; reversed decisions are marked Superseded with a link to the new one.
Re-check before relying. Important findings are re-checked by a second member before they go into the report.
Names, not blame. Logs record who found or proposed something so contributions are visible, not to assign fault.