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

Abierto
#2,707 0 comentarios 0 reacciones 0 asignados Ver en GitHub

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

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 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.

Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
9 h 48 min
PR fusionados (30 d)
151

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de registrystack/registry-stack

Todos los issues de registrystack/registry-stack

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.