Skip to content

v3 version 1: build order and owners #672

Open

Description

@kelvinkipruto

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

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.

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

  1. Read AGENTS.md in the repository, including "Working on an issue".
  2. 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 labelled status: blocked.
  3. Read the issue's "Start here" section, then the specification sections it names.
  4. 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 #n and 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

  1. added this to the v3: version 1 milestone on Nov 16, 2026
  2. added
    choreChange that improve code but doesn't add any feature
    v3PromiseTracker v3
    track: operationsTests, CI, staging, security and launch
    on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreChange that improve code but doesn't add any featuretrack: operationsTests, CI, staging, security and launchv3PromiseTracker v3

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions