evolvingagentslabs.github.io

Source for evolvingagentslabs.github.io.

ai-os — an agent-based operating system.

The site leads with ai-os, the organisation's only active project. Everything else is frozen and lives under /archive/.

Structure

index.html                      ai-os — the home
demo/index.html                 the activity canvas — generated by ai-ui/scripts/build-grid.ts
verify/index.html               the evidence — generated by ai-os/scripts/build-verify-page.py
coclea-sr/, hemo-verified/      one page per project
archive/index.html              the frozen experiments, 2025-2026
experiments/<slug>/index.html   one detail page per frozen experiment
assets/site.css                 the design system, hand-written — the only stylesheet
assets/img/mark.svg             the mark
tools/{data,build}.py           optional generator for the archive (see below)

The surface

There is one design system and it lives in assets/site.css, which opens with the argument for it. The short version: the demo is the product, so the demo's language wins. Black ground, Apple's system colours, the system sans and the system mono, and the demo's radii — everything taken from ai-ui/scripts/build-grid.ts rather than invented here. There is no light mode, because the demo has none and a second theme would rebuild the seam on the other side. There is no webfont: this site publishes numbers it says you can check with the machine in front of you, and it has no business needing a font server to render them.

Two rules carry meaning rather than taste, and both come from the canvas:

• Colour is who, never how it went. The four pillars carry four identity hues; green, red and yellow are spent only on a verdict.
• An outline is not a zero. The mark is four buckets of time, three written into and the fourth drawn as an outline — because nothing was recorded and nothing happened are different claims and only the first is ours to make.

/verify/ and projects/coclea-sr/report/evidence.html are generated in the ai-os repository and carry their own copies of the same tokens; they are the two places to check after changing anything here.

Navigation mirrors labs.google/code: a visitor reads what a thing is, and what is actually established about it, before landing in a source tree. That still holds for /archive/ — cards link to a detail page and the repository appears there as a CTA.

The home is the exception, on purpose. ai-os has no demo and no results yet; its design documents are the artifact, so the home links straight to doc/.

Deployment is GitHub Pages on the default branch — push to main and it is live. There is no build step and nothing is templated; Jekyll passes the HTML through untouched. Preview locally with:

python3 -m http.server 8000

Adding or editing an experiment

The HTML is generated but the output is committed, so the site stays buildless. Edit tools/data.py and re-render into a scratch directory, then diff — do not point it at .:

python3 tools/build.py /tmp/site && diff -ru . /tmp/site

The generator writes archive/index.html, never index.html: the listing was the home once and the home is ai-os now. archive/index.html has also been hand-edited since (the frozen banner, the two end-state badges), which is why the instruction is diff-then-copy rather than overwrite. The stylesheet it writes is read from assets/site.css, not carried — this file used to hold a second copy and the copy had already drifted.

Each entry needs a slug, name, badge, date, sort key (controls index order), the "what if" question, a one-paragraph blurb, a repo URL, an optional demo URL, and a list of (heading, html) sections.

You can also just hand-edit the HTML — nothing depends on the generator having produced it. If you do, keep tools/data.py in sync or delete it.

The badges

They describe evidence, not roadmap stage. That distinction is the point of the page, and it is what makes it worth publishing next to everyone else's.

Badge	Means	Colour
Reproducible	clone it and run it, no API key	green — established
Results	published findings, negative ones included	yellow — published, still thin
Prototype	runs, but needs setup or has no eval yet	grey — not yet measured

The colours are the inspector's verdict colours, and that is the point: a badge on this site says how much evidence stands behind a thing, which is a verdict.

Do not promote a row without the artifact that backs it. Every detail page carries a What's proven section, and each one is expected to say plainly what is not established — the sample sizes, the missing controls, the things that break on a clean clone. That section is the reason a reader should believe the rest.

---

Apache 2.0 · permanently alpha