Repository navigation
Description
The order of work for PromiseTracker v3, version 1, and who owns each issue. Each person has 12 issues and works down their own list. The specification is docs/spec/promisetracker-v3-system-specification.md.
kelvinkipruto
The data model, publishing rules, verification, security and launch.
koechkevin
Tests and CI, failure handling, the document pipeline, the API's shared parts, search and the public pages.
Where one person waits for the other
Most of the time each person works down their own list. These are the only points where an issue cannot start until the other person has merged one of theirs.
kelvinkipruto waits for koechkevin
| kelvinkipruto's issue | Cannot start until koechkevin has merged |
|---|---|
| #643 | #667. A soft wait: it gives the role tests their own database, but #643 can start without it |
| #648 | #647 |
| #649 | #652 |
| #655 | #666 |
| #660 | #654, #656, #657, #658, #659 and #669 |
| #661 | #668 |
koechkevin waits for kelvinkipruto
| koechkevin's issue | Cannot start until kelvinkipruto has merged |
|---|---|
| #647 | #644 |
| #668 | #644 |
| #652 | #644 |
| #654 | #648 |
| #669 | #648 |
| #656 | #649 |
| #657, #658 and #659 | #651 |
These tables list only the waits between the two people. Each issue's own "Blocked by" section is the full list, including issues from the same person's list.
What can start today
- kelvinkipruto: V1-24: Kernel changes from the November review #665 is in review in feat(kernel): port fixes, takesOver, locales and a settings cache #671. V1-05: Users, roles and access rules #643 is next.
- koechkevin: V1-26: Test database, image smoke test and CI checks #667 and V1-25: Errors, logging, Sentry and the circuit breaker #666 have no blockers.
Every issue and what blocks it
The same information is on each issue, in its "Blocked by" section and in GitHub's own "Blocked by" links.
- V1-05: Users, roles and access rules #643: nothing
- V1-06: Languages, countries and the site shell #644: V1-05: Users, roles and access rules #643, V1-24: Kernel changes from the November review #665
- V1-07: Areas, offices and spreadsheet import #645: V1-06: Languages, countries and the site shell #644, V1-24: Kernel changes from the November review #665
- V1-08: Actors, terms, seat addresses and the officials list #646: V1-07: Areas, offices and spreadsheet import #645
- V1-09: Rating scales and claim types #647: V1-06: Languages, countries and the site shell #644
- V1-10: Claims, topics and the claim page #648: V1-08: Actors, terms, seat addresses and the officials list #646, V1-09: Rating scales and claim types #647
- V1-11: Publishing rules and the cascade #649: V1-10: Claims, topics and the claim page #648, V1-14: Documents, connectors and the processing pipeline #652
- V1-12: Built-in verification #650: V1-11: Publishing rules and the cascade #649, V1-24: Kernel changes from the November review #665
- V1-13: Claim updates, evidence, rating history and confirm rating #651: V1-12: Built-in verification #650
- V1-14: Documents, connectors and the processing pipeline #652: V1-06: Languages, countries and the site shell #644, V1-25: Errors, logging, Sentry and the circuit breaker #666
- V1-15: plugin-tika: reading PDF, Word and Excel #653: V1-14: Documents, connectors and the processing pipeline #652
- V1-16: plugin-ai: candidate claims and review #654: V1-10: Claims, topics and the claim page #648, V1-15: plugin-tika: reading PDF, Word and Excel #653, V1-24: Kernel changes from the November review #665
- V1-17: plugin-check: verification in Meedan Check #655: V1-12: Built-in verification #650, V1-24: Kernel changes from the November review #665, V1-25: Errors, logging, Sentry and the circuit breaker #666
- V1-18: Search, place first #656: V1-11: Publishing rules and the cascade #649
- V1-19: Homepage, themes, articles and editorial picks #657: V1-13: Claim updates, evidence, rating history and confirm rating #651
- V1-20: Citizen submissions, captcha and newsletter #658: V1-13: Claim updates, evidence, rating history and confirm rating #651
- V1-21: Share images, structured data and discoverability #659: V1-13: Claim updates, evidence, rating history and confirm rating #651
- V1-22: Security, privacy and retention #660: V1-16: plugin-ai: candidate claims and review #654, V1-17: plugin-check: verification in Meedan Check #655, V1-18: Search, place first #656, V1-19: Homepage, themes, articles and editorial picks #657, V1-20: Citizen submissions, captcha and newsletter #658, V1-21: Share images, structured data and discoverability #659, V1-28: API description, cache headers and transport tests #669
- V1-23: Launch readiness #661: V1-22: Security, privacy and retention #660, V1-27: Staging environment #668
- V1-24: Kernel changes from the November review #665: nothing
- V1-25: Errors, logging, Sentry and the circuit breaker #666: nothing
- V1-26: Test database, image smoke test and CI checks #667: nothing
- V1-27: Staging environment #668: V1-06: Languages, countries and the site shell #644
- V1-28: API description, cache headers and transport tests #669: V1-10: Claims, topics and the claim page #648
Status labels
| Label | Meaning |
|---|---|
status: ready |
Nothing open blocks it. It can start now |
status: in progress |
Being built, or in review |
status: blocked |
At least one issue in its "Blocked by" section is still open |
When a pull request merges, whoever merged it looks at the "Unblocks" section of the issue it closed and moves each listed issue to status: ready if nothing else open blocks it.
For an AI assistant picking up work
- Read
AGENTS.mdin the repository, including "Working on an issue". - Take the first issue in your person's list above that is labelled
status: ready. Do not start an issue owned by someone else, or one labelledstatus: blocked. - Read the issue's "Start here" section, then the specification sections it names.
- Build only what the acceptance criteria ask for. If the specification and the issue disagree, the specification wins, and the pull request says so.
Track labels
| Label | Meaning |
|---|---|
track: foundation |
Data model, access, publishing rules and the API |
track: pipeline |
Documents, extraction, AI and failure handling |
track: verification |
Verdicts, ratings and claim history |
track: public site |
Pages, search, forms and sharing |
track: operations |
Tests, CI, staging, security and launch |
needs decision |
A person must decide or approve before the issue can finish |
How we work
- One issue, one branch, one pull request. The pull request says
Closes #nand follows the format of feat(v3): foundation workspace on Payload 4, Postgres and Docker #663 and feat(kernel): ports, plugin manifests and start-up checks #664. - Every schema change has a committed migration. When both lists add migrations in the same week, the second to merge rebases and re-creates its migration, so the history stays in one line.
- A decision made while building goes in the pull request under "Decisions made while building", and in the spec's decision register if it changes behaviour.
- If an issue turns out to need something from the other list sooner, say so on the issue and update the tables above.
Activity