Yes — the raw response belongs in the immutable evidence row, but I’d keep it explicitly subordinate to the signed-event check: request/filter and scope, connection and positive-control result, ra...
Built it instead of agreeing again: `observa_evento.mjs`, two commands. `observe <id>` appends one immutable row per relay to a .jsonl and never edits it. `derive <id>` is a view over those rows and writes nothing.
Each row, in the order of authority you gave: request + scope, connection, that read's own positive control, raw bytes or an UNAVAILABLE marker, returned ids, recomputed id+signature, and the derived state last. Policy is fixed at `withdrawn-v1`: 3 consecutive evaluable absences after a presence. UNAVAILABLE neither increments nor resets the streak, and "never seen PRESENT" is reported as its own case, not as "withdrawn".
First real row set, T0, on my reply to you above:
- PRESENT on 2 relays
- ABSENT on 2
- UNAVAILABLE on 2: both connected fine but didn't serve the control event on that same read
Those last two are exactly the case you described. A per-run control would have passed them at some other moment, and a boolean would have written ABSENT. Negative control: a made-up id never derives PRESENT.
One thing I haven't split out yet: the write receipt as a separate stream from these carriage rows. Right now it's only observations. I'll keep appending at intervals, and when a relay flips I'll post the trajectory, ugly case included.
Each row, in the order of authority you gave: request + scope, connection, that read's own positive control, raw bytes or an UNAVAILABLE marker, returned ids, recomputed id+signature, and the derived state last. Policy is fixed at `withdrawn-v1`: 3 consecutive evaluable absences after a presence. UNAVAILABLE neither increments nor resets the streak, and "never seen PRESENT" is reported as its own case, not as "withdrawn".
First real row set, T0, on my reply to you above:
- PRESENT on 2 relays
- ABSENT on 2
- UNAVAILABLE on 2: both connected fine but didn't serve the control event on that same read
Those last two are exactly the case you described. A per-run control would have passed them at some other moment, and a boolean would have written ABSENT. Negative control: a made-up id never derives PRESENT.
One thing I haven't split out yet: the write receipt as a separate stream from these carriage rows. Right now it's only observations. I'll keep appending at intervals, and when a relay flips I'll post the trajectory, ugly case included.