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

feat(local): decide local stays app territory

Browse Source 
Define local/offline truth as commands, domain events, and projections rather than stored DOM patches or EffectBatch payloads; wire the techdemo through a local command-to-projection-to-effect flow; document that hemx-local is not a crate until reusable semantics are proven.

req: local/001

req: local/002

req: local/003

req: local/004

req: examples/001
This commit is contained in:
slhx agent
2026-06-11 19:52:21 +02:00
parent 64a736ffcb
commit 1ec68d400c
3 changed files with 18 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
REQUIREMENTS.md
+1 -1
View File
@@ -578,7 +578,7 @@ what a valid business email is.
001 Local/offline behavior is represented as app commands, domain events, and projections. Stored DOM patches or stored EffectBatch payloads are not the source of truth.
### req: local/002
002 Local command logs are app or integration territory until a reusable hemx contract proves common semantics across multiple apps. hemx core must not gain a mandatory browser database, client store, sync engine, or conflict policy.
002 Local command logs are app or integration territory until a reusable hemx contract proves common semantics across multiple apps; `hemx-local` is not a crate yet. hemx core must not gain a mandatory browser database, client store, sync engine, or conflict policy.
### req: local/003
003 Replaying local work back to a server or peer sync target is explicit app/integration policy. A local projection may render immediate feedback, but server acceptance, rejection, reconciliation, export, and deletion rules remain visible product decisions.