| Comment: | Count clones and fetches
A clone reads and writes nothing, so it is the one kind of forge activity that leaves no trace in the DAG at all. The sync edge classifies the protocol's cards: clone SEQNO 1 opens a new clone, later rounds do not, so a big store cloned in forty rounds still counts once. Two sinks: the vocabulary event for anything reacting, and a JetStream counter for how many, which converges across nodes instead of losing increments to a read-modify-write. |
|---|---|
| Timelines: | family | ancestors | descendants | both | clone-counts |
| Files: | files | file ages | folders |
| SHA3-256: |
dc058fa551ad914a1c90ceafadfcb7e5 |
| User & Date: | dmestas on 2026-08-24 19:16:15.688 |
| Other Links: | branch diff | manifest | tags |
|
2026-08-24
| ||
| 19:16 | RFC 0005: state what the clone counters count closed check-in: c83148c71d user: dmestas tags: clone-counts | |
| 19:16 |
Count clones and fetches
A clone reads and writes nothing, so it is the one kind of forge activity that leaves no trace in the DAG at all. The sync edge classifies the protocol's cards: clone SEQNO 1 opens a new clone, later rounds do not, so a big store cloned in forty rounds still counts once. Two sinks: the vocabulary event for anything reacting, and a JetStream counter for how many, which converges across nodes instead of losing increments to a read-modify-write. check-in: dc058fa551 user: dmestas tags: clone-counts | |
| 18:08 |
Suite green across 29 packages; merges clean.
Four commits: the fan-out onto the vocabulary, per-subscription event selection, the settings surface, and the RFC correction that preceded them. check-in: 69fc3f06d1 user: dmestas tags: trunk | |