Update framework spec; add counter and todo examples

This commit is contained in:
Will Anderson
2026-04-29 08:50:26 -05:00
parent ef841d8a01
commit 2b2ca8a59e
3 changed files with 7 additions and 5 deletions
+1
View File
@@ -0,0 +1 @@
../../dist/el-ui.js
+1
View File
@@ -0,0 +1 @@
../../dist/el-ui.js
+5 -5
View File
@@ -59,7 +59,7 @@ When a node is updated, its importance increases by 0.1 (capped at 1.0). Recentl
## 2. Component Definition Syntax
Components are defined in `.el` files (the same extension as engram-lang source). A component is a specialized engram-lang module.
Components are defined in `.el` files (the same extension as el source). A component is a specialized el module.
### 2.1 Structure
@@ -508,7 +508,7 @@ el-ui-compiler App.el # produces App.js
## 9. Production Build — Quantum-Sealed via engram-crypto
The production build pipeline follows the engram-lang sealed artifact format:
The production build pipeline follows the el sealed artifact format:
```bash
# 1. Compile .el to .js
@@ -518,7 +518,7 @@ el-ui-compiler App.el -o app.js --target prod
ENGRAM_SEAL_KEY=my-deploy-key el seal app.js -o app.sealed
```
The sealed artifact is an `ENGRAM01` sealed bundle (same format as the engram-lang production target):
The sealed artifact is an `ENGRAM01` sealed bundle (same format as the el production target):
```
Offset Size Field
@@ -565,9 +565,9 @@ el-ui follows semantic versioning.
---
## 12. Relationship to engram-lang
## 12. Relationship to el
el-ui `.el` files share the `.el` extension with engram-lang source files. Components are specialized engram-lang modules — in a future version, an `.el` file can mix component definitions with engram-lang type definitions, constants, and utility functions in a single compilation unit.
el-ui `.el` files share the `.el` extension with el source files. Components are specialized el modules — in a future version, an `.el` file can mix component definitions with el type definitions, constants, and utility functions in a single compilation unit.
The spreading activation algorithm in `graph.js` and `activation.js` faithfully mirrors `engram-core/src/activation.rs`:
- Same BFS-based traversal