Overview
| Comment: | Publish the vocabulary on quarry.evt.<repo>.<noun>.<action>
RFC 0005 picked zit.evt., which the fold consumer already claims with a trailing wildcard — every vocabulary event would have been handed to the artifact parser. Own stream, own root, tests pinning both. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
3bca39d8f540c05c4c2e84c8ba578f7d |
| User & Date: | dmestas on 2026-08-24 16:27:03.248 |
| Other Links: | manifest | tags |
Context
|
2026-08-24
| ||
| 16:27 | Add the new event-plane files the previous commit omitted check-in: f485551646 user: dmestas tags: trunk | |
| 16:27 |
Publish the vocabulary on quarry.evt.<repo>.<noun>.<action>
RFC 0005 picked zit.evt., which the fold consumer already claims with a trailing wildcard — every vocabulary event would have been handed to the artifact parser. Own stream, own root, tests pinning both. check-in: 3bca39d8f5 user: dmestas tags: trunk | |
| 15:57 |
RFC 0005: dagnats already has the triggers; correct the record
I probed HTTP and concluded dagnats had no scheduler. Wrong lens — triggers are NATS and KV native. It has cron, subject, webhook, durable HTTP, worker-contributed kinds and debounce. So quarry builds none of that: it owes well-named subjects, and the vocabulary IS the hierarchy. check-in: 3aef7f3211 user: dmestas tags: trunk | |
Changes
Modified cmd/quarry/main.go
from [6fdfd8975f]
to [3a93884fbf].
[diff]
Modified docs/rfcs/0005-event-vocabulary.md
from [0621e4b0a6]
to [2cf146b226].
[diff]
Modified internal/api/register.go
from [c3754a5694]
to [f1c87c5414].
[diff]
Modified internal/events/events.go
from [0e859f8301]
to [3a43d3cc6f].
[diff]
Modified internal/evt/evt.go
from [60b5f63bd5]
to [0b847e562b].
[diff]
Modified internal/evt/evt_test.go
from [4e29fe6383]
to [fa16760f5d].
[diff]