hemx/INTENT.tsv

1	ID	PROBLEM	FOR	OUTCOME
2	server/001	Browser frameworks duplicate authoritative application state and policy	Rust teams building ordinary server-owned web applications	Keep state, authorization, validation, and recovery on the server
3	resource/001	Copied selectors and protocol identifiers drift away from rendered templates	Template and handler authors	Use generated typed resources and actions for every interaction boundary
4	protocol/001	Ad hoc browser commands create ambiguous ordering and compatibility	Framework adapters and browser runtimes	Apply one deterministic ordered effect protocol within an owned root
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