Repository navigation
Enforce original-task authority through routing, Turso and final provider delivery - #1
Merged
Merged
Conversation
GTrunSec
marked this pull request as ready for review
October 30, 2026 15:11
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
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.
Weaver keeps every LLM operation bound to its original task, profile, claim and shared budget/history domains from authenticated Go publication through MRR Data/Turso consumption and Rust's actual provider write and final gRPC delivery. Routing proposes a target; current Cedar authorization and durable original consumption constrain its use.
Go owns configuration, authenticated gRPC, routing proposals and source-publication orchestration. Rust owns Cedar evaluation, atomic consumption, fencing and final effects. Scheme retains its upstream Governor/Governance allocation; runtime reintegration remains paused.
Runtime enforcement
Source-led design and validation
Agentgateway's serialized endpoint publication, Go push coalescing and Rust ADS/body paths, the locked Tonic encoder, and Cargo-owned MRR/Turso sources informed the change. Weaver adopts immutable bounded publication and coalesces notification demand; it does not drop Policy intents or use a bare Arc load as final authorization. No new runtime framework, storage engine, queue capacity or dependency revision is introduced.
Measured performance boundary
Every complete paired MVCC run accounts for all 13,312 frames: 128 streams per arm, four concurrent streams, 13 one-row Protobuf frames, shared/disjoint roots and injected/no-injection cohorts. Both arms use one immutable optimized image per run. Four grouped preparations remain four; native final-queue transactions fall from 13 to four. Payloads, provider-call counts, queue capacity, original holds and latency targets remain unchanged.
The final image's shared no-injection control/snapshot throughput is 29.48/43.39 streams/s, and whole-stream P99 is 202.6/147.8 ms. Across all four final cohorts throughput improves 1.37–1.65 times. Snapshot final owner-turn P99 is 14.25–17.08 us. Native commit sums are per stream, not transaction quantiles; independent percentiles are never added.
The complete path does not qualify for sub-millisecond latency. Shared acknowledgment-to-Tonic P99 remains 10.380–22.224 ms; final disjoint no-injection Rust-queue-to-Go P99 is 4.498 ms. Shared injected acknowledgment, shared renewal-bin tails and disjoint Tonic-to-Go have regressions. The observed injected pressure is 2.561/3.680 CPU equivalents, not six occupied cores. Other jobs appeared around sampling, so final-image low-background qualification remains open. Earlier lower-background attempts, all regressions and the before/after scheduling counterexample are retained; no sample, deadline or safety constraint is discarded.
English Org, SysML, Lean, Quint and generated D2/SVG are synchronized. Raw logs and failed evidence stay in ignored cache. External dependency pins remain unchanged; Scheme reintegration is paused. No additional PR or storage backend is introduced, and the separate response-window candidate remains unpromoted.
See the source-led snapshot design and complete results, writer mediation and core delivery view.