Writing archive

API schema changes are not only field changes. Separate source contracts from product meaning, preserve evidence, and evolve mappings without spreading breakage.

A Rust future is Send only when every stored state is safe to move across threads. Trace captures and locals across await to fix spawn errors.

A synchronization run rarely fails as one clean unit. Define progress, safe retries, checkpoints, and recovery so partial success becomes an ordinary state.

Zero-copy scanning still reads every inspected byte. It removes a second materialization in memory. I use streaming Aho-Corasick to explain automaton state, chunk boundaries, DFA dependency chains, prefilters, and honest performance measurement.

A system-boundary model showing why useful AI products still depend on identity, freshness, permissions, schemas, replay, and observable data flows.