Design Memory PlatformOn the homepage Records-over-time graph, each line carries a small dot in the line's own colour on every day that series gained a record, and each dot is a hyperlink into the matching record page anchored at a specific record (records/gaad_<type>.html#<id>). Dots are increment-only (none on flat runs); a dot targets the record that took the count to that level, and the final dot of each line is pinned to the newest record of that type.
GAAD now has three peer scenes: GAAD Generator (where design happens), GAAD Navigator (where design is remembered, D134), and the new GAAD Isolator (where one stage is studied on its own). The panel top row switches between them - Generator / Navigator / Isolator - each a single click, none a toggle. Pressing Isolator LINKS the selected Generator stage's objects into the Isolator scene (the same objects and materials, never duplicated, so colour mode stays in sync automatically) and switches there, with its own HUD titled 'Isolator - Stage N'. Isolator is Generator-fed for now; isolating a remembered stage from a Navigator disc via replay is a later pass.
The Backtrack button (F006) now tells the whole arm/confirm flow through its own label and colour. In the Generator, idle, it reads 'Backtrack' with no colour. The first press opens the Navigator and the button turns red, reading 'Select Stage for Backtrack'. Selecting a lineage disc relabels it, still red, to 'Backtrack to String {s} / Gen {g}'. Committing replays the chosen stage and returns to the Generator, where the button is plain 'Backtrack' again.
Each circle on the Navigator lineage array is a Genome: the complete genetic makeup of one remembered design at one generation. The square in the Generator stays a Stage (where design happens, D134). The Backtrack button and prompts name it - 'Select Genome for Backtrack', 'Backtrack to Genome - String {s} / Gen {g}'.
GALF (GAAD Architectural Language Framework) defines the Architectural Language Contract that every GAAD Architectural Language implements. GAAD is the platform; GALF is the contract; PRAL, GRAL, MHAL, FWAL and future languages are implementations. v0.003 agreed 08 Jul 2026 by all three seats: 16 contract sections with requirement levels (Relationships Required; Mission/Identity/Validation never empty); two-axis language status (knowledge_status / platform_status - PRAL is platform-active); typed relationship triples for internal-coherence validation; no tool names in the contract body; every stage file records language, language_version and galf_version; validation layer 3 is the F030 proving run. Resolution Axis remains EXPERIMENTAL pending the FWAL acid test (freeze at v0.004 only if unchanged). MAHL removed as accidental. Contract filed at Spec/GALF_Architectural_Language_Contract_v0_003.md.
GRAL (Garden Room Architectural Language) is recognised as the first Architectural Language built on the GALF contract - no longer just a prototype. Its conformance pass to GALF v0.003 (terminology linkage of platform terms, mandatory status vocabulary mapping) is the template every subsequent language follows.
GALF is owned by the Specification Owner (Claude) and lives in the bundle's Spec/ folder under GAAD file naming: Spec/GAAD_GALF_v0_0X_Architectural_Language_Contract_Specification.md (+ .json mirror). v0.004 is the stewardship version - content is the agreed v0.003 verbatim; only ownership, naming and the Resolution Axis freeze pointer (now v0.005) changed. The externally-named v0.003 files are removed from Spec/ (one authoritative copy, drop discipline); the agreed v0.003 share bundle remains the record of the three-seat agreement (D140).
The bundle gains a top-level Languages/ folder holding the Architectural Language file trios (md/json/html): GAAD_PRAL_v0_001, GAAD_GRAL_v0_021, GAAD_MHAL_v0_003, and future languages (FWAL). Spec/ holds what the platform PROMISES (Lineage, SmokeTest, DL, and the GALF contract per D142); Languages/ holds the implementations that conform to it.
15:21: Validate Scripts (F030) completed its first fully clean run - 18 steps, 0 failures - driving every real operator (Reset, First Generation, breeding, Backtrack arm/select/commit, breed from pivot, Navigator rebuild, three colour flips, Isolator) and validating each against its declared expected outcome. Miles: 'an object of beauty'.
On agreeing GALF v0.003 across all three seats, Miles marked the shift: 'This feels like one of those moments where the project changes direction. GRAL is no longer just a prototype; it's the first Architectural Language built on the GALF contract. That simple decision gives GAAD a foundation for every language that follows.'
Panel command Isolator: shows the selected stage on its own in a dedicated GAAD Isolator scene, a peer of GAAD Generator and GAAD Navigator. The stage's objects are linked (not copied) into the Isolator scene so geometry and materials stay in sync with the Generator; the scene carries its own HUD (Isolator - Stage N). Switched from the panel top row alongside Generator and Navigator - one click, no toggle. Reworked from the original visibility-toggle isolate in addon v0_98 (D137); Generator-fed for now.
Ability to step back or forward through the design lineage - a core feature of the original 1994 GAAD thesis (Fig 3.16, 3.17). In the 1994 algorithm, a Track decision point sits outside the main genetic loop. The user chooses forward or back: Forward track checks if a forward generation exists - if yes, go forward one generation; if no, WARNING: there is no generation forward of this one. Back track checks if a previous generation exists - if yes, go back one generation; if no, WARNING: this is the progenitor, nothing exists before this. Once repositioned, the user re-enters the genetic loop and can grow progeny from that point, creating a new branch. The full genetic path is recorded so pivot progenies are always reachable. The Design Evolution tree is the data structure that makes this possible. Implementing backtrack in Rebirth is a direct test of the revival against the original 1994 system. Depends on seed storage (D030) and is tracked under D045 (backward/forward tracking). ELEVATED 02 Jul 2026: Backtrack is promoted from convenience utility to one of the platform's three core verbs (Evolve / Explore / Backtrack, D110, P047). Rapid Evolution (F022) makes it much more valuable: fearless one-click breeding wants a one-click step-back as its safety net. Candidate companion for the same build when F022 is implemented. NEXT 7 DAYS (Miles, 03 Jul 2026): with EVOLVE shipped as Rapid Stage Select (F022, D119) and the click-click-click loop live at 0.3s per generation (T012 closed, D118), Backtrack is the natural companion - every click is a commitment and evolution needs an undo. Big topic: touches storage (D030 seed reconstruct), the Navigator (F024 fwd+back tree), the D110 grammar (Evolve / Explore / Backtrack) and lineage. Own session, own D### when built. THESIS AUDIT 07 Jul 2026 (Chapter 3 reread, Figs 3.14-3.29): Both Forward and Backward tracking are REPLAY functions - they restore macro phenotypes from genes already stored in the gene bank and never mutate, unlike Forward Search which varies the genes. This maps directly onto D030 (store the recipe, not the cake). Backtrack exists to escape the stated dead-end limitation of Forward Search alone (Fig 3.14): the user backtracks to a PIVOT PROGENY showing greater potential and a new genetic string branches from it (Fig 3.16). Only the current path is recorded as data; dead-end paths stay visible in the tree but are ignored. Unique file naming generation_visitcount_quadrant.CEL keeps revisits distinct (8_3 = 8th generation, 3rd visit; Fig 3.25's worked path alternates forward search and backtracks A-K, including a backtrack right to the progenitor and a fifth genetic string from there). A Right Back button jumps to the progenitor in one step. Genetic Engineering causes a recorded 'break in genetic tree' (Fig 3.18) - a boundary case the Rebirth lineage model must represent. The 4th-dimension framing: time between generations is GAAD's 4th dimension; the user moves forwards and backwards through the design evolution with all design decisions recorded. v0_99: the button self-labels in three states and arms red - 'Backtrack' (idle) -> 'Select Stage for Backtrack' (red, in Navigator) -> 'Backtrack to String {s} / Gen {g}' (red, disc selected) -> commit returns to the Generator as plain 'Backtrack' (D138).
Mitigated in v0.99.06 + gaad_assert: the genome selector and all surface checks are now '.001'-tolerant ('_Surface' in name). Platform fix still open: the tree (or Reset) should sweep stale Lineage_* datablocks so canonical names are never held hostage - the same pattern the v0.90 platform preview applied to Stage_ surfaces.
Fixed in gaad_tree_report_v0_9: build_lineage_flat reads lineage.json and walks the current string's spine back through its pivots to g1 (selected-parent lineage, unselected tip skipped), with the legacy discovery kept as fallback. Spine walk proven in-sandbox on synthetic branched data before delivery. Validate Scripts check message also made truthful (written/MISSING).
On agreeing GALF v0.003 (the Architectural Language Contract) across all three seats, 08 Jul 2026.
Conclusion of the benchmark comparing the agreed GALF contract against NASA/SP-2016-6105 Rev2 and NPR 7123.1 - thirteen of GALF's sixteen sections mapped directly onto NASA SE concepts; GALF's additions (Design Memory, Knowledge Status, Honest Geometry, the language contract itself) have no NASA equivalent. Filed as Spec/GAAD_GALF_v0_01_NASA_SE_Benchmark.