Record the person's data-sharing choice and the legal basis behind each read

未关闭
#2,707 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
postgresql, rust

调研方向

Start by reading the consent and access-log issues (#1375, #1766, #1768), the acting-for-someone-else issue (#1389), and configure/breg-consent.mdx plus spec/rs-dm-manifest.mdx. The issue lists unresolved product and data-model decisions across consent, legal basis, audit logging, and App Kit. Done requires those decisions to be made and the resulting scope defined; no implementation files or tests are specified.

由索引模型根据 Issue 内容生成。

描述

Problem

Online services often ask a person to let the service use their details from other government registers, or tell them that the law allows it. Today that choice or notice lives only in the service's own front end. Nothing in Registry Stack records which notice was shown, what the person decided, or which purpose and legal basis the service relied on, and nothing links later reads to that decision. A service can promise "you can see who has used your data" without any product backing the promise.

Current state

  • Consent-gated reads (#1375) and the consent module (configure/breg-consent.mdx). Consent applies to whole records, not individual fields, and there is no pending-request state.
  • The person's access log (#1766) records requester, client and purpose. It has no legal basis, only the person can read it, and some read paths are not covered (#1768).
  • Purpose is set by requiredPurposes on BReg access profiles and per assertion in Evidence, which also records the grant's authority kind (statutory, consent or delegated).
  • The Manifest declares legal-basis and consent gates, but no product checks them (spec/rs-dm-manifest.mdx).
  • App Kit has no "who used my data" page and no consent step that saves a record.
  • PublicSchema models ConsentRecord and legal_basis.

Questions to decide

  1. Does the person's decision live in the source register, the service's register, or a dedicated consent register?
  2. When a read rests on a statutory basis, do we store an acknowledgement that the notice was shown, or only record the basis on each access?
  3. Is legal basis set on the access profile, on the grant, or both? Does it appear in the access log and in the Evidence audit?
  4. Does App Kit provide a consent step that saves the decision, and a "who used my data" page?
  5. When a person withdraws consent, what stops, and from when?
  6. How is a representative's choice recorded? This depends on how acting for someone else is designed (see #1389, closed as not planned until a concrete adopter).
  7. Can an officer list the access log for a person, under what grant, and is that listing itself logged?

Out of scope

Representation itself, data subject requests beyond the access log, a person identifier shared across registers, and wallet receipts.

主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。