docs(dynamic-tools-v1): compatibility contract + reserved streaming extension — #92 - #97
Merged
Merged
Conversation
…xtension — #92 Make the consumer contract explicit so integrations build reliably, versioned and update-capable: - Compatibility = protocol version (dynamic-tools-v1) + a pinned binary SHA-256, verified by the startup health handshake. Binary semver is informative. - Update rule: swap a newer binary answering the same protocol id + re-verify; no in-place self-updater. - Breaking changes only via -v2 or a strictly additive field; SHA-256 integrity only (signed provenance out of scope); interop surfaces (OpenAI/MCP) are separate consumer projects, not the core. - Streaming reserved as an additive extension (opt-in stream:true + conversation.delta), so a later interactive consumer needs no -v2. v1 stays non-streaming. Epic #94.
This was referenced Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Schließt #92 (Epic #94): macht den
dynamic-tools-v1-Kompatibilitätsvertrag explizit — die Grundlage, auf die jeder Konsument (HA, künftiger OpenAI-Gateway, weitere Integrationen) „verlässlich, versioniert, updatefähig" baut.Was hinzukommt (rein Doku,
docs/proposals/dynamic-tools-v1.md)-v2oder rein additiv. SHA-256-Integrität (keine signierte Provenance). Interop-Oberflächen (OpenAI/MCP) sind separate Konsumenten-Projekte, nicht der Core.conversation.result); ein späterer opt-instream:true+conversation.delta-Frame ist additiv (kein-v2) — damit ein interaktiver Konsument keine Sackgasse ist.Verifiziert
Der Health-Frame im Doc (
status:"ready") stimmt mit der Runtime überein (agent_main.h:234).Nebenbefund (Cross-Repo, separat)
Die App-Repo-Fixture
geist-home-assistant/protocol/dynamic-tools-v1.jsonverlangt"status":"ok", die Runtime sendet aber"ready". Das sollte im App-Repo abgeglichen werden (die Runtime + dieser Vertrag sind autoritativ mit"ready") — nicht Teil dieses PRs.Epic #94 · Issue #92