| Comment: | RFC 0005: one named event stream, three consumers
Events are noun.action, subscribed by name. Fossil has no such vocabulary — its hooks are artifact-level and its alerts are eight letters — so the delivery semantics come from its warning that a distributed system cannot promise exactly-once. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
dc2bb819a315aeb1d9ca2bd57b60c48a |
| User & Date: | dmestas on 2026-08-24 13:11:09.708 |
| Other Links: | manifest | tags |
|
2026-08-24
| ||
| 15:36 |
RFC 0005: verified the bus, added schedules and dispatch
The stream is a one-hour window, so events split: DAG-derived ones are re-derivable after a gap, operational ones need OLTP backing. A cron run and an ad-hoc run are not events — three trigger sources, and schedules take fossil's 'a' so a repo admin owns their own. check-in: 60206e85b2 user: dmestas tags: trunk | |
| 13:11 |
RFC 0005: one named event stream, three consumers
Events are noun.action, subscribed by name. Fossil has no such vocabulary — its hooks are artifact-level and its alerts are eight letters — so the delivery semantics come from its warning that a distributed system cannot promise exactly-once. check-in: dc2bb819a3 user: dmestas tags: trunk | |
| 12:28 | merge timing-wall into trunk check-in: 952100a76b user: dmestas tags: trunk | |