festipod

Files

T

Sylvain Duchesne e62a17e5a2 docs(data-layer): correct the graph-round-trip claim (it was the bloat hang)

The lib e2e harness proves that on the current broker an anchored
INSERT DATA { GRAPH <plainNuri> {…} } DOES round-trip — the earlier 'explicit GRAPH
writes a phantom named graph the read never sees' claim was false; the '0 entity'
symptom was actually the wallet-bloat hang (caveat_wallet-bloat-hang), not a graph
mismatch. Reframe the no-GRAPH default-graph rule as a simplicity/safety convention,
not a round-trip necessity. Lib/app inline comments asserting the phantom-graph
claim remain to reconcile.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-06 23:56:51 +02:00

_overview.md

feat(data): union read model — list via anchorless sparql_query, hang eliminated

2026-07-05 20:49:01 +02:00

brief_2026-07-06_reactive-reads-and-attendance.md

feat(data): reactive cross-session reads (doc_subscribe), + real 2-browser e2e

2026-07-06 23:40:43 +02:00

caveat_event-fields-not-persisted.md

doctrine: Festipod treats @ng-eventually/client as a finished NextGraph SDK

2026-07-03 23:23:23 +02:00

caveat_participation-deletion.md

doctrine: Festipod treats @ng-eventually/client as a finished NextGraph SDK