Let a person act for someone else: record who acted, for whom, and under what authority
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 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.
- Requests, Proposals, cases and audit entries record the person acting and the person represented in separate fields.
- Authority is checked against a register at the time of the request, or taken from claims in the sign-in token.
- Mandates (who may act for whom, for what, until when) are held as records in a register, with their own evidence and end date.
- Organisation membership can authorise writes, not only reads.
- App Kit shows and switches "acting as", and the person represented can see what was done for them.
- 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分
- マージ済み 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