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

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

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.

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

描述

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.

主要语言
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 摘要。