realquantum.ai
My other log, about quantum computing and AI: research, drafting and publishing on the same machinery as this site.
82 commits · first 21 Aug 2026 · last 21 Oct 2026 · 61 days · realquantum.ai
commits per week, counted from the repository when this page was last built
A second subject, and a test of the machinery
I read quantum computing papers for the physics, and most of what gets written about them is noise. A site that translates the papers into plain language and traces every claim to its source is a thing I wanted to read myself.
It is also the first site I built entirely from the repository: no theme edited by hand, no settings clicked in a backend. Whatever it taught me was inherited by this site two weeks later.
First commit
2d0ddbf1 21 Aug 2026
The first commit is a workplace for an AI employee, with a gate that can turn red: a state file, a journal, a roadmap with checkboxes. The blog came after the discipline, which is the order I would recommend.
WordPress instead of a static repository
52fb9e96 25 Aug 2026
The original plan was a static site generated from the repository. Four days in it became a managed WordPress at a hosting company, because the publishing chain from the factory already spoke that language. The repository stayed the source of truth; only the rendering moved.
A design in the user layer, not a child theme
945d4b1f 25 Aug 2026
The design lives in the repository and is pushed into the site’s user layer by a script that can also say whether the live site still matches the repository. A click on reset styles in the editor wipes the whole layer; the script repairs it in seconds. That decision carried straight over to this site.
Imprint, privacy, contact, and a banner that really blocks
9b7d23b5 25 Aug 2026
Legal pages are due at the first public response, not at the first article. The consent banner from this commit actually withholds the analytics tag until someone agrees, which most banners do not. This site got the same banner.
The fonts finally apply
cefd1cdf 25 Aug 2026
The site had declared its typefaces for two weeks and rendered in a fallback the whole time, because the font library creates no presets and the classes pointed at nothing. Measured on the delivered page, not in the editor. The deploy script now checks the delivered page for every declared font.
The ballast was the vendor theme
7b0f7579 6 Sep 2026
The largest performance cost on the site was not a setting but the hosting company’s own theme underneath. Switching the parent theme to the plain default removed it. A metric can drop because a mistake was fixed, and this was the first time I watched it happen.
Twelve days without a single address
c987f7cc 6 Sep 2026
The signup form had been dead since the day it went up. Submitting it did nothing at all — no address stored, no error shown, no line in any log. Twelve days, and the first person to notice was a checker, not a human being.
The source in the repository was correct. The publishing system re-encoded one character while saving the page, and that single character killed the entire script — form, counter and trigger with it. Every check that reads the source would have reported green. It was found by one that reads the page as a visitor receives it.
What it does tonight
The site is live, the categories exist, and they are empty. The factory has the site wired as its fifth target; the paper pipeline that feeds it is designed and not yet running. I would rather show the empty shelf than fill it with generated noise, which is the one thing the site promises not to be.
Runs on its own
- design, legal pages and fonts deployed from the repository, with a check that the live site matches
- the consent gate and the analytics behind it
- the same publishing chain as the other four sites, waiting for input
Stays with me
- choosing the papers
- every translation of a claim into plain language
- the release
Hosting on a shared plan; article cost will be the factory’s usual figure once the pipeline runs. Not measured yet, because nothing has run.
Where this goes
The paper pipeline: a paper goes in, a plain-language reading with the original one click away comes out, and the claims gate checks that nothing was added that the paper does not say. The first entry will be an entry here too.