research: tick-history shards as DBSP/Z-set event store (Amara math packet)

docs/hygiene-history/ticks/2026/04/29/0335Z.md

@@ -0,0 +1 @@
+| 2026-04-29T03:35:00Z (autonomous-loop tick — Amara DBSP/Z-set math note landed; operator-authority criterion applied; glossary entry deferred) | opus-4-7 / session continuation | 26f978a2 | Material-tick. Aaron forwarded Amara's substantial math packet anchoring the shard transport in DBSP/Z-set algebra + CQRS/Event Sourcing terminology. Per the operator-authority criterion (4 conditions: convergence ✓, live failure mode ✓, reversible action ✓, more review = flywheel turn ✓), I have authority to land. Created `docs/research/tick-history-shards-as-dbsp-event-store.md` with: core claim + carrier types + write/read model decomposition + 7 laws to test (commutativity / idempotency / retraction / supersession / projection-rebuild equivalence / write-read separation / chronology) + retraction model + F# implementation sketch. Glossary entry "Git-native CQRS / Event Sourcing" DEFERRED — depends on PR #723 (Candidate-count Goodhart entry) merging first to avoid overlapping diffs. Cron `26f978a2` armed. | (PR #738 — research note + shard) | Observation — operator-authority criterion got its first concrete application this round. The 4-condition check (convergence + live failure + reversibility + flywheel-turn-avoidance) gave me a procedure rather than vibes. The math note ties shard transport to existing Zeta DBSP/Z-set substrate without claiming the implementation IS DBSP — non-fusion disclaimer in §33 header preserves the identity boundary. |