docs(format): RAR5/UDF/Deflate64 feasibility ADR [RM-306]#64
Merged
P4suta merged 2 commits intoJul 23, 2026
Merged
Conversation
ADR-0013 resolves the RAR5, UDF, and Deflate64 feasibility questions that RM-300 and ADR-0012 delegated to RM-306. It is a feasibility-and-scope decision that lands no provider; support-matrix cells still flip only when a provider is implemented. - Deflate64 (method 9): read = go via the external pure-Rust `deflate64` decoder behind the codec-provider boundary (follow-on slice); write = won't-do (no pure-Rust encoder exists). Supersedes ADR-0012's "Deflate64 (read + write)" deficit with a write-only won't-do row. - UDF: go for a scoped read-only in-tree pure-Rust provider (Phase 1: rev 1.02/1.50/2.01, activated from the shared Volume Recognition Sequence); write/VAT/sparable/2.50-2.60 metadata partitions out of scope. Generic RAND boilerplate recorded as a low-but-nonzero tracked IP risk. - RAR5: legally defensible as an independent read-only decoder, but the provider is deferred in its entirety — no clean-room forbid(unsafe) pure-Rust decompressor exists, C-UnRAR FFI is disqualified by the portable profile, and a metadata+Stored-only cut would read almost no real archive. Decode-only / clean-room / nominative-naming constraints fixed for any future work. Updates docs/support-matrix.md (deficit ledger + not-yet-implemented prose) and docs/tracking/campaign-3-evidence.md. No src/ change, no dependency added. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
P4suta
enabled auto-merge (squash)
July 23, 2026 03:31
P4suta
deleted the
feature/dev-112-rm-306-rar5-and-udf-feasibility-resolution-and-scope-adr
branch
July 23, 2026 03:45
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.
RM-306 / DEV-112 — RAR5 and UDF feasibility resolution and scope ADR
Feasibility-and-scope decision (ADR-0013) resolving the RAR5, UDF, and Deflate64 questions that RM-300 and ADR-0012 delegated to RM-306. No provider lands with this ADR; support-matrix cells still flip only when a provider is implemented.
Decisions
deflate64decoder consumed behind the codec-provider boundary (C-free portable profile,#![forbid(unsafe_code)], bounded 64 KiB window), landing in a follow-on slice; write = won't-do (no pure-Rust encoder exists, demand nil). Supersedes ADR-0012's "Deflate64 (read + write)" deficit with a write-only won't-do row.forbid(unsafe)pure-Rust decompressor exists, C-UnRAR FFI is disqualified by the portable profile, and a metadata+Stored-only cut would read almost no real archive. Decode-only / clean-room / nominative-naming constraints fixed for any future work.Changes
docs/adr/0013-rar5-udf-deflate64-feasibility.md(new)docs/support-matrix.md— deficit ledger + not-yet-implemented prosedocs/tracking/campaign-3-evidence.md— RM-306 evidenceNo
src/change, no dependency added.just cipassed locally (pre-push gate).🤖 Generated with Claude Code