Record the person's data-sharing choice and the legal basis behind each read
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- postgresql, rust
- Área
- backend-api-design, databases
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Rust
- Estrellas
- 2
- Forks
- 0
- Merge medio
- 9 h 48 min
- PR fusionados (30 d)
- 151
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de registrystack/registry-stack
-
area:breg enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
registrystack/registry-stack#2765 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
registrystack/registry-stack#2761 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
registrystack/registry-stack#2743 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
registrystack/registry-stack#2706 ·
Los mantenedores suelen responder en 1 día
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
registrystack/registry-stack#2704 ·
Los mantenedores suelen responder en 1 día
Todos los issues de registrystack/registry-stack
Issues similares
-
[Bug] 建议把黑白主题设置同步到启动页面Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
stackabletech/airflow-operator#898 ·
Los mantenedores suelen responder en 1 día
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Posiblemente ocupada @zyl71 la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100