Request evidence can keep pace with the evidence it corroborates - #4
Merged
Conversation
By-default request evidence demanded a deletion clock. After 0.2.0
flipped core evidence to keep-indefinitely, that meant the
corroboration — the IP, the client, the place that cement a recorded
act to a person when the dispute is "that wasn't me" — was scheduled to
expire before the agreement it corroborates. A scheduled weakening of
the record is not a privacy feature.
keep_recorded_{ip_addresses,browser_user_agents,ip_geolocation}_indefinitely!(because:)
is the third answer to "how long", said out loud with a reason like
every escape hatch here. A clock and keep-indefinitely together are
refused as opposite decisions; keeping forever silently remains
impossible.
The README's request-evidence section now argues FOR recording, with
the on-by-default posture as the recommendation — discipline unchanged:
per-field decisions, written purposes, encryption, reviewed proxy
provenance.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013A6ZmfmFuQ2z3GyvQCuECA
Three more places demanded a deletion clock for recorded request
evidence and knew nothing of the new declaration: the per-policy
reference validator, the policy-level setting validator, and the
capture-time extractor that stamps the annex schedule. All three now
accept the third answer — an indefinite annex rule in the retention
class (new keep_recorded_{ip_address,browser_user_agent,ip_geolocation}_indefinitely
builder verbs) or the application-wide
keep_recorded_..._indefinitely!(because:) — and their error messages
name all the options. Precedence is unchanged and more-specific wins:
policy clock, then class rule, then the application-wide declaration.
An indefinite annex stamps no schedule; the planner reports it
unresolved-by-decision and never lists it, pinned at a 100-year
horizon through a real capture.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013A6ZmfmFuQ2z3GyvQCuECA
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.
IP + user agent + geolocation are what cement a recorded act to a person — an agreement dispute is usually "that wasn't me", and the core event alone answers the wrong question. Two changes:
keep_recorded_{ip_addresses,browser_user_agents,ip_geolocation}_indefinitely!(because:). By-default request evidence used to require a deletion clock, which after 0.2.0 scheduled the corroboration to expire before the evidence it corroborates. Keeping forever is now declarable — out loud, with a reason, never silently. Clock + keep-indefinitely together is refused as opposite decisions.800 runs / 5254 assertions green, rubocop clean.
🤖 Generated with Claude Code
https://claude.ai/code/session_013A6ZmfmFuQ2z3GyvQCuECA