Rows are kept in the order they were written. That is not always the order things happened. The times are stored but never sorted on, so a fill found by a later check with the venue goes in at the end, behind events that came after it.
What is refused
An event of a kind the spine does not know is refused outright rather than written down.
A repeated fill is refused too, and that refusal is ordinary.
What is written before what
A fill is written down before it is acted on, and only an accepted one is used to update the running pictures.
Sending an order is written down around the act. The intention to send goes in before the venue is asked. What became of it goes in after: the venue's answer where that could be read, or a note of failure where the failure was one of the kinds looked for.
A reply broken in a way none of those kinds covers escapes both, and only a line in the log marks it. The intention stands in the record with nothing beside it, which is what leaves such a send readable afterwards as a send attempted with no result recorded.
One writer at a time
Only one writer at a time may read the last row, add the next with its codes, and save — so two writers sharing one spine cannot both add a row after the same last one. Two separate spines, or two programs on the same file, are not held apart by that lock.
Related
Source evidence
---
row: P2-17
baseline: 49aa659
created: 2026-09-26 08:12 UTC
modified: 2026-11-09 13:36 UTC
evidence:
- claim: "Each event kept carries its epoch, time, kind and contents"
source: "`event_spine.py` 123-131"
- claim: "Rows go in as they are written, with no sorting or checking of the times"
source: "`event_spine.py` 1165-1172, the order coming from the key at 124"
- claim: "A kind the record does not know is refused rather than kept"
source: "`event_spine.py` 1158-1161"
- claim: "A fill already written for the same epoch, account, pair and venue's own name for the trade is refused, and nothing is written for it"
source: "`event_spine.py` 1022-1023"
- claim: "A fill is offered here before it is projected"
source: "`execution_manager.py` 4328-4330"
- claim: "A send writes down the intention before the venue is asked"
source: "`execution_manager.py` 4264-4265, ahead of the call at 4268-4272"
- claim: "An answer that could be read is written down after"
source: "`execution_manager.py` 4301-4308, then 4309"
- claim: "A failure of a kind looked for is written down instead"
source: "reached at `execution_manager.py` 4296-4299, delegated at 5420-5422, answered at 5424, built and appended at 5457-5465, applied at 5466"
- claim: "A reply malformed past what is looked for escapes both and leaves only a line in the log"
source: "raised at `binance_adapter.py` 940, caught by none of the alternatives — either `execution_manager.py` 4282, or 4292, or 4296 — and logged at 4012-4019"
- claim: "One lock serves the writers sharing one spine object, and belongs to that object alone"
source: "`event_spine.py` 456 making it on the object, taken at 947-948"
- claim: "It is held through the writing, the sealing and the commit"
source: "`event_spine.py` 1125-1126 inside the lock taken at 947-948, the sealing at 1165-1176"
---