Establish and exercise the first commit-gated model execution boundary
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 25/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- go
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- Go
- スター
- 309
- フォーク
- 29
- 平均マージ
- 15時間 56分
- マージ済み PR(30日)
- 225
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
stacklok/mecatl のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
docs: make local provider configuration discoverable from mecatui再び着手できるかも @brainsparker が 28 日前に担当しましたが、オープン中のプルリクエストはありません。 オープンdocumentation
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
stacklok/mecatl#2470 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 1 日以内に返信
-
Flake: MCP handshake cancellation can outlive authorization send deadline対応中かも @jbeda が今日担当しました。 オープン
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
メンテナーはふだん 1 日以内に返信
stacklok/mecatl の issue をすべて見る
似ている issue
-
HTTP probe loses insecureSkipVerify in the generated probe manifest対応中かも @BahaaMattar が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 87/100
litmuschaos/litmus#5745 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 2 日以内に返信
-
type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
メンテナーはふだん 1 日以内に返信
-
messaging/v1: IsGRPCProtocol and InternalMetadataToGrpcMetadata panic on empty or nil metadata values対応中かも @patelshivani2283-lab が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
メンテナーはふだん 1 日以内に返信
-
needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
stacklok/toolhive-catalog#2024 ·
メンテナーはふだん 1 日以内に返信