Establish and exercise the first commit-gated model execution boundary
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
- Área
- ai-infra-agents, backend
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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de stacklok/mecatl
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
docs: make local provider configuration discoverable from mecatuiQuizá libre de nuevo @brainsparker la tomó hace 28 días y no hay ningún pull request abierto. Abiertodocumentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
stacklok/mecatl#2470 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
Flake: MCP handshake cancellation can outlive authorization send deadlinePosiblemente ocupada @jbeda la tomó hoy. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
Todos los issues de stacklok/mecatl
Issues similares
-
HTTP probe loses insecureSkipVerify in the generated probe manifestPosiblemente ocupada @BahaaMattar la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 87/100
litmuschaos/litmus#5745 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 2 días
-
type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
Los mantenedores suelen responder en 1 día
-
messaging/v1: IsGRPCProtocol and InternalMetadataToGrpcMetadata panic on empty or nil metadata valuesPosiblemente ocupada @patelshivani2283-lab la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
stacklok/toolhive-catalog#2024 ·
Los mantenedores suelen responder en 1 día