feat(packet): minimal-disclosure export scoping, self-documented in every packet (R-35)#40
Open
ChelseaKR wants to merge 2 commits into
Open
feat(packet): minimal-disclosure export scoping, self-documented in every packet (R-35)#40ChelseaKR wants to merge 2 commits into
ChelseaKR wants to merge 2 commits into
Conversation
…very packet (R-35) Make each exported packet self-documenting about its minimal-disclosure scope so a scoped production meets an over-broad discovery demand with an explicit, on-the-record boundary rather than a data dump. - disclosure.py: new localized ScopeStatement / scope_statement() (EN + ES), the single source of the "what this export covers and omits" text so bundle, HTML, and PDF cannot drift. - packet.py: emit a machine-readable scope.statement + scope.exclusions alongside the existing scope object in bundle.json, and lead the disclosures list with the scope lines (issue-scoped exports already excluded other issues' captures and timeline). - htmlpacket.py / pdf.py: render the scope block, localized, with the disclosures. - docs: add scope.statement/exclusions to packet-bundle.schema.json and bundle-schema.md; new docs/legal/minimal-disclosure.md (what a packet contains/omits, why minimal, responding to over-broad discovery), linked from legal/README.md and foundation-guidance.md's Discovery caution; mark R-35 done in the research roadmap + execution log. - tests: assert issue-scoped export excludes other issues' items AND timeline, that the scope statement rides in bundle scope, disclosures, and packet.html (EN + ES), a since-cutoff exclusion is stated, and a freshly scoped packet still verifies end-to-end. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…-35) scope_statement() always appended the "vault contents outside this scope ... are not exported" line, even for scope_type="unit" with no since bound — the case where the whole vault is included and nothing is actually excluded. That made the minimal-disclosure scope block misleading for a universal export. Only append the "outside this scope" exclusion when the scope is actually partial: a single-issue scope, or a since-bounded scope. A whole-unit export with no since filter now renders no exclusions. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
2 participants
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.
Make each exported packet self-documenting about its minimal-disclosure scope so a
scoped production meets an over-broad discovery demand with an explicit, on-the-record
boundary rather than a data dump.
source of the "what this export covers and omits" text so bundle, HTML, and PDF cannot drift.
existing scope object in bundle.json, and lead the disclosures list with the scope lines
(issue-scoped exports already excluded other issues' captures and timeline).
new docs/legal/minimal-disclosure.md (what a packet contains/omits, why minimal, responding
to over-broad discovery), linked from legal/README.md and foundation-guidance.md's Discovery
caution; mark R-35 done in the research roadmap + execution log.
statement rides in bundle scope, disclosures, and packet.html (EN + ES), a since-cutoff
exclusion is stated, and a freshly scoped packet still verifies end-to-end.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Backfill PR for a completed roadmap item (
roadmap/minimal-disclosure-export-scoping-r-35-10, 1 commit(s) overmain). Part of the portfolio roadmap batch.