Refactor code

Author: johnsamuelwrites

README.md

@@ -2,7 +2,7 @@
 
 Automaginarium is a configurable universe generator for cellular automata. It extends the spirit of [Cellcosmos](https://github.com/multilingualprogramming/cellcosmos): instead of exploring only the 256 elementary Wolfram rules, it opens the rule space itself.
 
-The project is designed to demonstrate the expressive power of the Multilingual programming language. The canonical automata concepts are written in French Multilingual source, while JavaScript is kept as a thin browser layer for loading presets and JSON, drawing to canvas, generating optional rule tables, wiring the preset gallery, and handling only the essential interface events.
+The project is designed to demonstrate the expressive power of the Multilingual programming language. The canonical automata concepts are written in French Multilingual source, while JavaScript is kept as a thin browser layer for loading presets and JSON, drawing to canvas, wiring the preset gallery, synchronizing form controls, and handling only the essential interface events.
 
 ## Vision
 
@@ -33,6 +33,7 @@ The repository currently includes:
 
 - a canonical French Multilingual core in `src/automate_universel.ml`
 - a small JavaScript adapter in `public/automate-core.js` that mirrors the current core until the Multilingual/WASM build pipeline is wired
+- canonical rule-table generators, form/config helpers, genetic helpers, and perturbation mutations exposed through the core bridge instead of separate browser-only engine modules
 - a canvas UI in `public/app.mjs`
 - copied Cellcosmos heritage references in `public/metrics.js` and `src/cellcosmos_primitives_heritage.ml`
 - example configurations and a JSON schema in `examples/`
@@ -119,4 +120,4 @@ Where source code is directly adapted, comments identify Cellcosmos as the origi
 4. Add more generated rule spaces: totalistic, symmetric, genetic, stochastic, and multi-channel examples.
 
 ## Architecture et Création
-- John Samuel
+- John Samuel

docs/architecture.md

@@ -11,12 +11,16 @@ public/app.mjs               essential DOM events, canvas drawing, preset loadin
 
 The intended stable boundary is the configuration object. The UI should not know Wolfram-specific details except where it offers a preset shortcut.
 
-The browser layer is intentionally narrow: one module applies configuration objects, delegates evolution to the core bridge, renders the resulting universe, and wires a static preset gallery. Presentation-only concerns such as tab systems, mirrored form state, and client-side gallery choreography are not part of the long-term architecture.
+The browser layer is intentionally narrow: one module reads and writes form controls, delegates configuration assembly, evolution, canonical rule-table generation, genetic evaluation, and perturbation mutations to the core bridge, renders the resulting universe, and wires a static preset gallery. Presentation-only concerns such as tab systems, mirrored form state, and client-side gallery choreography are not part of the long-term architecture.
+
+Advanced tools such as the genetic workbench and perturbation toolkit are now lazy browser features. They are loaded only when their panels are opened, so the baseline application path stays focused on the core Multilingual configuration and rendering loop.
 
 Canonical JSON-array rule keys use forms such as `"[0,1,0]"`, rather than concatenated keys such as `"010"`. The browser adapter still accepts older Cellcosmos-style keys as a compatibility fallback.
 
 The packed Multilingual/WASM bridge keeps the full French core as the canonical configuration and evolution model, while `src/automate_packed_wasm.ml` exposes a narrow numeric ABI for browser calls. The browser prefers `window.AutomaginariumPacked` when available and falls back to JavaScript only where rich JSON orchestration is still needed.
 
+Rule-table generation follows the same pattern: canonical helpers live in `src/automate_universel.ml`, narrow deterministic numeric helpers live in `src/automate_packed_wasm.ml`, and `public/automate-core.js` exposes the browser bridge so `public/app.mjs` does not duplicate the rule logic, form-to-config assembly, or configuration summaries.
+
 ## Reuse From Cellcosmos
 
 Directly reusable ideas: