What it does
The engine library defines a documented, versioned JSON-lines export of log records, each with a SHA-256 of its canonical encoding, and a standalone reader that depends on no storage code. It is a library feature that no route or command calls today.
How it works
The first line is a self-describing header with the format id, the version and a description of the record schema. Each following line is one log record with a digest of its own canonical form. A reader needs a JSON parser and SHA-256 and nothing else, and rejects any other format id or an out-of-window version rather than guessing. A content digest over the records lets a replay into a fresh log be compared with the original.
A format registry records, for each persisted format, the version the engine writes, the window of older versions it reads and which versions have existed; tests check that the registry matches what the log code accepts.
Where you reach it
- Library
kynetra_core::wal_export: export_to_path, clean_room_read, content_digest (engine library, not wired to the server)
Limits
- Not reachable from the server or the command line. The kynetra replay command reads records from a data directory and is a separate feature.
- Encrypted logs cannot be exported through the clean-room path without their keys.
Evidence
- TestsCovered in the engine repository by format-evolution tests, including a clean-room export that is read back and replayed into a fresh log and compared by content digest
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
This is not available in the preview. Request a preview to discuss the current scope.