Technical diary

D102 newadoptedArchitectureDecision01 Jul 2026

GAAD Design Language (DL) is the master architecture; panel is a view; JSON is source of truth

The GAAD Design Language becomes the authoritative architectural model from which all Design Languages (PAL, GRAL, MAL, HAL) inherit. The DL defines the data model, not the Blender interface. The Blender Panel is a presentation layer onto the DL and is not required to expose every DL field or share its structure. JSON remains the single source of truth; documentation, reports and interfaces are derived from it. The DL comprises eleven sections (Metadata/Identity, Philosophy, People, Place, Experience, Objects, Parameters, Relationships, Evolution Rules, Evaluation Criteria, Initial State), with human-centred sections optional so a thin language such as PAL validates without inventing content. The Project Design Record is a SEPARATE, linked record type (record_type 'design_record'), because the Language is stable while the Record grows. Two owner-level corrections were made to the coordinated response: (1) Seed is a run control belonging to the Design Record, not a DL section, so it maps to no DL section; (2) Getting Started is derived help generated from Metadata and Philosophy, not the storage location of Metadata. Issued as GAAD DL v0.03 for peer review; GRAL becomes the first reference implementation to validate the spec before v1.00.

D103 newadoptedProcessDecision01 Jul 2026

Freeze DL v0.03 for the duration of GRAL (anti-churn)

GAAD DL v0.03 is frozen as the baseline specification for the entire duration of GRAL v0.01. GRAL is implemented against v0.03 exactly as peer-reviewed and approved, with no specification changes mid-implementation. The five peer-review recommendations (required-but-empty human-centred sections; unknown-key validation as warning within a reserved namespace; a Terminology section referencing gaad_terminology.json; a shared GAAD Principles record; and an explicit idea-to-standard lifecycle) are logged and parked as the v0.04 agenda, to be applied after GRAL and informed by it. Anything GRAL surfaces that appears to need a spec change is added to the v0.04 backlog rather than reopening v0.03. The freeze may only be broken by a genuine blocker where GRAL cannot proceed, and only as a deliberate, logged exception.

D104 newadoptedProcessDecision01 Jul 2026

DL v0.03 specification filed into the bundle under Claude's ownership

The GAAD Design Language Specification v0.03 (owner: Claude, Specification Owner per P045) is filed into the versioned bundle in Spec/, as both the authoritative .docx and a hyphen-clean .md reference extraction, alongside the frozen panel mock-up v1_0. This stops the frozen GRAL baseline (D103) from living only in chat history. The bundle carrying it is named GAAD Development 0_103 to avoid confusion with the separately-scoped 0_102 task list. Authoring the DL as gaad_design_language.json in the house record style (so it obeys JSON -> MD -> HTML like every other record) remains outstanding and is developed alongside GRAL v0.01, not in isolation.

P044 ArchitectureMoment01 Jul 2026

The Design Language becomes GAAD's master architecture

Ownership of GAAD DL was handed to Claude, and the Design Language was established as the authoritative architectural model - a stable, JSON-defined data model that every Design Language (PAL, GRAL, MAL, HAL) inherits from, with the Blender Panel demoted to a view onto it. Issued as DL v0.03 for peer review, with GRAL set as the first reference implementation.

P045 GovernanceMoment01 Jul 2026

The three-role model crystallises

The GAAD working team settled into three complementary roles: Miles Walker as Chief Architect ('Is this where GAAD should go?'), Claude as Specification Owner ('Is this internally consistent, technically correct and maintainable?'), and ChatGPT as Architecture Reviewer ('Does this strengthen the architecture, and what might it mean in the future?'). Captured as gaad_team_roles for the future governance section of the Charter.

F016 parked-for-v0.04Design LanguageFeature01 Jul 2026

DL v0.04: required-but-empty human-centred sections

Change People/Place/Experience from optional to required keys that must be present but may be explicitly null with a stated reason (e.g. PAL: applicable=false, reason='abstract primitive language'). Reinforces 'Understand People Before Geometry' while keeping honest validation. Owner refinement of peer-review recommendation 1.

F017 parked-for-v0.04Design LanguageFeature01 Jul 2026

DL v0.04: unknown-key validation as warning within a reserved namespace

Downgrade unknown-key validation from error to warning ONLY within a reserved namespace (e.g. x_ prefix or an 'experimental' block); unknown keys elsewhere remain an error. Allows controlled evolution without losing the no-silent-private-extensions guarantee. Owner refinement of peer-review recommendation 2.

F018 parked-for-v0.04Design LanguageFeature01 Jul 2026

DL v0.04: Terminology section referencing gaad_terminology.json

Add a Terminology section to the DL spec that references the existing gaad_terminology.json record and adds only DL-specific terms, rather than duplicating vocabulary. Peer-review recommendation 3.

F019 parked-for-v0.04Design LanguageFeature01 Jul 2026

Shared GAAD Principles record cited by all specs

Create a standalone gaad_principles record (JSON + doc) holding the shared principles (Understand People Before Geometry; Decisions become data; Structured knowledge before learning; platform vs language) that every future GAAD specification references from one source. Peer-review recommendation 4.

F020 parked-for-v0.04Design LanguageFeature01 Jul 2026

Document the idea-to-standard specification lifecycle

State explicitly the lifecycle a GAAD specification follows: idea -> draft -> peer review -> reference implementation (validation) -> standard (v1.00). Make it a shared convention future specs follow. Peer-review recommendation 5.

T007 highclosedConsistencyTicket01 Jul 2026

Scene rename to 'GAAD Navigator' is only half-applied across addon and README

Closed as not-a-defect after in-Blender verification: both scenes read correctly ('GAAD Generator' and 'GAAD Navigator'), and the addon's live scene references and HUD use 'GAAD Navigator' consistently. The 'Design Evolution' occurrences that prompted this ticket were changelog header comments (historical, correct to keep) plus two minor cosmetic UI-text leftovers (an operator label and a tooltip) and a stale README HUD line - not scene-name defects. Any residual cosmetic-text tidy can be handled separately if desired.