tmk241/hemx
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(requirements): split canonical API scaling rule

Browse Source 
Split oversized canonical_authoring/006 into generated-shape, normal authoring surfaces, and escape-hatch boundary requirements.

req: canonical_authoring/006

req: canonical_authoring/012

req: canonical_authoring/013
This commit is contained in:
slhx agent
2026-06-25 14:05:36 +02:00
parent 89878b424a
commit 89dbc3f0f4
2 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
REQUIREMENTS.md
+7 -1
View File
@@ -74,7 +74,13 @@ client app state framework.
009 Generated helpers must not combine persistence, routing, rendering, target selection, or domain policy into generic commands such as `refresh`, `save_and_update`, `sync_component`, or `rerender`. [north_star]
### req: canonical/006
006 There is no separate beginner API and expert API. The simple generated shape is canonical and should scale: generated slots, partials, forms, class constants, islands/events, and page helpers are normal. Explicit primitives, raw targets, raw HTML, raw effects, manual registries/form parsing, low-level ids/opcodes, wire formats, and raw routes remain named escape hatches or internals around the same render/target/effect/transport model. [north_star]
006 There is no separate beginner API and expert API; the simple generated shape is canonical. [north_star]
### req: canonical/012
012 Generated slots, partials, forms, class constants, islands/events, and page helpers are normal authoring surfaces. [north_star]
### req: canonical/013
013 Explicit primitives, raw targets, raw HTML, raw effects, manual registries/form parsing, low-level ids/opcodes, wire formats, and raw routes remain named escape hatches or internals around the same render/target/effect/transport model. [north_star]
### req: canonical/007
007 Opaque islands are explicit leaf adapters: templates declare `data-hemx-island` and optional generated handles/events; server code may emit snapshots/events such as `ui::game.emit(event)`, while island JS owns only high-frequency local behavior. Islands do not introduce a component runtime, client state graph, VDOM, or second UI model. [north_star]