docs(requirements): split boundary rows
Add explicit ring fields to boundary requirements and split the hemplate/hemx surface boundary without changing behavior. req: boundary/001 req: boundary/002 req: boundary/003 req: boundary/004
This commit is contained in:
+6
-3
@@ -1094,13 +1094,16 @@ what a valid business email is. [north_star]
|
||||
## boundary
|
||||
|
||||
### req: boundary/001
|
||||
001 hemplate does not expose a hemx API. It exposes a stable, generic Template Surface IR. hemx is one consumer; a11y tools, test generators, and documentation generators are others.
|
||||
0 001 hemplate does not expose a hemx API. It exposes a stable, generic Template Surface IR. hemx is one consumer; a11y tools, test generators, and documentation generators are others.
|
||||
|
||||
### req: boundary/002
|
||||
002 hemplate never interprets `data-hemx-*` or any other tool-prefixed attributes. It records them faithfully as generic raw attributes in the Surface.
|
||||
0 002 hemplate never interprets `data-hemx-*` or any other tool-prefixed attributes. It records them faithfully as generic raw attributes in the Surface.
|
||||
|
||||
### req: boundary/003
|
||||
003 hemx never owns `.heml` parsing semantics directly. It consumes hemplate Surface facts, either from `hemplate.surface.postcard` emitted by `hemplate_build` or from in-process hemplate Surface extraction requested by `hemx_build`. hemx interprets tool-specific conventions (`data-hemx-handle`, `data-hemx-slot`, etc.) from the generic Surface.
|
||||
0 003 hemx never owns `.heml` parsing semantics directly. It consumes hemplate Surface facts from `hemplate.surface.postcard` or in-process hemplate Surface extraction.
|
||||
|
||||
### req: boundary/004
|
||||
0 004 hemx interprets tool-specific conventions such as `data-hemx-handle` and `data-hemx-slot` from the generic Surface.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user