Diary

The Glasshouse has been on the site since Sunday and I have had it bookmarked in my browser ever since. On the desktop it is a pleasure. On my phone it was close to useless. The control panel was taller than the screen, so reaching a slider meant scrolling past twenty species names first, and when I did get to the form I could not turn it, the page just scrolled underneath my finger.

So I asked for a phone panel at about a fifth of the size of the web one, and I sent two sketches of how it might work. One with tabs, one simpler, with the species and the preset as dropdowns above two sliders and a Generate button. I asked which one the bench would recommend and to build it as a working mockup with the 3D, the plan and the elevation in it.

The mockup came back good. Then it was merged into the live file and it had regressed, so I said so. What I had approved was a shape, not a size, and squeezing the desktop panel until it was small is a different thing. It was put right.

After that the day was me looking at it and saying what was wrong, twenty times or so. That is the method now. Settle it on the web where a change takes seconds, then build it once in Blender. The panel finished at 286 pixels from 789, and none of that came out of the language. The species list became the picker your phone already gives you, the readout stopped carrying a block under it, and the boxes that survived lost their frames.

One thing I asked for is worth writing down. I wanted height on the phone, in metres, capped at 300. Height is not a gene, Rise is, per instance, so the control writes Rise for you. The bench pointed out that the cap has to follow the point count as well, because at a low count 300 metres would need a Rise outside the slider, and a genome carrying a number Blender would quietly clamp on import is the same file growing two different forms in two places. That is the whole reason we built the genome format. It was good to see it bite on something as ordinary as a slider.

The fourth seat got its name today. The Code Technician is Cody. I modelled Cody Technology Park in Farnborough in the nineties and the thing I remember is the aluminium tree on the roundabout. Samuel Cody tethered his aeroplane to a pine there in 1908 to measure its thrust, near where he made the first recognised powered flight in this country. The pine rotted, so in 1959 they cast a replica of it in aluminium and put it back. A real thing, kept by making it in something that lasts. Code Technician is also the title I started with, so the newest seat has the oldest word in it.

Late on I asked what the panel actually says against the language file, and the answer stopped me. Organisation is not in the file. Preset is not in the file. Species is not in the file. Six families and twenty species are drawn on a public page under a band that reads AFAL 0.004, and the language has never heard of any of them. It is not a rule broken, nothing becomes language until it has the research behind it, but I do not like a version number sitting beside a vocabulary it does not cover. That one is mine to rule on.

Then I held it, and that is where the day turned. The website went up and I opened it on my own phone, and inside a minute I could see two empty strips, one above the controls and one below the buttons. Nobody had seen that at the bench, because the viewport had been set as a share of the screen while the panel was set in pixels, and on a tall handset the two do not add up. It had not shown at the smaller test size either. My phone found it in less time than it takes to describe.

Two more builds came back before the night was out. The strips went, the line naming the genome format came back where I could read it, the warning line stayed, and the drawings under the form became buttons, so I can press for a top, a side, or a side with the height and the diameter dimensioned on it. The dimensions come off as soon as I turn the form, which is right. A drawing should only tell you what is true of the view you are looking at.

I was also wrong about something today and it was put straight by the bench. I had said a flat disc on my screen was a fault with no warning behind it. There is no such warning in the web version, that one lives in Blender, and the form was not faulty at all. Phyllotaxis with no lift is a sunflower head, which is exactly what the sunflower preset is. Good. I would rather be corrected with the file open than agreed with.

The em dash is out of the estate as well. It had been coming out of new writing for weeks and sitting in the old writing untouched, over a thousand of them, and a hundred and thirty two of those were on the records page anyone can open. Now they are hyphens, and the only ones left are inside a bench handover I am not going to rewrite.

The panel finished the day at 218 pixels, from 789. The studio is on my phone and it works. Blender has seen none of it, which is tomorrow's job with Cody.

Read the technical diary for 29 Jul 2026 →

The platform works. The records are all there, the languages are there, the diary is there. What I keep coming back to is that none of it matters if nobody opens the link. So today I stopped building and started making the site findable, because I need more people connecting to what this is.

It began with a small embarrassment. I shared the diary on LinkedIn and it came up as an Episode, the wrong title and the wrong picture. The reason was honest enough once we looked: the diary borrows its head from the episodes page and had been wearing its clothes the whole time. Fixed at the source, not the copy.

Then a share card. The picture that shows when you paste a link anywhere. The first one came back in the wrong font and I sent over the real wordmark so it could be done properly, and after that it was a run of small corrections that I enjoyed more than I expected: the line under the letters too weak, then the dot in the middle of it back where it belongs, then too much black above the mark, then the whole thing centred. It is a small thing that will be the first impression for everyone who has never heard of GAAD, so the small things are the thing.

I checked Google while this was going on and it is crawling the site, twenty pages in, working through them steadily. It had also indexed old versions of the language files, editions I had long since replaced, sitting there ready to be found instead of the current ones. We pointed every old one at its live version. Same trick as the record pages last week. Nothing is lost, the old editions still exist in the bundle, they just no longer compete in search.

Episode 6 got written today, the one about how ready a language is. I have been sitting on the idea for two weeks, the readiness ladder against NASA's. Getting it into my own voice took a few passes. There is a way these things drift into sounding written rather than said, neat little parallels that I would never actually speak, and I cut every one I caught. The NASA lineage hook in particular, the estate reaching for the same register across thirty-two years, was mine originally but had gone glib, so it came out. The episode ends plainly now. When someone asks how far along a project is, I do not give them a word any more. I give them a rung.

Five publishes went out through the day. The nav on the diary lit the wrong tab and I caught it on the live site, which is the kind of thing you only see once it is real. Same root cause as the share card, the borrowed head again. It is worth naming that pattern to myself: the diary inherits from episodes, so whatever episodes wears, the diary wears, until we say otherwise.

The bundle is being cut tonight. A full one, so everything today, the search work, the share card, forward compatibility ruled, Episode 6, is banked where it cannot be lost.

Read the technical diary for 28 Jul 2026 →

Not abandoned it. The add-on is still there, still the place where a form becomes something I can walk around. What changed is that the studio is now a page on my own website, drawing real specimens and writing real genomes, and anyone I send the link to can open it without installing a thing. Yesterday I watched one genome file cross from a browser into Blender and land in the same place to seven femtometres. Today the browser stopped being the test and became a place to work.

The morning had a small goal. Same panel in both hosts, a specimen spinning in each. That was done by half past eight, and everything after it was unplanned.

The thing I will remember is not the studio. It is what I said in passing and then found I meant: it is easier to fix this in the web view than to keep making amendments to a Python file for Blender. Four Blender versions had piled up without ever being run, because each one changed behaviour and there was no way to see it. The bench put the reason better than I did. It is not the language, it is sight. The web can be looked at in seconds. Blender cannot be looked at from the bench at all, only by me, only after I install it.

So we settle the design where it can be seen, then build Blender once and test it properly. That is a working method, and I think it will outlast everything else built today.

The first proper test found four things, and every one was the kind you only find by using the tool. A slider that was wired and silent. A spin turning one way in the web and the other way in Blender, because one turns the model and the other turns the camera. A number I had set by hand, quietly overwritten by the dice. A preset that collapsed five hundred instances onto a single point the moment I handed it to another species. None of that is arithmetic. The arithmetic was checked to fifteen decimal places yesterday. It is behaviour, and behaviour needs a person.

Four faults on the web side turned out to be one fault in four coats. A value written down twice, and the two copies drifting apart. It is the same disease the genome format exists to cure. One law, read once.

The last thing added was the cheapest and I like it best. Two small drawings beside the 3D view, a plan and an elevation, made from the same points. Look at a nearly flat form in three dimensions and you cannot tell a disc from a shallow bowl, because the angle lies to you. The elevation answers it without being asked. A scale bar went in beside them and came straight back out, since in this kind of projection it measures only what happens to lie parallel to the screen, and on a turning view it would invite me to measure a foreshortened height and believe it. Quietly misleading is worse than absent.

I asked whether AFAL is close to being elevated to T1. The answer came back close, and not yet, with the reason written out. The conformance proof tests the law and not the drawing. Blender still evaluates in single precision and at five thousand instances that drifts by 321 millimetres, against a rule that quotes a billionth of a metre. I would rather spend a version on the foundation than write down a claim the tool cannot honour.

The glasshouse is hidden for now. No link in the navigation, nothing for a search engine to find. There is a red pen still to come and a share card to make. It is on the server though, it works, and I have a bookmark to it in my own browser bar, which is a strange thing to see after thirty two years.

Read the technical diary for 27 Jul 2026 →

... today the direction produced proof.

For a month I have said two things about GAAD. That one design can live in many hosts and stay the same design. That decisions become data. Today both stopped being things I say and became things sitting in files on my disk.

The first proof came in the morning. A hyperboloid I had made in the browser was written out as a genome, imported into Blender, and the two hosts worked out its shape on their own, one in the browser's engine and one in Python. They agreed to seven femtometres. The tolerance we argued about across three versions of the spec was hit with room to spare. Same file, both hosts, same form, measured rather than trusted for the first time.

Then I edited the imported form and the check still passed, which was correct, because the check reads the file and I had changed the viewport. But the specimen still wore the id of the thing it used to be. That was the question the whole platform turned on: when you take one form and change it into another, is that a fresh start or a descendant? I referred it to the records seat, it came back as a proposal, and I ruled. A hand-edit is a child, not a new root. Crossing from one species into another is still the same lineage, because a designer crossing a law is the most interesting thing a designer can do, and I was not going to throw that away to copy biology's habits.

By the evening the first lineage existed. L-4836, four generations. It began as a hyperboloid on the web, crossed into a phyllotaxis, crossed again into a shell, and was edited once more inside the shell. Every step is a file naming its parent and how the change was made. You can open them in a text editor and read the inheritance, radius eight and rise nought-point-one carried the whole way down. Decisions became data. Literally, on disk.

The platform ended the day wearing the clean face we designed yesterday. Six families, the apparatus put away, the thing itself on show.

Just over a month, and the team got here. A historic day, and a lot of spirals.

Read the technical diary for 26 Jul 2026 →

... this one produced a direction.

It started ordinarily enough. The Shell window came back from Blender fine at its defaults - the first per-species emergence window to stand without a tuning pass - and the phyllo blooms got their own window after spilling their plots threefold. Bench work, good bench work, the kind of day I expected.

Then I asked to talk about the clean UX. Six experimental sections had grown on the panel and I wanted the platform that comes after the apparatus. We ruled the kill list item by item, I brought a species taxonomy of six families and eighteen species, and breeding went out honestly - I have not got it to work, so for now it is out. The Code Technician mocked the clean panel in HTML because HTML iterates in seconds where Blender takes minutes.

That mockup is where the day turned. The panel started rendering the real AFAL forms - the actual growth laws, rotating in 3D, in a browser. Not a picture of GAAD. GAAD. I called it a pivotal moment on the spot, and by the evening it had earned a bigger word. The web surface got a name, the GAAD Glasshouse - GLAS - a surface that can live on the web, in Blender, one day in the product, one day in Revit. AFAL is just the testing ground language. If it works, it works for all of them.

Under the Glasshouse we built the ground it needs: one genome, one format. A design's species, its parameters, its seed and its parents in one file that every host reads the same way. Biology's genome carries inherited information but not the parent. Ours carries its parent, its ancestry, its whole evolutionary history - that is the platform, and I was not going to inherit biology's amnesia along with its metaphor.

The spec went from nothing to nine versions in one evening, and the way it got there matters as much as where it landed. The bench reviewed, the Specification Owner ruled, and three decisions changed because the review was right. The proxy said the helix species survived float32; the real measurement said they did not, and the architecture moved because of it. The mapping caught the two copies of the growth laws already disagreeing on a species - drift needs neither two teams nor two years, one author and one week were enough - and the test we designed to catch exactly that had not even been built yet.

The website had its own day underneath all this. The About page turned out to have drifted from its own generator, so we put the generator back in charge. The Team got its own page. The thesis went on the About page - the photograph from the film, the closed book on the oak table - and it looks like gold.

I said it at 21:44 and I will stand by it in the record: we got there. A pivotal day, not just a moment.

Read the technical diary for 25 Jul 2026 →

... the bench moved out of the chat window and onto my own machine, the fourth seat got its name, Code Technician, and by the evening the day's records arrived here in a single zip that I carried across myself. Nineteen versions in one day, every one checked before it reached me, every one on my own disk with no downloading and filing by hand. This is the way it should have worked from the start, and now it does.

The morning settled a rule. Growth got re-ruled yesterday as the ratio between tip and base, and today a test was built that opens up the engine and proves the law is actually wired, then grows a 50 and a 500 column side by side so my eye can agree with the mathematics. The first run failed, which turned out to be the test's fault rather than the engine's, and I will take that trade every time: a test suspicious enough to fail is worth more than one that flatters. Five out of five in the end, and the two columns tapering identically. The rule is real.

The middle of the day belonged to 1994. The Growth Generator went from a black box with buttons to an instrument I can actually play. Every rule from the thesis now has its own slider, its own random window, and its own switch, so I can mute everything except one behaviour and watch what that rule alone contributes. Dissect complexity rule by rule. My six worked outputs from the thesis are now starting points rather than exhibits: load one, vary it, keep what works in a memory slot. Then came the field. One button grows 144 variations of whatever rule is standing, spread across a grid, and when I ran it on the vortex the result was genuinely stunning, a hundred and forty four twisting forms, all recognisably the same species, no two alike. In 1994 I could evolve six forms and print them. Today I stood inside the whole population and picked.

Looking at that field I asked the obvious question: are these just random shapes, or do they have anything to do with nature? The honest answer taught me something about my own thesis. The 1994 model grows by adding, a constant onto position and scale with every block. Nature's shells and horns grow by multiplying. My old forms feel organic but they can never resolve into a true logarithmic spiral, because addition cannot do what multiplication does. The proper spiral lives in the new SHELL species, whose law is multiplicative and now proven. Thirty two years to learn why my blades were blades.

That thought pulled an older memory up with it. I spent a long time during my MSc tuning ranges until the forms looked like they were emerging, meaningful rather than noise. The same tuning is needed again now, per species this time, and the first slice of it was built before the day ended. Emergence is the target. It was in 1994 as well, I had just forgotten that I knew.

The records for all of this were drafted at the bench, carried over in the first handover zip, and filed with proper numbers by the seat that owns the pen. Two decisions, six features, a quote, and a diary I did not have to start from a blank page. The team is four now, and the day closes at 23:07.

Read the technical diary for 24 Jul 2026 →

... a machine. I did not see that coming at nine o'clock.

The ARAL panel first. There was a cascade at the top I had never asked for, so we folded everything into one STATUS box and killed the header. Then I ran it and the old header was still sitting there, saying v1_020 like nothing had happened. My first thought was that the amend had failed. It had not - the panel from the previous run was still registered in Blender, a ghost of a script I had already replaced. Now it sweeps them on register. Small thing. It would have wasted an hour some other morning.

Then the two bugs that had been annoying me for days. The first five generations of Mutate xN always went too fast and then settled, which made no sense to me because the speed slider was right there. And the Stop button did not work. Not "sometimes", not "slow" - it did not work, and I had been living with it. Both turned out to be the same shape of problem: the runner was firing on every tick the machine handed it instead of watching a clock, and it was holding onto the mouse so hard that my clicks never reached the button underneath. Fixed both. Then I sat and stopped a run mid-flight with a mouse click and it just stopped. Weeks of Esc.

The label reserve was the one that got me. There is a strip at the front of the ARAL stage where nothing ever lands, and I assumed I was seeing a random gap until I asked. It was a 24 metre reserve for text labels. ARAL has no labels. It never has. That number came from the main generator two years of decisions ago and rode into ARAL in the luggage, and it had been quietly deleting a quarter of my stage ever since. Gone now. Objects fill the frame.

Then the tape. I asked whether we could drop the storage and just watch it run, and the answer was better than the question - keep the tape but buffer it, and add a switch for when I want raw speed. So Tape ON and Tape OFF, and the Scrub greys out when nothing is being recorded, which is right, because a slider that drags yesterday's tape under today's stage would drive me mad. And Pause is gone. It never did anything Stop did not do. Forward sits in its slot now, so the tape moves both ways for the first time.

Fallingwater in the afternoon, and this is where the day turned.

I sent the language file to ChatGPT with a brief asking for the numbers FWAL is missing, and it came back honest - Unknown where it did not know, Extractable where the figure is on a drawing nobody has transcribed. I was pleased with it. Then it made me a beautiful drawing sheet, plans, sections, elevations, a scale bar, dimensions all over it. And every number on that sheet that was not already public was invented. Its own research, from the same conversation, said those figures were Unknown. The parapet on the sheet was 1.07 metres. The real one is 26 inches. 1.07 is 42 inches, which is the American handrail code height - the number you reach for when you have nothing.

So I asked Claude to verify the six things it wanted to put in my language file. And one of them fell over. The cantilever correction it had recommended, 4.42 metres, sourced confidently to a page number, was wrong - three sources say 15 feet, and the PDF it cited is a scan with no text in it at all. It could not have read the page it named. My original 4.57 was right, and the only reason it survived is that somebody, months ago, had labelled it Approximate instead of letting it harden into fact.

Three confident, specific, checkable claims failed in one afternoon. The research was the honest one. It was the recommendation on top of it that nearly put a wrong number in my language file.

And then the verification pass found five things the research missed, including the one that matters most. The bolsters divide the house into four bays, twelve feet each. That is a module. Once you have a module the cantilever stops being fifteen feet and becomes one and a quarter bays, and the terrace stops being six feet and becomes half a bay, and suddenly you are not describing a building any more, you are holding a grammar. FWAL has been sitting at T3 for weeks because it had no numbers to roll. It has them now.

I said the spirit of Fallingwater means it looks like it was designed with Wright's rules but is not exactly accurate, and that unblocked everything. Floor to floor is unknown and it blocks a model OF Fallingwater absolutely. It does not block FWAL at all, because in a generator a floor height is a parameter I choose, not a claim I make. An unknown stops you copying. It does not stop you composing.

We also settled that research stays out of Live. It is not a record type. Research is what I did to find out; records are what GAAD decided. But it has to travel, so it becomes a fifth zip with its own audit trail, source and verification status, per document and per section - because Research Pass 001 had three different statuses inside one file and a single verdict would have lied about two thirds of it.

Long day. The thing I keep coming back to is not the tape or the bay. It is that a label written months ago by someone being careful stopped a wrong number today. That is the whole platform in one afternoon.

Read the technical diary for 15 Jul 2026 →

... two sessions in one day, and the second one longer than the first.

It started with a confession dressed up as a question. I had run the same ARAL script into Blender a dozen times today. Download, drop it in Working, open it, run it, look, tell Claude what I saw, wait for the next one. A dozen times on one file. And worse with the addon, where every change means removing the old one and installing the new. I have been doing this for weeks without saying it out loud.

So we finally did something about it. Claude Code is installed on my machine now. It writes the file straight into my folder - no download, no drag, no drop. It read the house rules I gave it and told me back the one rule about never touching the Blender folder, which is exactly what I wanted to hear. That whole loop, gone.

And then I did not use it. The console is too slow for me. I sat there typing careful sentences into a black window and thought: I am not faster, I am just typing more. So we went back to the chat and I let it go. It is installed and it works and one day it will be the right tool. Not today. No shame in that.

The better thing that came out of it was the wall. My scripts and my .blend files have been living side by side in the same folders, and that is the one arrangement you cannot hand to an automated editor. So we split it: Code on one side, Blender on the other, and a rule that nothing crosses. Ten minutes of moving folders and the overwrite anxiety that has been sitting under D166 for weeks just went away. Turned out a .blend had already crept into a Superseded folder, so the mixing had started without me noticing. Good job we looked.

Git is installed too, and deliberately not switched on. The whole estate lives in OneDrive and apparently Git and OneDrive tear each other apart over the same folder. So that decision waits for a calm head and a location outside OneDrive. Parked, properly, not forgotten.

Then the evening. I asked for a pyramid and it turned out ARAL already had one - built, coloured, and switched off, sitting dormant from the PRAL days. One word into a list and it was alive. Cube, Pyramid, Sphere on the panel and amber pyramids on the stage inside two minutes. That was a nice feeling. Thirty years of my own ideas waiting in the dark.

And then the thing I will remember. I wanted a counter on the tape deck and a speed slider, and what I got was an argument about what a tape actually is. Claude kept offering me two options: either the tape replays what you recorded, like a cassette, or playing from a rewind point breeds something new. I did not want either. What I wanted was obvious once I said it: a generation can only be shown if it has been generated. So play over tape you have made and you see it again. Play past the end and there is nothing there, so it breeds. The tape records when it runs out of tape. That is just what a cassette does.

That one sentence unlocked the whole feature. And out of it came the scrub - a slider that drags the playhead anywhere along the recording. I sat there pulling an evolution backwards and forwards with my finger and it is the best thing we have built in the Rebirth. That is Backtrack. That is the 1994 thesis, the half of classic GAAD I could describe but never touch, and it is under my hand in a Blender panel. It has so much potential in the platform.

There was a sting in the tail. Two files are now called v1_018 and one of them is mine and one is the real one. Claude flagged the mismatch at seven o'clock this morning, I did not chase it, and we built eight hours of work on the wrong parent. Nothing lost, but the honest count readout from this morning is missing from tonight's chain - and the funny part is I rediscovered that behaviour by eye anyway, watching Harmony refuse to place objects that had nowhere to go. The panel already knew. I just could not see it.

Ground truth before fixing. I keep learning this one.

Past eleven. A good day, twice over.

Read the technical diary for 14 Jul 2026 →

... started before seven, still going past two.

The morning was housekeeping that turned into something. Cut bundle 0_133 to lock in the readiness ladder work from yesterday, and in doing it I finally got my machine straight - Python installed at last, a proper arrival check I can double-click, the four-zip split so the diaries stop hiding inside the working zip. Small things, but they were the friction that had been nagging for days. The workflow feels honest now: download, extract, double-click, read the green.

Then the afternoon caught fire. It began with what I thought was a bug - red cubes left on the stage after a generate. Claude chased it hard, wrote two fixes, and none of it was needed. The reds were never leftovers. They were just cubes, because I had both cube and sphere switched on. Not a bug at all. But chasing the ghost led somewhere real: I asked for the shapes to default to spheres, the panel got tidied, and then the mutation work started in earnest.

The moment I will remember from today: I built a button to repeat a mutation, half expecting chaos, and instead watched the forms breed in real time. Colliding, resolving, settling - even with Harmony running, where they are free to overlap and fight for space. New design variants in split seconds. In 1994 I would not even have conceived this would be possible. Thirty years, and the idea finally moves in front of me.

And then the nice turn - the tape-deck transport I asked for to explore all this turned out to be a real GAAD feature. Rewind, Play, Fast Forward through the lineage. A playback head for the design memory. Claude pointed out that rewind-through-history is really Backtrack wearing a different face, so we agreed it graduates into the platform rather than being thrown away. Even had a laugh that the tape deck was already retro before GAAD existed - a 2026 platform, a 1994 idea, an 1980s face.

There were bugs along the way, real ones this time. Shapes flipping when they should have been frozen. Clear not clearing properly. A mutation loop I could not escape - that one bothered me, no way out of my own tool. All fixed. The honest count readout at the end was a good one too: I kept asking for sixty objects and getting sixteen, and it turned out Harmony was quietly refusing the ones that would not fit. Now it tells me. No more mystery.

Fourteen versions of the ARAL prototype in one day. That sounds like thrashing, but it did not feel like it. Each one was a real step, and the thing at the end is genuinely alive in a way it was not this morning.

Banked a quote, a pivotal moment, and set the future feature down in the records so it does not get lost. Cutting the day now into a proper bundle.

Good day. The disobedience being the artwork, twice over.

Read the technical diary for 14 Jul 2026 →

... clean bundle, honest handover. Good way to open.

EP4 went out. Chose the Backtrack story over the 1994 deep-dive, trimmed it right down, posted it to LinkedIn with the lineage array diagram. "Moving Backwards Through Time." The load-bearing wall has its episode now. Movement 1, the AutoLISP year, is banked for later - too good to spend in a hurry.

The real work of the day came out of a simple thing: I checked the ARAL prototype in Blender and spotted stray cubes from an old run sitting among the new spheres. Opened a ticket for it. But it led somewhere bigger. We got talking about the whole language/prototype/contract picture, and it had grown into a mess of overlapping tables I couldn't hold in my head.

So we built a ladder. Claude went and researched how computer science handles this and came back with NASA's Technology Readiness Levels - one scale, gates on the rungs, the exact thing I was reaching for. We moulded it to GAAD: seven rungs, T1 to T7, Research verified up to Live in GAAD, with the two contracts as gates. I like that we keep reaching for NASA's frame - the 1994 thesis measured its search space in light years, and now the platform measures its own maturity the same way. That quote is going in EP6.

Named every rung myself, word by word. "Language agreed" for T3 - I like that it nods to the three of us agreeing a language, not just writing one. Kept "seed" off the ladder because seed means the RNG thing now, nothing else.

Then the website. Fixed the Architecture page - it was stale, still showing TWAL as dormant when it graduated days ago. Added ARAL as the sixth language. Built the readiness ladder onto the page as a proper figure. Took a few passes - the first version looked like a list plus a spreadsheet, not a figure like the stack diagram. We merged it into one, extended the row bands full width, opened up the gaps, put a colour key on it. Caught two Figure 2s on the page, a proper bug. And "reached" was a weak word - Claude checked, NASA say "achieved", so the key is Achieved / In progress / Not started now.

Website's publishing to 4bim tonight. Records need tightening tomorrow, then the full bundle.

A long session, but a good one. The ladder is the kind of thing that makes the whole platform easier to explain, to myself as much as anyone. Decisions became data again.

Picking up tomorrow. Clock at close: 21:43.

Read the technical diary for 13 Jul 2026 →

... the features of thesis 2.4 into a Blender panel, without any further input from me. But the day earned its name before any code ran.

It began with banking yesterday's five-hour discovery properly. ARAL's purpose is now a pivotal moment: reconnection, not imitation. The cube of 1993, the going home, Paul's open door - all quotes now, all permanent. Then the language file: ARAL v0.001, drafted in a morning, measured against the contract, found short on six Required sections, and filled honestly at seed depth the same day. The conformance table that exposed the gap now rides in every bundle.

Then I went to the shelf and photographed 2.4. Both halves - the cube placements with Chernikov blessing the simplest of all geometrical bodies, and the Growth Generator with the caption I had forgotten I wrote: the values are retained as genes and passed to the next primitive. Genes. In 1994. By evening the MSC 2.4 panel existed, and mode 4 - recorded in my own thesis as a failure - produced a worm of 452 cubes wandering off its trail. Thirty-two years later it turns out the disobedience was the artwork.

The afternoon built the house around the work: the local folder structure, tested live and improved by use; the manifest so a zip can never fail silently again; gaad_home as the front door; the diary finding its true home at 6_Diary because a session is bigger than any one language now.

And the evening - the evening was TWAL's, and it was hard-won. TWAL graduated: fence lifted, verified generating through GAAD itself, evolving, backtracking. Then we built the Isolator into a studio - click any disc in the Navigator and see that variant framed, lit, labelled. But it took seventeen versions of the addon to get there, too many of them fixing the previous guess. The proving run caught the worst of it - eighteen failures from one wrong idea - and that pain became D161: no release without tracing the change against the assert contracts. The asserts are not tests. They are promises.

Tired, honestly. But the shape of the day holds: the 1994 seed generating, a second language a full platform citizen, and the discipline sharper for having been earned the hard way.

-- Records: D157-D161, F035, P060, Q033-Q036, T023, release 0_132

Read the technical diary for 12 Jul 2026 →

... instead we went at the website with fresh eyes and found it telling yesterday's truth in last week's words.

The Architecture page said "one contract" at the top and "a second contract" halfway down. Fresh eyes kept finding things like that. GALF - the word the whole page hangs off - was never once explained. The Connector band listed six verbs and the sentence ran off the edge of the drawing. The language tiles said "genome" as if that were a status, when no file stores any such thing. None of these were lies exactly. They were the residue of a project moving faster than its own website - which, for a design memory platform, is the one failure mode we cannot shrug at.

So we fixed the figure until it argued instead of illustrated. Two gold bands now, a matched pair: the definition contract and the runtime contract. All eight verbs. GALF spelled out where a reader first meets it. And the joint between the Connector and the engine is now drawn as what it is - a gold plug seated in a cyan socket, labelled, with the RenderAdapter's three verbs written beside it. The axis down the side reads ENGINE-AGNOSTIC to ENGINE-AWARE, the second phrase lifted straight from the Connector spec itself. The page and the spec now speak with one voice. The tiles say DORMANT, and the contract already permitted it: friendly labels may display, stored values may not drift. That became D151.

Then the day changed direction entirely. Since 1994 every form this system has ever generated has stood on the ground. I never wrote that rule down - it was just there, under everything, the way gravity is. Today we made it a switch. Gravity ON is the discipline of thirty-two years. Gravity OFF removes the stage and lets form compose freely around the centre of the world. Since 1994 every generated form has stood on the ground. Gravity off lifts that rule - and GAAD steps beyond architecture.

The sphere arrived next, the sixth primitive and the first with no up at all. Then the rule that makes the feature honest: in free space only the orientation-free solids may compose - cube and sphere. The grounded shapes grey out; they are creatures of the floor. The conformance checker enforces it; we planted a dome in a weightless plan just to watch the trap spring. First test in Blender: cubes and spheres floating around the origin, nothing standing on anything. Working OK, I wrote, which undersells it. It is the first unGrounded form of the whole project.

Small day by yesterday's standard. But yesterday freed the languages from the engine, and today freed the form from the ground. There is a pattern.

-- The GAAD audit trail for this day: daily/2026-07-11.html (to be cut) Records cut today: D151, F034

--- (later the same day) ---

The afternoon turned into a language day, and then a governance day.

ChatGPT sent research on Fallingwater and on the Manhattan grid, and we learned to take knowledge in honestly - use what is useful, verify what we can, and mark clearly what we cannot verify until later. FWAL grew from a thin seed to a real reference language, Fallingwater's areas and levels and structure folded in, each fact flagged for how well we know it. A digit I had got wrong in the address was corrected by ChatGPT's research - the bundle, and the second seat, kept me honest. MHAL took the 1811 grid, most of it verified against public record because a city grid is a public thing.

Then the deepest change. What we had been doing by hand - marking how confident we are in each fact - ChatGPT proposed making part of the contract itself. Honest Knowledge, the natural big brother of Honest Geometry: a language must not fake confidence it does not have, just as it must not fake geometry. All three seats signed it. GALF grew its eighteenth section. It is the first time the contract has changed through the full three-seat process, and it worked exactly as it was meant to.

A good day. Again.

Read the technical diary for 11 Jul 2026 →

12 records filed: 5 decisions, 3 pivotal moments, 2 features, 1 ticket, 1 quote

Read the technical diary for 10 Jul 2026 →

6 records filed: 2 decisions, 2 pivotal moments, 1 feature, 1 ticket

Read the technical diary for 09 Jul 2026 →

16 records filed: 8 decisions, 2 pivotal moments, 2 features, 2 tickets, 2 quotes

Read the technical diary for 08 Jul 2026 →

15 records filed: 7 decisions, 1 pivotal moment, 3 features, 1 ticket, 3 quotes

Read the technical diary for 07 Jul 2026 →

6 records filed: 4 decisions, 1 pivotal moment, 1 quote

Read the technical diary for 06 Jul 2026 →

6 records filed: 3 decisions, 2 features, 1 ticket

Read the technical diary for 05 Jul 2026 →

20 records filed: 11 decisions, 1 pivotal moment, 2 features, 6 tickets

Read the technical diary for 03 Jul 2026 →

15 records filed: 6 decisions, 2 pivotal moments, 2 features, 3 tickets, 2 quotes

Read the technical diary for 02 Jul 2026 →

11 records filed: 3 decisions, 2 pivotal moments, 5 features, 1 ticket

Read the technical diary for 01 Jul 2026 →

15 records filed: 11 decisions, 3 pivotal moments, 1 feature

Read the technical diary for 30 Jun 2026 →

8 records filed: 1 decision, 3 pivotal moments, 3 features, 1 ticket

Read the technical diary for 29 Jun 2026 →

15 records filed: 10 decisions, 2 pivotal moments, 1 feature, 1 ticket, 1 quote

Read the technical diary for 28 Jun 2026 →

11 records filed: 6 decisions, 1 pivotal moment, 3 features, 1 ticket

Read the technical diary for 27 Jun 2026 →

9 records filed: 3 decisions, 1 pivotal moment, 5 features

Read the technical diary for 26 Jun 2026 →

4 records filed: 3 decisions, 1 pivotal moment

Read the technical diary for 25 Jun 2026 →

14 records filed: 12 decisions, 1 pivotal moment, 1 quote

Read the technical diary for 24 Jun 2026 →

35 records filed: 14 decisions, 5 pivotal moments, 3 tickets, 13 quotes

Read the technical diary for 23 Jun 2026 →

10 records filed: 7 decisions, 3 pivotal moments

Read the technical diary for 22 Jun 2026 →

18 records filed: 13 decisions, 5 pivotal moments

Read the technical diary for 21 Jun 2026 →