docs: add AUDIT_CHAIN.md wire spec#9
Merged
Conversation
Standalone specification for the SHA-256 hash-chained audit log shared between vyrox-proxy (Rust) and the private worker side (Python). Targets compliance reviewers and customers who want to verify their own audit files independently. Contents: - File layout (one daily JSONL, chain continues across files) - Entry shape for both Rust action entries and Python wrapped entries - Hash computation rules including the canonical-JSON requirement and the | separator on the Rust side - Genesis sentinel value - Reference verifier in about thirty lines of Python that handles both entry shapes and detects tamper / truncation - Chain continuity across process restarts, tied to tests in both implementations - Tamper-detection properties and the truncation mitigation - Durability properties (append-only, fsync after every entry) - Field-stability commitments This unblocks a customer compliance team running an independent SOC 2 evidence verification pipeline against the JSONL export. Cross-refs to ARCHITECTURE.md, THREAT_MODEL.md, and API_REFERENCE.md will resolve once the foundation PR (#8) merges.
This was referenced May 23, 2026
keirsalterego
added a commit
that referenced
this pull request
May 23, 2026
The previous ROADMAP carried ARR targets, pilot counts, quarterly revenue numbers, and an MSP channel percentage. That material moved to vyrox-design-partners/docs/gtm/INTERNAL_ROADMAP_WITH_TARGETS.md in PR #9 of that repo. This commit lands its replacement. The new ROADMAP is organised by capability, not by quarter or by revenue tier. Sections: - Recently shipped: the sixteen blockers from the May 2026 audits (eight P0 + eight P0.5), each described as a public contract change with the file paths a reader can verify. - In flight: items that touch a public contract, with the actual bottleneck called out (Postgres before tenant 25, retry runner not yet wired into worker entrypoint, etc). - Planned, not started: public OpenAPI spec, customer-side audit verifier binary, EU data region, web operator interface trigger conditions. - Adapter coverage: shipped vendors plus on-demand future adapters. - Compliance and certification: where we are honest about what is in flight versus planned versus not started. - Versioning and release cadence: semver intent for the public repos. - "Intentionally not on the roadmap": SIEM, managed human SOC, web dashboard during alpha, free public ingestion endpoint. Cross-refs to ARCHITECTURE.md, API_REFERENCE.md, AUDIT_CHAIN.md, ADAPTERS.md, SECURITY.md resolve after the foundation and specialty PRs (#8, #9, #10, #11) land.
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
1 participant
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.
Summary
Adds
AUDIT_CHAIN.md— the wire-level specification for the SHA-256 hash-chained JSONL audit log shared between the Rust proxy and the private Python worker.Targets compliance reviewers and customers who want to verify their own audit files independently of the platform.
Contents
|separator on the Rust sideWhy
A customer compliance team needs to be able to run an independent verifier against their SOC 2 evidence export. The format had no public spec until this PR.
Depends on / merges after
#8 — foundation rewrite. Cross-refs to
ARCHITECTURE.md,THREAT_MODEL.md,API_REFERENCE.mdresolve once that lands.Test plan