Repository navigation
Prepare provider execution and qualify Scheme runtime - #3
Merged
Merged
Conversation
Reuse immutable execution inputs and SDK prepared programs while preserving fresh deciding reads, current authority, source barriers and retained holds. Carry publication-bound Governor topology and bounded facts through the existing affine owner and rooted C ABI; validate owned candidate indices. Specialize wholly nested retained programs with the public ASCENT factory. Add fixed four-worker benchmarks and SDK GC attribution, with preparation, queue, derivation, reply and natural cleanup measured separately. Keep retained/preopen/packed modes opt-in and preserve the original deadlines. The submillisecond target remains unqualified: the latest candidate owner P99 is 3.419-3.605 ms. Both four-way source-readiness waves failed before Governor derivation. Record passing local controls and these open gates in the delivery plan; this checkpoint makes no full CI or production claim.
Version the source, Kubernetes fixture, acceptance controls and SysML allocation. Keep generated run outputs in the local verification cache. Final Scheme release qualification remains pending after the prepared SDK was removed.
The four-thread ledger library suite and cargo fmt pass. The full feature Clippy hook still requires the prepared Scheme SDK.
Prepare trusted TOML profiles, own browser and device credentials, and bind delegated OAuth exchange to the existing mTLS operation and signed grant boundaries. Qualify lifecycle and transport behavior through bounded fixtures, Rust properties, SysML traceability and Quint models.
Keep the strict ASP gate enabled by separating RPC handlers, listener lifecycle, and the source-owner worker. Move the ingress test into its unit fixture and retain SysML trace witnesses at their new locations.
Exercise cached OAuth and connection reuse through four concurrent prepared-profile callers. Verify cancellation through the same configuration entrypoint, bind the SysML witnesses, and register the existing Criterion case and Server dependency in the workspace gates.
Set TCP_NODELAY on the accepted fixture socket and retain the original five-second workload limit. Include the active protocol phase in timeout errors so Ubuntu failures identify which boundary stalled.
Reuse Cargo release artifacts for the provider and observation fixtures while retaining the Scheme qualification graph. Preserve all property cases, race checks, and the ten-minute integration budget, and trace the selection in SysML.
Remove the generic five-minute Cargo preparation cutoff that truncates optimized builds. Keep the enclosing suite deadline and native runtime acceptance timeout, and verify descendant cleanup for both preparation stages under parent cancellation.
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.
Provider execution repeats preparation across ledger transactions and Scheme Workflow wakes. This PR prepares reusable execution objects and fixed SQL programs, while keeping fresh authority/source reads and claim, reservation, fence, revocation and unknown-outcome checks in Rust's deciding transactions.
Scheme/POO and gerbil-ascent retain planning and inference. The existing affine owner now supports publication-bound topology, complete bounded fact transfer and checked node-index results over the rooted C ABI. The retained nested candidate uses ASCENT's public program constructor to reduce 24 relations/21 rules to 21/14, preserving source inputs, fact limits and atomic replacement. Retained, preopen and packed execution remain opt-in.
The maintained benchmarks include four-worker HTTPS Snake Oil paths and a finite quiet resident-owner profile. The latter uses one prepared owner, four Tokio workers and 32 waves of four complete snapshots. SDK usage counters distinguish GC time, heap capacity and whole-process counters. Generated execution evidence stays in ignored cache directories; reproducible drivers, model witnesses and acceptance limits are versioned.
Validation and open gates:
See
docs/50-59-research-program/59-provider-rpc/59.87-spec-upgrade-and-delivery-plan.organd the linked SysML requirements for current behavior, finite evidence and remaining gates. Further performance work is deferred for architecture review. Keep this PR Draft; no merge or release is requested.