Let a person act for someone else: record who acted, for whom, and under what authority

Abierto
#2,708 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
postgresql, rust

Línea de trabajo

Start by reading the linked issues #44, #49, #1389, #1766, #2532, and #2707, then trace how the Rust services represent token claims, requests, proposals, cases, and audit entries. The issue asks for design decisions about delegated authority and representation; no implementation entry point or tests are named. Done means the required representation types, authority checks, and lifecycle questions have a settled design before 1.0.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

Many public services are used by someone acting for another person: a household member applying for the household, a parent for a child, a legal representative or appointed agent, or staff completing an application with the person present. Registry Stack has no general way to record or check this. A request records one person, the signed-in one, so a service either refuses these cases or records the wrong person as the applicant.

Current state

  • Tokens may carry an act (actor) claim. Today it is used for AI agents acting through the MCP edge.
  • Evidence can issue a credential to a representative, with a subject and holder that differ (#562).
  • Earlier proposals were closed until an adopter needed them: #49 and #44 (OAuth delegation profiles) and #1389 (derive consent representation from relationships held in the register).
  • #2532 (open) covers delegated personal-data reads for MCP clients.
  • App Kit has no "acting for" state in the session.

Decisions that are hard to change later

These shape stored data, audit records and token contracts. They should be settled before 1.0, even if the full feature comes later.

  1. Requests, Proposals, cases and audit entries record the person acting and the person represented in separate fields.
  2. Authority is checked against a register at the time of the request, or taken from claims in the sign-in token.
  3. Mandates (who may act for whom, for what, until when) are held as records in a register, with their own evidence and end date.
  4. Organisation membership can authorise writes, not only reads.
  5. App Kit shows and switches "acting as", and the person represented can see what was done for them.
  6. A representative may, or may not, read the person's access log (#1766) and record their data-sharing choice (#2707).

Kinds of representation

  • household member for the household
  • parent or guardian for a child
  • legal representative or appointed agent
  • staff completing a request with or for the person
  • staff of an organisation acting for the organisation

Other questions

  • Which kinds are needed first?
  • Is authority checked only at submit, or again when a decision is made or a change applied?
  • What happens to an open request when a mandate ends?
  • Who is told about each step: the representative, the person represented, or both?
  • How does the person represented find out, and object?

Out of scope

OAuth delegation profiles as such (#44, #49) unless the design needs them, AI agent delegation (covered by the MCP work), and mandates recognised across borders.

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.