OSS-Singularity/zcode-dispatch-observatory
OSS-Singularity/zcode-dispatch-observatory
Watch
1
0
Fork
You've already forked zcode-dispatch-observatory
 0
Code Issues Pull requests Projects Releases 137 Packages Wiki Activity Actions

Pinky ZZZZ: the retry-timestamp truth (v1.109.0, #62 EIL) #144

Merged
ClaudiuSchuster merged 1 commit from oss-oo/pinky-zzzz-retrytime into main 2026-10-24 20:50:40 +00:00
Conversation 0 Commits 1 Files changed 17 +825 -63
ClaudiuSchuster commented 2026-10-24 20:48:31 +00:00
Owner

Retry preserves the originäres sent_ms by construction (id-embedded root + ordinal; retry-of-retry keeps the ROOT); .retry.json lineage sidecar; both times on receipts and in the deck; 11 discriminating legs; sibling sweep.

Retry preserves the originäres sent_ms by construction (id-embedded root + ordinal; retry-of-retry keeps the ROOT); .retry.json lineage sidecar; both times on receipts and in the deck; 11 discriminating legs; sibling sweep.
Pinky ZZZZ: the retry-timestamp truth (owner finding #62, EIL: Diagnose-Vergiftung) — the STEER-RETRY button used to mint the fresh steer id at the RETRY moment, and the id's embedded send-ms is what every consumer trusts (queue FIFO, receipt sentMs, the delivered annotation's child-id parse): backlogged steers read YOUNGER than they were and the master's timeline got poisoned; the cure preserves the original sent_ms by construction (the retry id embeds the ORIGINAL send with an honest ordinal {orig-ms}-{n}-{sid}; retry-of-retry keeps the ROOT; the queue position follows the same law), gives the retry moment its OWN field everywhere (.retry.json lineage sidecar {retryOf, sentMs, retryMs, retryCount} + payload + the settled record's retryMs with the file's own birth preserved across the settle write), surfaces both times on the receipt (sentMs stays the ORIGINAL; retryMs/retryOf/retryCount join it), renders both in the deck's voice (gesendet: X beside Zustellung: Y · N. Versuch — retry fired Z, plus the honest toast), carries the original send through the dispatcher's ZCODE_DISPATCH_STEER_SENT_MS env seam, refuses an overwritten mint BY NAME at the product gate (proven red on a scratch-copy reintroduction — 11 discriminating legs — and green on the cure, with the honest negative pinning the retry's record/receipt diff to EXACTLY the settle keys), extends the attribution globs to retry-shaped prompt files (root-preferred on ties), and sweeps every sibling re-fire path (verdicts in the README) (v1.109.0)
All checks were successful
Checks / Functional checks (pull_request) Successful in 49s
Details Explain this check
859643bfb8
ClaudiuSchuster deleted branch oss-oo/pinky-zzzz-retrytime 2026-10-24 20:50:40 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
OSS-Singularity/zcode-dispatch-observatory!144
No description provided.