Datary 0.2.0: corrective audit release - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
I treated the critique as a release blocker and followed Datary's evidence path from raw input through parsing, analysis, integrity checks, reports, package builds, and the release artefacts.
Oh! The most important correction is mathematical: order-dependent metrics now preserve observation order. The session trust boundary rejects symlinks before resolution, malformed evidence is hashed, overwrite publication is recoverable, and recording/inspection analysis is disk-backed instead of accumulating every record in memory.
The ingestion, quality, comparison, plotting, replay, reporting, generator, privacy, packaging, and CI boundaries received the same corrective pass. The README and 0.2.0 notes explain both how the project works and what this alpha still does not claim.
Verification
Release status
This is intentionally an alpha prerelease. Checksums detect accidental corruption; they do not authenticate authorship. Unit conversion, explicit comparison resampling, signed sessions, and very-large-plot downsampling remain documented limitations.