feat: self-model, paper alignment notes, Mermaid architecture, marimo notebook#150
Merged
rororowyourboat merged 7 commits intomainfrom Mar 28, 2026
Merged
feat: self-model, paper alignment notes, Mermaid architecture, marimo notebook#150rororowyourboat merged 7 commits intomainfrom
rororowyourboat merged 7 commits intomainfrom
Conversation
added 7 commits
March 28, 2026 20:10
Mathematical audit against Zargham & Shorish (2022) via NotebookLM identified 3 framework inventions vs paper definitions: 1. Composition algebra (Def 1.1): categorical structure is a framework design choice, not mandated by the paper's h(x) = f(x, g(x)) 2. U_x decomposition (Property 4.5): paper defines U: X -> P(U) as a single map; struct/behav split is an ontological engineering choice 3. StateMetric split: paper's d_X is a single metric (Assumption 3.2); variable declarations (R1) vs distance callable (R3) is framework Also noted: Rice's theorem R3 boundary applies to the implementation scope (arbitrary Python callables), not the paper's mathematical scope (compact/convex/continuous constraint sets per Assumption 3.5). Canonical decomposition h = f ∘ g (Def 1.4) confirmed as faithful to paper Definitions 2.6-2.9.
Dog-fooding: the GDS monorepo modeled as a component diagram using its own gds-software package. 9 components (packages), 4 interfaces (GDSSpec, SimAPI, ODEAPI, ControlAPI), 8 connectors. Canonical result: h = g (stateless — pure API composition). Providers (framework, sim, continuous) become BoundaryActions; consumers (DSLs, analysis, symbolic) become Policies. No state, no mechanisms. 8 tests verifying compilation, canonical decomposition, verification, and Mermaid output.
Three views of the GDS ecosystem modeled using its own DSLs: Component diagram (prior commit): package dependencies as h = g (stateless API composition) DFD pipeline: user workflow from spec→compile→verify→export→simulate→ analyze as h = f ∘ g (full dynamical system with 4 data stores) ERD data model: Pydantic model graph (GDSSpec→Block→Interface→Port, Entity→StateVariable→TypeDef, SpecWiring→Wire) as h = f (pure state, 9 relationships, 20 state variables)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan
mkdocs build --strictpasses