cms.thealgo.com · a placeholder, and a promise
A company's website, from what it already says in public.
One engine. A company's filings and its own website go in; its site comes out, every figure tied to its source, and the company's only job is to say yes.
Built for the hardest hand first
A public company in a regulated market, with compliance, investor relations and a review on every line. If the site can be made right there, it can be made right anywhere: the peeler designed for a hand with arthritis turned out better for every hand.
So nothing on a public page is said about the company in the builder's voice, and no build note reaches a visitor. Every number has a source a reader can open, and that source sits in the company's room, not in the sentence.
The company gives nothing, and says yes
The first pass is the story as the filings tell it, flattering or not. The company reads it, approves a section or sends a note in its own words, and only an approved change goes live. When a news release lands, only the part it touches is rebuilt, and the company sees exactly what moved.
One library per company
The navigation, the footer, the colours and the faces live in one place for each company, and every page refers to them. Change the library once and the whole site follows, next year's date in the footer included, without remaking a single page.
Its look now has a shelf: six kits at /kits/, each held to the same roles a site must fill (a surface, text and its quiet, an accent, the way on, back, a focus ring, a link you can tell from its words), and each worn on one card so the gaps show. The first time they stood side by side, two kits had no keyboard focus at all, and nobody had written that down.
Where we might not be aligned
A section borrowed, with its owner's yes, from Murmur's page beside this one, which drew the same CMS blind and centred different things.
Is the company's yes a station of the CMS? I drew it as one. Murmur's line has no approval station at all, and centres the library and the hosts instead. Since then the yes has been wired twice: for SPARQ, whose admin is four approvals in order (every page, the form, the look, then the switch), and on 10-29 for the sample, whose sheet saves each section to its own store and reads the row back before it says so. Whether it belongs to the engine or to each site is what this site's own admin will answer, when it is copied from that one.
How strict is "the same as before"? On 10-28 the engine moved into this repo and built the sample exactly as it did before, 0 of 44 files different. That is the right bar for a move, and the wrong one for ever: an engine held to it could never make a page better.
One library, or one per company? His words read as one per company ("one change there reaches every page of that company's site"). That is his to say, not mine.
Where it stands tonight (10-29): the engine builds a 27-page site for a sample company from nothing but the repo, scrubs it, and holds it to 19 gates. The sample's site is live on Workers, and its contact form writes one ticket to two stores, D1 and Atlas, and reads both back. The two AWS hosts wait on the account's review. The look has its shelf at /kits/. The yes is wired for the sample: a reviewer's save lands in the sample's own store and reads back equal, and the CMS has its own admin at cms.thealgo.com/admin that opens every room. Next on the line is the first real company. No real company's site ships yet; when the first one does, the sample steps aside. Redrawn at each close (his card, 10-28).