docs: record the 5A page-boundary bug, and assess SFM as a tool

Two things Brian asked for after the BE12599 work.

The known bug: the 5A walk discards the key's page byte, so once a unit has
recorded more than 64 KB since its last erase, an event spanning the boundary
reads an end_offset behind its own start. The chunk loop then fetches nothing
and TERM packs a negative offset_word, which is the 500. Reproduced on BE12599.
It hid this long because every capture the walk was verified against came from
a freshly-erased BE11529 — all three confirmed TERM examples sit inside page
0x11. Prod is unaffected; it ingests complete files and never runs this walk.

The status doc exists because "is SFM reliable?" has three different answers
depending on which tier is meant. The codec library and the data side are
production — verified per-sample at scale, carrying Terra-View daily. The
device side is emergency-grade: it works, but it is synchronous,
unauthenticated, and thinly tested. The lab is research artifacts. Most
confusion comes from answering for the wrong tier.

It covers all three of what Brian asked for: maturity per capability, an
operator-facing "what to use when" (the cheap probes are cheap and the event
walk is not), the known-issues table, and the gap analysis. That gap is mostly
auth, async and guardrails — not protocol work. The protocol is the finished
part.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qcu9ByJfuKBQxmrWb8rSrN

This commit is contained in:

serversdown

2026-09-20 01:30:14 +00:00

co-authored by

Claude Opus 5

parent 6589da445b

commit f1ab5b1e9d

3 changed files with 173 additions and 0 deletions

									
										README.md
									
		+5
		
												View File
												
				@@ -496,6 +496,11 @@ Use **com0com** or **VSPD** to create the virtual COM pair on Windows.

				## Roadmap (Future)

				> **Where it stands *today*** — an honest per-capability maturity assessment,

				> what to rely on, known issues, and the gap to a real tool:

				> [`docs/sfm_tool_status.md`](docs/sfm_tool_status.md).  This section covers

				> where it is *going*.

				### Strategic direction — where this is going

				seismo-relay is being built as a **suite of cooperating components**