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

Isolate template authoring validation

Browse Source
This commit is contained in:
tmk241
2026-09-01 23:14:12 +02:00
parent 5b29100340
commit 42710354a6
6 changed files with 388 additions and 307 deletions
Download Patch File Download Diff File Expand all files Collapse all files
INTENT.tsv
+2
View File
@@ -5,3 +5,5 @@ protocol/001 Ad hoc browser commands create ambiguous ordering and compatibility
web/001 Framework abstractions often replace native web semantics unnecessarily People using Hemx applications Retain semantic HTML, accessibility, URLs, forms, and browser fallback
portable/001 Host-only parsing dependencies prevent portable server-side rendering Rust applications targeting Wasm and constrained servers Render through normal Hemx APIs without host parser dependencies
scope/001 Universal extension systems turn a small interaction layer into a client framework Maintainers and application authors Compose ordinary behavior from a small kernel, direct adapters, and explicit islands
maintainability/001 Build and adapter responsibilities are interleaved, making safe changes costly Hemx maintainers and downstream users relying on stable generated contracts Cohesive private ownership seams preserve behavior, diagnostics, and portability
assurance/001 Boundary changes can pass broad suites without focused semantic drift checks Maintainers changing generated APIs, handlers, adapters, and browser runtime Focused checks expose contract and integration drift at the owning seam
1 ID PROBLEM FOR OUTCOME
5 web/001 Framework abstractions often replace native web semantics unnecessarily People using Hemx applications Retain semantic HTML, accessibility, URLs, forms, and browser fallback
6 portable/001 Host-only parsing dependencies prevent portable server-side rendering Rust applications targeting Wasm and constrained servers Render through normal Hemx APIs without host parser dependencies
7 scope/001 Universal extension systems turn a small interaction layer into a client framework Maintainers and application authors Compose ordinary behavior from a small kernel, direct adapters, and explicit islands
8 maintainability/001 Build and adapter responsibilities are interleaved, making safe changes costly Hemx maintainers and downstream users relying on stable generated contracts Cohesive private ownership seams preserve behavior, diagnostics, and portability
9 assurance/001 Boundary changes can pass broad suites without focused semantic drift checks Maintainers changing generated APIs, handlers, adapters, and browser runtime Focused checks expose contract and integration drift at the owning seam