Skip to content

Preserve provider admission and qualify native Scheme governance - #3

Draft
GTrunSec wants to merge 99 commits into
mainfrom
perf/provider-lifecycle-footprints
Draft

GTrunSec wants to merge 99 commits into
mainfrom
perf/provider-lifecycle-footprints

Conversation

@GTrunSec

@GTrunSec GTrunSec commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

Provider admission must retain complete budget, claim and authority custody while compatible work shares the execution path. Rust selects the exclusive writer turn and rechecks domain discovery before its native Turso transaction; accepted authority changes, settlement and unknown outcomes retain their barriers and reservations. Go releases bootstrap-only source connections after known static activation.

Native Scheme governance uses the existing SDK Build Packages/C ABI on a tracked owner. Authenticated source compilation, durable source versions and intent prefixes, and Scheme/POO Governor derivation remain bound to the ledger frontier, claims and reservation transactions. SysML allocates the lifecycle and workflow acceptance to their existing native entrypoints.

CI uses independent Ubuntu suites and retains the enabled macOS Scheme job. Go is selected through official Go 1.27.3 tooling; source preparation starts with four workers. Full dependency cold preparation is observed separately, without the retired installation cutoff. Target selection (120 seconds), native cold build (eight minutes), recovery (12 seconds) and natural exit (15 seconds) keep their original limits. The SDK combines module, linker and startup C objects in its existing bounded compilation pool; Cargo uses its default target directory and line-table debug information.

Validation and remaining gates:

  • At 3988eeff, all five non-Scheme Ubuntu suites and the complete macOS Scheme suite passed. Linux Scheme selection passed in 46 seconds, native cold build in 6m14s and native Go/gRPC integration in 4m26s. Only the Linux Rust governance_owner qualification failed with SIGPIPE.
  • The bounded GDB run reproduced the same path: a Tokio TLS worker was inside writev while the Scheme owner was inside Gambit cleanup. The process-wide SIGPIPE reset escaped the existing owner-local mask. The independent Go consumer had passed and no earlier Rust panic was reported.
  • SDK 9aa4de6 passed all seven Ubuntu checks, including the concurrent SIGPIPE control and its negative case, the real external Arrow round trip, and actor AOT and Rust concurrency qualification. Linux prepares a private paired Gambit archive with separate members and scopes the signal binding to cleanup. Weaver 6dbcd4fd pins this SDK in Cargo and the setup action, and records the cleanup boundary in SysML. Local locked resolution, architecture tests and workflow lint passed. At 6dbcd4fd, all six Ubuntu suites passed. Linux selected targets in 48.23 seconds and cold-built in 6m13.74s, with four workers compiling 466 C objects in 2m10.82s. The rooted SDK owner and Go/gRPC recovery passed. On macOS, the selection passed in 100.55 seconds, while the 8-minute cold-build deadline interrupted the C batch. The receipt shows three native workers and a batch start at 5m53.93s. Weaver baseline CI. SDK PR #18 · SDK CI
  • 144923a8 invokes weaver-dev bootstrap-scheme to call the native Gerbil package manager and publish the same receipt locally and in CI. It removes shell timing, receipt probes and the temporary automatic debugger step. The existing architecture tests and local entrypoint controls passed. Ubuntu used Go 1.27.3 and passed all five non-Scheme jobs. The Scheme receipt records dependency preparation at 59m50.65s, target selection at 61.90s, native cold build at 7m51.05s, and a passing rooted Rust owner. The gRPC nested restart case exhausted its 12-second scenario deadline after control reconciliation took 7.25s. On macOS, dependency preparation passed in 25m51.96s, while native compilation reached the 8-minute deadline immediately after archive assembly. Both failure receipts are preserved. Weaver CI for the simplified entrypoint.
  • 818ca68a removes the Go race runtime's default one-second sleep after main returns in the control test fixture. A deliberate race still reported and exited with the configured failure code. The original local four-worker Go/gRPC race suite passed in 215.79s against the already-built native library, with the nested restart reaching its join in 9.27s. The original CI entrypoint is running for this revision. Exact CI.
  • The previous Ubuntu dependency run entered Gerbil's automatic gxtags pass after about 16m13s and finished 43m38s later. The published Gerbil source shows this pass recursively imports Scheme source to generate an editor index after package builds. Two earlier Ubuntu logs show about 30m and 35m after the same marker. A local isolated scan of the installed dependency tree took 83.13s and produced the same 585-byte output size as the local package-manager scan. That local probe does not reproduce the Linux tail. The native dependency command is unchanged.
  • The original Go workloads, four-worker settings, target/cold-build/recovery/exit budgets and all failed receipts remain retained. Source dependency preparation is measured separately from native runtime acceptance.
  • Prior provider correctness and performance evidence remains in docs/10-19-llm-gateway/10-routing-and-inference/10.17-admission-turn.org. Favorable retained cohorts do not establish broad P2 performance. This PR remains Draft.
  • Production approval and approved site replay are separate outstanding records. Local Weaver/SnakeOil qualification does not depend on them. Formal A/A and retained A/B must bind the site material and a completed sample/estimator plan to one release before execution.

Generated verification evidence stays in ignored cache directories; normal GitHub artifacts publish structured receipts.

@GTrunSec GTrunSec changed the title Narrow provider lifecycle invalidation without splitting shared constraints Share provider read custody across budget domains Nov 5, 2026
@GTrunSec GTrunSec changed the title Share provider read custody across budget domains Preserve provider authorization through shared custody and admission scheduling Nov 5, 2026
@GTrunSec GTrunSec changed the title Preserve provider authorization through shared custody and admission scheduling Preserve provider admission and qualify native Scheme governance Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant