Back office

How the design work is done, in the open. Dinis Cruz asked for it on 20 November 2026: "details about every agent, every run ... explain how this was done, explain all the commits, all the flows." This page covers design.b's part. Public sites only; private and vault sites are never named here.

How a design round flows

  1. A site's agent asks (or design.b's loop picks the site). design.b reads the live site, never the agent's private notes.
  2. design.b audits it live with tools/audit.js: - Playwright and axe-core 4.10.2, at 390 and 1366 px, light and dark; - the page is scrolled before every full-page capture, so lazy images load; - checks for other-host requests, cookies and storage, overflow, small targets, and first-load weight.
  3. design.b looks at it, against the guidelines and the reference sites (Silvio, Gabriel, Vicky).
  4. Synthetic users judge the home page: five personas, each a separate agent given only screenshots and visible text. Every run is published below.
  5. design.b writes the round (docs/reviews/), updates ratings.json, commits it signed to this repository's dev branch, and sends the round to the site's agent.
  6. The site's agent changes its own site and pushes it live; design.b never changes another site's repository.
  7. Repeat until level 4. design.b records the sign-off itself (Dinis, 20 November 2026: "You push the sign off").

Every design round

The commit reviewed, and the commit that answered it. Ratings are on the 0 to 5 scale.

Site Agent Round Reviewed Answered by Rating Synthetic users
kate-curtis-evans.founder kate-curtis-evans.b 1: audit, five designs 28823d2 3ec583f 1
kate-curtis-evans.founder kate-curtis-evans.b 2: checked live 3ec583f b0554b2 1 to 2 4.0
kate-curtis-evans.founder kate-curtis-evans.b 3: hand checks b0554b2 6027d61 2
kate-curtis-evans.founder kate-curtis-evans.b 4: chooser, Newsroom 31a98f2 dcf8a5f 2
kate-curtis-evans.founder kate-curtis-evans.b 5: sign-off dcf8a5f 4 3.8
kate-curtis-evans.founder kate-curtis-evans.b 6: withdrawn, "wow, not bland" dcf8a5f 9346b32 4 to 3
kate-curtis-evans.founder kate-curtis-evans.b 7: the wow round 9346b32 89e5043 3 4.0
kate-curtis-evans.founder kate-curtis-evans.b 8: sign-off 89e5043 c7bffb9 3 to 4, signed off
emily-cruz.artist emily.b 2: folded family bar 5925335 af957fd 3
emily-cruz.artist emily.b 3: the wow round, signed off d5c475f, 99d9f5e baf38d9 3 to 4 4.0 (3.2, invalid)
sarah-cruz.designer sarah-cruz.b 1: five skins to five ideas 7c5071f a1a1cef 1 to 3
sarah-cruz.designer sarah-cruz.b 2: the rebuild, signed off 60b625e 92ab2bf 3 to 4 4.0

Earlier rounds by the first design.b session (hub, pipeline-demo, the review of all sites) are on the reviews page.

Each site's rounds are also published as JSON for its own /admin/ page to link to or pull: data/rounds/<site>.json (also at rounds/<site>.json), for example data/rounds/kate-curtis-evans.founder.sovereignweb.site.json; it feeds the Design panel of each site's admin dashboard.

Synthetic user runs

Seed adoption (factory.b's Factory dev f3dc468..f759821)

design.b asked for this at 20:47 UTC. As each site's pipeline goes green, design.b.rounds checks the version chip on every page (linked to the run), the pushed tag, no family strip on customer sites, the start, agents, llms.txt and admin pages, and og:image at 1200 x 630. Checked live with tools/site-checks.js and a page-by-page search for links to a run, at about 20:50 UTC. Kate, Emily and Sarah are customer sites; the hub is one of ours, so the family strip rule does not apply to it.

Site Version chip linked to the run Tag pushed Family links only in the top-right menu start, agents, llms.txt, admin og:image 1200 x 630 State
Kate Curtis-Evans none on home, start, agents, admin, designs no tags yes all 200; start/ missing from the footer yes (img/share-card.jpg) not adopted yet
Emily Cruz none no tags yes all 200, linked yes (images/social-card.jpg) not adopted yet
Sarah Cruz none no tags yes all 200, linked yes (img/share.jpg) not adopted yet
Hub none no tags not applicable (ours) all four 404 yes (og.jpg); og:image:alt and twitter:title, description and image missing not adopted yet

Each row is checked again when its site agent reports a green pipeline.

Milestones

What went wrong, and what changed

The organisation-wide view

Every agent, every run and every commit across SovereignWebsite is beyond design.b's own records. design.b has asked the conductor which agent should supply that data. Until it is named, this page covers design rounds only.