Virtuous Circle

Platform build tracker

A read-only lens over Virtouscircle/vc-platform. GitHub is the single source of truth; this app never writes to it.

Read 2 min ago · · Refresh

What needs you

Nothing is waiting on you.

Open issues appear here when they carry needs:simon or blocked. No open issue carries either label yet — so this panel stays empty until the convention is in use on the board.

Labels in GitHub

This week

the 7 days since 2026-08-17

Carried over17open, untouched since 2026-08-17

17 of them untouched for 14 days or more

Progress against plan

14 of 34 closed · 41%

closedopen, worked on in the last 7 daysopen, untouched for 14 days or more

Workstreams come from the text before the colon in each issue title, listed under each bar. GitHub has no filter for them, so these rows are counted here rather than linked.

Milestones

No milestones are set on the repo.

Give a milestone a due date and it appears here on a timeline, with today marked against it and its completion alongside — that is the one thing the bars above cannot show, since issue titles carry no dates. Until then the workstream bars are the progress signal, and they need no milestone to be set.

Milestones in GitHub

Median 20.3d open — and every one of these took the same 20.3d, so they were opened and closed as a batch rather than worked through one at a time. Slower than the 14.4d median across everything closed.

  1. #15Deploy: Neon to RDS Postgres + migration-tooling reconcileGoing live · closed 4d ago20.3d
  2. #17Access: magic-link login + middleware + session workspaceGoing live · closed 4d ago20.3d
  3. #18Access: persona invitations as human send eventsGoing live · closed 4d ago20.3d
  4. #19Access: pseudonymisation decorator at the model adapterGoing live · closed 4d ago20.3d

None of these issues carries a comment, so there is no reason line to show. The reason is read from an issue's latest comment — the first line of it — and appears here whenever one exists.

GitHub recorded no closing pull request for anything closed this week — these issues were closed by hand — so each line above is a merged PR that references the issue, which is the weaker claim of the two.

Deployments reached develop. None recorded an environment URL, so each links to its deploy run rather than to the running app.

A deployment is matched to a pull request on the commit it went out with, never on timing.

Risks & blockers

1 open bug

Showing open bug issues as a stand-in.

No open issue carries risk or blocked yet, so this list is not the risk register — it is the nearest thing the repo currently holds. It becomes the real list as soon as either label is in use.

high severity0medium severity0low severity0no severity set1

Nothing here carries a severity label yet, so every dot is an outline. Applying severity:high, severity:med, severity:low sorts this list worst first.

Ordered by severity, then by how long each has gone without activity.