scheduling: let a person book, move and cancel their own appointments without a task grant

Abierto
#2,729 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
Bien especificado
Estado de actividad
Activo
Stack tecnológico
openapi, postgresql, rust

Línea de trabajo

Start with crates/registry-scheduling/src/store.rs, especially the is_managed_by behavior cited in the issue, and read the linked task grants documentation to understand the current authority model. Then trace the scheduling paths and PostgreSQL suite for booking, rescheduling, cancellation, caps, and managed appointments. Done means both authority paths meet the acceptance criteria, existing suites pass, scoped reads work, and the security page, OpenAPI document, clients, and CLI catalogue are updated.

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

Descripción

area:scheduling criticality:p2 enhancement triage:needs-implementation

Use case

Public-facing services need people to book for themselves with their own sign-in: registration appointments, exam sittings, clinics, information sessions, and activities with limited places. Today a person cannot book directly. Every commitment takes its authority from a task grant alone, and a trusted producer such as Casework mints those grants.

Current evidence

  • Task grants: "Every commitment takes its authority from the grant alone."
  • is_managed_by: a retained source manager replaces the creating actor. When an appointment has a manager, its owner can no longer act on it.

Proposed behaviour

  • A self-service commitment profile. A person's own verified token may hold, book, reschedule and cancel for themselves, within the exact service, location and action permissions the profile declares. No task grant is involved, and the task-grant path is unchanged.
  • The party is always the token subject. This path never books for someone else.
  • A cap per person: at most one active booking per person per window, and a configurable ceiling on active holds and bookings per person per offering. Hold lifetimes stay bounded, so one person cannot park capacity.
  • An appointment may also retain an institutional manager. The owner and that manager may both act on it, and nobody else may.
  • Eligibility stays with the service's source of record. Scheduling does not decide it.

Acceptance criteria

  • A person's token books, reschedules and cancels its own appointment under the profile.
  • The profile refuses, with distinct problem codes, a request for another party, a request outside the declared permissions, and a request above the cap.
  • Concurrent requests from one person cannot exceed the cap (PostgreSQL suite).
  • Task-grant bookings behave as before, and the existing suites pass unchanged.
  • On a managed self-service appointment, the owner and the retained manager can both cancel, and a third principal cannot.
  • Self-service appointments are reachable through scoped operational reads (#2337), so the notification journey proven in #2339 can find whom to notify.
  • The Scheduling security page records the second authority path, its abuse controls and its residuals. The OpenAPI document, clients and CLI catalogue are regenerated.

Delivery

Implemented in one PR with the displacement issue that follows this one, because once people own their bookings an institution needs a way to clear them when supply goes.

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.