Establish and exercise the first commit-gated model execution boundary

Abierto
#2,891 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
go

Línea de trabajo

Start by reviewing parent issue #2664 and prerequisite #2761, then inspect the existing session/history, modelrequest, and execution-boundary contracts mentioned in this issue. Review ownership, identity, input/output lifetimes, failure handling, and ordering before choosing package placement or adding consumers. Done means the deterministic offline interaction passes through the real isolated kernel and composition, with acceptance, invocation admission, submission ownership, and retained facts covered at that boundary.

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

Descripción

Parent: #2664.

Outcome

One deterministic model interaction executes through the actual isolated kernel, establishing the first reviewed boundary between session state, coordination, and execution.

Scope and contracts

Reuse existing session/history and provider-neutral modelrequest contracts. Settle only the responsibility split and execution seam needed for this interaction: request construction and accepted commitment, final invocation admission, completed response capture, and submission ownership. Keep accepted commitment distinct from final invocation authorization or proof of sending.

Before implementation, review proposed ownership, dependencies, identity/correlation, detached input/output lifetimes, failure handling, and ordering. Review new or materially changed public contracts before adding their consumers. Choose package placement in that review, preserving the passive packages' responsibilities and inward dependency direction; this issue does not prescribe a package layout or a general executor API.

Acceptance
  • An offline deterministic executor receives a request constructed through the existing modelrequest path; its completed response becomes accepted session history through the real composition.
  • Rejected or uncertain prerequisite acceptance prevents invocation and accepted-state advancement; executor counts provide a negative control. Completed outcomes do not authorize downstream work before required acceptance.
  • Final execution admission is explicit and distinct from accepted commitment; request identity alone grants no invocation authority.
  • Submission ownership preserves one unresolved append batch per history. A retry of uncertain acceptance retains the original proposal identity and does not repeat external execution.
  • Inputs and completed outputs have explicit ownership; mutation or reuse by an executor cannot silently alter retained facts.
  • The introduced contracts receive coherent review before consumers, are documented beside their owning code, and are exercised at the actual execution boundary.
Dependencies and exclusions

Prerequisite: #2761 supplies SessionGroup lease contracts, supervised local admission and the fixed two-history in-memory atomic-fencing proof. Reuse those reviewed contracts rather than create a competing ownership mechanism. It does not require waiting for catalog lifecycle #2903 or concrete deployment provider #2904; neither this model interaction nor the memory proof qualifies distributed execution.

Builds on completed #2663, including #2793 and #2841; reuse existing usage accounting for any reports this slice receives rather than inventing another accounting path. It does not qualify all failure/retry usage capture.

No tools, general scheduler, production entry-point changes, provider SDK machinery inside passive kernel packages, streaming-delta persistence, production governance integration, or full interruption recovery. Basic acceptance safety is required here, not deferred to a later child. Cancellation/storage-wait stress qualification is a later slice, not permission to bake in contradictory ordering contracts.

Lenguaje dominante
Go
Estrellas
309
Forks
29
Merge medio
15 h 56 min
PR fusionados (30 d)
225

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 stacklok/mecatl

Todos los issues de stacklok/mecatl

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.