Plan: slices 002, 003, 025 and 026 added - #13
Merged
Merged
Conversation
…025 encryption at rest, 026 store-and-forward receipts Changes 7, 8 and 9 of the 2026-09-20 plan, landed as one branch because all three move the same change-log count. 002 (phase 0, S, depends on 000, counted in M9): a CycloneDX SBOM from the gate and on every release, build provenance attested on release artifacts, one README line for the TLS floor. 003 (phase 0, M, depends on 000, counted in M2): a second gate matrix entry on a UBI9 container with OTP 28.5.0.5 built from source with --enable-fips, FIPS mode entered before crypto loads, a smoke that proves it, and the crypto:supports/1 diff committed; it is where 024's FIPS properties run. 025 (phase 2, M, depends on 010 and 024): the Trinity.Keys custody seam with a local adapter first, envelope encryption for blobs nothing indexes, and the measured dm-crypt baseline for everything SQLite indexes. 026 (phase 2, L, depends on 024): receipt/2 gains a queued-then-acknowledged mode with hybrid logical clocks and Merkle merge; blocked on the external plane's answer, routed through the owner. ROADMAP: rows, the M2 and M9 conditions, the graph, a note that 025 and 026 carry no milestone yet, and the change-log entry deriving 40. One correction to the previous change-log entry: it escaped the pipe inside the deriving command, which plan_check rule 5's pattern does not match, so the rule read the older entry's 36 and passed by coincidence. Both entries now use the bare pipe the rule expects and the rule reads 40. plan_check: PASS (191 tracked files). trinity.names: OK. trinity.reuse: OK. Signed-off-by: Ayla Croft <aylacroft@proton.me>
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.
Changes 7, 8 and 9 of the 2026-09-20 plan. Four new SLICE.md files, ROADMAP rows, milestones, graph and change log. The commit message carries the detail and one correction to rule 5's input.