Establish authoritative SessionGroup membership and session catalog lifecycle

Aperta
#2,903 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go

Direzione di ricerca

Start by reviewing the linked contracts in #2761, #2760, #2665, #2669, #2670, #2671 and #2672, then trace the existing Go session and history creation, publication, lookup and activation paths. Define the catalog authority, persistence and failure model before implementing; the issue requires review before implementation and deterministic tests at the storage and activation boundaries. Done means membership, publication and tombstones remain authoritative across interruptions, deletion, restart and owner changes, with delegation behavior qualified against #2671.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Outcome

An authoritative catalog records SessionGroup identity, permanent Session/history membership, session existence/publication, and logical deletion independently of whether history bytes already exist. Deletion and retained references cannot re-enable execution/access or permit identity reuse.

Parent: #2666, under #2659. This carries catalog and lifecycle obligations moved out of #2761's bounded group-lease contract and two-history memory proof. #2761 supplies ownership/fencing primitives, not catalog authority.

Scope

  • Define and implement authoritative group/session creation, member registration, publication, lookup and logical deletion. A group may be empty and has no intrinsically distinguished root member.
  • Assign each Session/history permanently to one group. Register new members under the correct group authority; do not implement cross-group migration. Distinguish membership from initialized history, loaded runtimes, principal authorization and execution authority.
  • Review the catalog/manifest persistence and creation/publication ordering contract, including interruptions before any accepted history exists. A backend index or routing table is not a competing catalog.
  • Specify deletion tombstones/identity retirement, activation/access checks and cleanup without claiming immediate physical purge. Session and group identities are not reused or silently reassigned.
  • Coordinate delegation lifecycle policy with #2671: where a parent/root deletion must disable owned delegated work, enforce that policy consistently without assuming every group member is a child or that deleting any member deletes its peers. Retained history/environment references cannot resurrect disabled or expired resources.

Acceptance

  • Catalog and membership authority, storage schema, failure model, access/execution boundaries and Go/stored/wire compatibility are reviewed before implementation.
  • Creation/member publication interrupted before, during and after first-history acceptance produces explicit reconcilable states, without duplicate identity or an independently activatable orphan.
  • Concurrent registration/activation and stale-owner operations cannot assign a member to two groups, bypass the group lease or reinterpret absent history as absent membership.
  • Logical deletion prevents prohibited activation/access and ID reuse even before history creation, after runtime eviction, and after restart or owner change; cleanup is distinct from deletion authority.
  • Delegation deletion/cancellation integration is qualified with #2671, including stale child advancement and direct API Team creation where applicable. SessionGroup itself has no required root.
  • Deterministic tests exercise actual catalog/storage and activation boundaries with isolated state, plus bounded handling of corruption/uncertainty. Residual deployment qualification is explicitly assigned.

Dependencies and boundaries

Coordinate #2761 leases/fencing, #2760 durable history, #2665 interrupted recovery, #2669 shared controls, #2670 authorization/provenance, #2671 delegation and #2672 final cutover qualification. Reuse accepted history identities without importing the legacy Session aggregate or treating diagnostic InstanceID as authority.

No automatic cross-owner private-output replay, cross-group migration, implicit cross-history transaction, production cutover, physical purge promise or schema/API break is authorized by filing this issue. Preserve the existing separation between principal access and execution leasing.

Lingua principale
Go
Stelle
309
Fork
29
Merge medio
15h 56m
PR unite (30g)
225

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di stacklok/mecatl

Tutte le issue di stacklok/mecatl

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.