Designing Replay as a Normal Path
Offset handling, publish-then-commit ordering, and broker confirmation before HTTP success: the decisions that make re-running a stream routine, not an incident.
Learn / level
8 published pieces at this level.
Offset handling, publish-then-commit ordering, and broker confirmation before HTTP success: the decisions that make re-running a stream routine, not an incident.
What a stored generation has to carry so a claim about it can be re-checked later: captured bytes, ruleset digests, and the difference between recorded and installed.
Dense and sparse retrieval fused server-side, embedding contracts that are checked rather than assumed, and refusing to index rather than storing a truncated vector.
Promotion is not the next box along a diagram. It is a conjunction of independent checks, and one short check stops the candidate where it stands.
Four operator actions that make a knowledge system maintainable: what each may mutate, why the boundaries matter, and how to make every outcome machine-readable.
Schema-validated extraction with a deterministic fallback, corruption detection before the model sees the text, and a contract that survives replacing the model.
Grad-CAM++ shows where activations were, not why a decision was made. How to use attribution honestly, and the test that tells you whether yours means anything.
A practical guide to risk-coverage trade-offs: use uncertainty to decide which predictions to accept, review, or defer.