Record the person's data-sharing choice and the legal basis behind each read
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 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
requiredPurposeson 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
ConsentRecordandlegal_basis.
Questions to decide
- Does the person's decision live in the source register, the service's register, or a dedicated consent register?
- 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?
- 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?
- Does App Kit provide a consent step that saves the decision, and a "who used my data" page?
- When a person withdraws consent, what stops, and from when?
- 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).
- 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分
- マージ済み PR(30日)
- 151
環境構築
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
registrystack/registry-stack のほかの issue
-
area:breg enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
registrystack/registry-stack#2765 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
registrystack/registry-stack#2761 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
registrystack/registry-stack#2743 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
registrystack/registry-stack#2706 ·
メンテナーはふだん 1 日以内に返信
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
registrystack/registry-stack#2704 ·
メンテナーはふだん 1 日以内に返信
registrystack/registry-stack の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 75/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 82/100
stackabletech/airflow-operator#898 ·
メンテナーはふだん 1 日以内に返信
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)対応中かも @zyl71 が今日担当しました。 オープン
難易度 1/5 1時間未満 初心者へのやさしさ 88/100