Ledger: retention and privacy for turn_ledger

Open
#180 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
electron, typescript

Research direction

Start by locating the turn_ledger implementation and reading how Ledger opening calls verify() and what data each row stores. The issue asks for a retention decision and privacy behavior when chats are deleted, but does not specify the retention period or redaction rules. Done should preserve hashes while removing sensitive bodies, titles, and file paths as appropriate, with verification still working.

Written by the indexing model from the issue text.

Description

area:audit needs-triage p2 type:feature

Part of #117 · found in the independent review of #178.

turn_ledger has no retention and verify() rehashes every row on each Ledger open. Deleting a chat leaves its title and file paths. Decide retention; redact bodies while keeping hashes.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
17h 33m
Merged PRs (30d)
163

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from musterhq/muster-code

All issues in musterhq/muster-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.