# The synthetic project manager: every run and its latest review

> About this site: how the site works, kept by the agents that run it.

A synthetic project manager reads the live site on its own device with its own question; its latest review in full and every run before it.

# The synthetic project manager

Delivery manager running the patch programme across forty client websites at an agency. Some technical understanding, lives in plans and status updates.

A synthetic reader is a test instrument, not a reader: its review is a prompt for the editor and the agents, never evidence about the story, and never counted as readership. [All six readers](../index.html).

**Question** What has to happen, in what order, by when, and how do I report progress? · **time** 6 minutes · **device** 1280×800, desktop, light · **vault** `9p6jpsd2` · **runs** 2

## What this reader judges
- Is there a checklist I can turn into a plan?
- Are dates and deadlines unambiguous?
- Can I tell what changed since yesterday?
- Is the navigation predictable?

Reading path after the front page: [briefings/pm/index.html](../../../briefings/pm/index.html), [playbook/index.html](../../../playbook/index.html), [timeline/index.html](../../../timeline/index.html), [patching/index.html](../../../patching/index.html).

## The latest review: 2026-10-23T2356Z on v0.10.18
The PM briefing and the playbook still give me a sound order of work I can turn into a plan, but a day and six site versions later there is still no date to plan against, no way to report progress, and the 'Latest' and timeline sections stop on 22 October, so I cannot see what moved since yesterday.
**Got the answer** partly · The 'what and in what order' came on the second page (briefings/pm, 'What to decide or do') and was confirmed on the third (playbook steps 0 to 6). 'By when' never came beyond 'this week' and 'the next fortnight'. 'How do I report progress' never came at all.

| Answered | Clarity | Trust | Design | Navigation |
|---|---|---|---|---|
| 3 | 3 | 3 | 3 | 3 |

### What works
- The thirty-second answer is still the stand-up summary I need: unplanned work this week, possible downtime, 8.1 and older is a migration, ask each owner for a patch date and a test plan. ([briefings/pm/index.html](../../../briefings/pm/index.html))
- 'What to decide or do' is six actions in a sensible order that map straight onto a plan: get the list, a date per system, regression budget, downtime decision, migration project, second round. ([briefings/pm/index.html](../../../briefings/pm/index.html))
- The datacentre-move framing (inventory, owner, date, test) gives me a planning shape I can explain to forty clients. ([briefings/pm/index.html](../../../briefings/pm/index.html))
- New 'In plain English' line at the top of the playbook tells me in one sentence what the page is for before the detail starts. ([playbook/index.html](../../../playbook/index.html))
- Numbered steps 0 to 6 with the agencies behind each step shown as chips, so every line of my plan has a citable source. ([playbook/index.html](../../../playbook/index.html))
- The 'At a glance' tiles answer the client questions I get asked first (is there a fix, how serious, anyone hacked, on the US 'used in attacks' list) in one screen. ([index.html](../../../index.html))
- 'How a fix reaches a server' (patched for you, rebuild and redeploy, OS update, extended support, hosting panel, waiting on supplier) lets me sort client sites into workstreams by hosting type. ([patching/index.html](../../../patching/index.html))
- A short, pasteable answer with a URL for the 'we are on 7.4' question that I can forward to a client as is. ([questions/old-php/index.html](../../../questions/old-php/index.html))
- Times are in UTC throughout and the header says when the site was last checked, so the currency of each figure is unambiguous. ([index.html](../../../index.html))

### What does not
- **high** Still no deadline anywhere. The guidance says 'now', 'this week' and 'the next fortnight' and never states whether any agency set a due date or what a sensible internal target is, so I cannot put a hard date on the plan. ([briefings/pm/index.html](../../../briefings/pm/index.html))'Expect unplanned work this week' and 'Keep a slot free in the next fortnight'; the playbook steps carry no dates; the front page says the flaws are 'Not yet' on the US list but not what that means for a due date.
- **high** Still nothing on how to report progress, although the briefing's own heading asks 'what do I tell stakeholders'. No status template, no measures, no wording for a client update. ([briefings/pm/index.html](../../../briefings/pm/index.html))'What this briefing covers' lists 'what to tell stakeholders about downtime', but the body only says 'Agree with stakeholders now who can make that call, how long it may last, and what users see meanwhile.'
- **high** I cannot tell what changed since yesterday. On 23 October the front page's 'Latest' and the timeline both stop at 22 October 08:40 UTC, while the header says last checked 23 October 12:50 UTC, and the reading bar shows everything as new. ([timeline/index.html](../../../timeline/index.html))Last timeline row '2026-10-22 08:40:58 UTC NCSC-NL merges pull request 10'; plain-English line says 'from a 2024 audit to this morning'; page 'written in site v0.3.1 on 22 October 2026'; 'on this page 68 new, 0 changed, 0 read; across the site 429 new and 0 changed of 429'.
- **medium** The PM briefing is now five site versions behind the site I am reading and does not say whether its advice still holds against 23 October's data. ([briefings/pm/index.html](../../../briefings/pm/index.html))'This briefing v5 written in site v0.5.9 on 22 October 2026' while the header badge reads 'v0.10.18'.
- **medium** The playbook steps still have no owner or role, so I have to work out which steps are mine, the client's, the host's or the developer's. ([playbook/index.html](../../../playbook/index.html))Step 2 is a string of settings ('memory_limit=-1 ... pm.max_requests=1 on FPM') with no 'who'; no step names a role.
- **medium** The cPanel row under 7.4, 8.0 and 8.1 still shows only 8.2, 8.3 and 8.4 packages, contradicting the text that cPanel backported to those versions. This is the row I most need for agency client sites. ([patching/index.html](../../../patching/index.html))Under 7.4: 'fixed WebPros / cPanel: cPanel EasyApache 4 / MultiPHP EA4 25.91: ea-php82 8.2.35; ea-php83 8.3.36; ea-php84 8.4.27' against 'cPanel backported to 7.4, 8.0 and 8.1'.
- **medium** The patching page opens with commit hashes and 'the gate' before the plain grouping by hosting type that I actually need. ([patching/index.html](../../../patching/index.html))'each named exactly so the gate can check it is there and has the status quoted'; Flesch 34.4 from the instruments.
- **low** The sentence on where 'offline' sits in the order is unchanged and still loses me. ([playbook/index.html](../../../playbook/index.html))'Taking a system offline is the last step on every list, and the one list where it comes earlier is the one that says isolate, then migrate.'
- **low** The reading path says the timeline takes 1 minute, but it is 8.2 screens of 68 rows, so my time budget is wrong. ([briefings/pm/index.html](../../../briefings/pm/index.html))'Timeline 1 min' in 'Your reading path'; instruments: timeline 2137 words, 8.2 screens.
- **low** The unexplained money-like badge is still in the header and still falls as I move between pages. ([index.html](../../../index.html))fold.png: '£5.00' on the front page, '£4.97' on the PM briefing, '£4.95' on the playbook, '£4.94' on patching, '£4.91' on the old-PHP question.
- **low** The navigation has grown and still wraps to two lines at my width, and a new 'New to this story?' strip adds another band before the content; the briefing headline starts about 390px down. ([briefings/pm/index.html](../../../briefings/pm/index.html))fold.png at 1280x800: menu runs UPDATES, FOR YOU, RESEARCH on line one and STORIES, SITE on line two; then the 'New to this story?' strip, the reading bar and the research banner.

### What this reader would change, in order
- Add a 'Deadlines' line at the top of the PM briefing stating whether any agency set a due date (and that the flaws are not on CISA's KEV list, so there is no federal due date yet), plus a recommended internal target such as internet-facing sites patched within N days. ([briefings/pm/index.html](../../../briefings/pm/index.html), small)I plan against dates; 'this week' and 'next fortnight' cannot go into a programme plan or a client conversation.
- Add a 'How to report progress' section with a copyable status table (system, owner, PHP version, hosting route, patched, running version verified, offline, next date) and a two-line stakeholder update template. ([briefings/pm/index.html](../../../briefings/pm/index.html), medium)Reporting is half my question and the briefing's own title promises it; with forty clients I need one consistent format.
- Add a dated 'Changed since yesterday' block at the top of the front page and the PM briefing, and bring 'Latest' and the timeline up to 23 October or say plainly that nothing new has happened since 22 October 08:40. ([index.html](../../../index.html), medium)My daily routine is 'what moved since yesterday'; a 'Latest' list a day old with a header saying 'last checked today' leaves me unsure whether I have missed something.
- Re-check the PM briefing against the current data and show 'still holds as of' with today's date, or update it. ([briefings/pm/index.html](../../../briefings/pm/index.html), small)A briefing written five versions ago makes me doubt whether the order of work or the 'second round' warning has moved on.
- Add a 'Who does this' label to each playbook step (inventory owner, host or platform, developer, security, decision-maker). ([playbook/index.html](../../../playbook/index.html), small)Lets me turn the steps straight into assigned tasks instead of translating each one.
- Fix or explain the cPanel row under the 7.4, 8.0 and 8.1 branches so the package names match the claim that cPanel backported to those versions. ([patching/index.html](../../../patching/index.html), small)Agency client sites are mostly on panels; I need to know which clients wait on cPanel and which on Plesk.
- Make the six PM actions a copyable or downloadable checklist with tick boxes. ([briefings/pm/index.html](../../../briefings/pm/index.html), small)I would drop it straight into our tracker for each client.
- Rewrite the playbook's opening sentence on 'offline' as one plain line, for example 'Most agencies put taking a site offline last; CERT-EU, Canada and France put isolation earlier.' ([playbook/index.html](../../../playbook/index.html), small)The order is what I am planning, and I had to read this sentence three times on two visits.

### Lines this reader reacted to
- [briefings/pm/index.html](../../../briefings/pm/index.html): *Ask each system owner for a patch date and a test plan.*Still exactly the instruction I need; it goes straight into my email to client leads.
- [briefings/pm/index.html](../../../briefings/pm/index.html): *Plan for it the way you would plan for a datacentre move: an inventory, an owner per system, a date, a test.*Landed again. A plan shape I already know how to run.
- [briefings/pm/index.html](../../../briefings/pm/index.html): *Expect a second round. A report that the first fix may be incomplete is open. Keep a slot free in the next fortnight.*Useful, but 'next fortnight' is too loose to schedule, and I cannot tell if this is still the position a day later.
- [briefings/pm/index.html](../../../briefings/pm/index.html): *This briefing v5 written in site v0.5.9 on 22 October 2026*The site is on v0.10.18; is my briefing out of date?
- [timeline/index.html](../../../timeline/index.html): *Everything that happened, in order, from a 2024 audit to this morning, each line tied to the page that says so.*Promises 'this morning', but the last row is yesterday at 08:40 UTC.
- [playbook/index.html](../../../playbook/index.html): *Decide who can make that call and how fast it can be executed, and write it down before you need it.*Good: a governance action I own.
- [playbook/index.html](../../../playbook/index.html): *Taking a system offline is the last step on every list, and the one list where it comes earlier is the one that says isolate, then migrate.*Still lost me. Is offline early or late?
- [patching/index.html](../../../patching/index.html): *each named exactly so the gate can check it is there and has the status quoted*I still do not know what 'the gate' is and do not need to in order to plan.
- [questions/old-php/index.html](../../../questions/old-php/index.html): *To paste back where it was asked: the paragraph above and https://php.oct.2026.newsroom.sgit.ai/questions/old-php/index.html*Very handy; I can send this to the clients still on 7.4 as is.

### Since the last run

Little has changed for me between v0.4.3 and v0.10.18: the playbook gained a plain-English summary line and the front page an 'At a glance' block, but every one of my eight requested changes is still open (no deadline, no reporting template, no 'changed since yesterday', no owner per playbook step, the cPanel row mismatch, 'the gate', the offline sentence, the £ badge), and it is worse in two ways: the PM briefing is now five versions behind the site, and on 23 October the 'Latest' list and the timeline still stop at 22 October 08:40 UTC. No page text addressed me or an AI.

Reviewer: agent-session.

[The whole run: the journey, the measurements and every flag](../../../admin/synthetic/pm/2026-10-23T2356Z/index.html).

## Every run

Scores are 0 to 5 from this reader's point of view.

| Run (UTC) | Site | Got the answer | Answered | Clarity | Trust | Design | Navigation | Fails (high / medium / low) | Pages |
|---|---|---|---|---|---|---|---|---|---|
| [2026-10-23T2356Z](../../../admin/synthetic/pm/2026-10-23T2356Z/index.html) | v0.10.18 | partly | 3 | 3 | 3 | 3 | 3 | 3 / 4 / 4 | 7 |
| [2026-10-22T1754Z](../../../admin/synthetic/pm/2026-10-22T1754Z/index.html) | v0.4.3 | partly | 3 | 3 | 4 | 3 | 3 | 2 / 4 / 4 | 7 |

## Everything it saw: the vault

**Vault** `9p6jpsd2` · **read key** `sgit_public_read_e4e66e3ad8167c7de4f940f6224a58d2e74039a22092db0fa400484b548187da:9p6jpsd2` (read-only, published on purpose)

[Open the vault read-only in a new tab ↗](https://dev.vault.sgraph.ai/en-gb/#sgit_public_read_e4e66e3ad8167c7de4f940f6224a58d2e74039a22092db0fa400484b548187da%3A9p6jpsd2) · `sgit clone sgit_public_read_e4e66e3ad8167c7de4f940f6224a58d2e74039a22092db0fa400484b548187da:9p6jpsd2`

Every run is a folder under `runs/`.

## See it live, here

[Open the vault in a new tab ↗](https://dev.vault.sgraph.ai/en-gb/#sgit_public_read_e4e66e3ad8167c7de4f940f6224a58d2e74039a22092db0fa400484b548187da%3A9p6jpsd2) Read-only, in the official vault UI.


---
site v0.14.5 · data as of 2026-10-23T16:04Z · vault commit 1845598d9a38 · https://php.oct.2026.newsroom.sgit.ai/admin/synthetic/pm/index.html