Skip to content

Lab 0.9.11: sent reasoning-effort blueprint

Choose a tag to compare

@mbachorik mbachorik released this 08 Nov 22:34

Lab0.9.11 — sent reasoning-effort blueprint

Adopts actual published Runtime0.9.18 with an exact public wheel URL/source/SHA256,
retaining Core0.5.0, Harness0.9.12 and original recorder0.3.0/store0.4.1 bytes.
Adds the copyable sent-effort host, guide, installed
synthetic HTTP/native acceptance and required real PostgreSQL recovery. Every
previous blueprint remains available with unchanged resource bytes.

Behavior: Result observations separate artifact requests, original profile
defaults and actual encoded HTTP controls/launched native effort argv. Retries,
tools, repairs and safe pool fallback retain bounded owned histories. Explicit
none/false, omission, zero attempts, unknown execution and truncated observations
are distinct. HTTP call IDs join existing recorder evidence without schema changes.
Sent never proves provider delivery, acceptance or compliance. Native inner calls
and vendor settings remain unobserved; no new effort support or retry allowance.

Compatibility and identity: Artifact/rule/prepared/workflow/bundle input
identities gain no fields; independent public0.9.17 goldens remain exact. Saved
private Result bytes gain additive evidence; old receipt absence is preserved,
not invented. Published Harness and PG adapters require no new DDL or republish.
Prior active manifests/provenance/freezes are preserved verbatim as pre-sent-effort;
only current SDK profile and development/evaluation freeze hashes advance.
Corpus/prompts/scoring/live evidence remain unchanged. Public views stay filtered;
observations grant no authorization, billing eligibility or consent to retry.

Release gates: Fresh exact source and isolated installed wheel/rebuilt-source
consumers; frontend/browser/native checks; all four LinuxAMD64/ARM64×PG16/18
ordinary cells, four installed rule/feature/PG cells and both reasoning jobs.
Required database lanes fail missing infrastructure and verify restricted roles
and exact cleanup. Local candidate checks do not certify the final released train.
Require exact-head overall SUCCESS, original CI ZIP/source payload/count evidence,
expected-head merge and equal tested/merged trees. Publish only original qualified
CI wheel/source archives and sanitized proof. Anonymous public downloads, fresh
wheel/rebuilt-source consumers and all independent post-merge gates must pass.
Earlier tags/releases/assets are immutable. No live inference.

Qualified source: 5e280ee7c8792110e1a380fbf10ce7d19d07be3b; merge: 94ba18812d8ac80dc6bbeb31cda2203d83403c41; equal tree: 48cbfd3bb3e3abf56f1f8c220fd4727cd386da38.

All ten pre-merge checks and overall GraphQL status passed. Each ordinary architecture/database cell passed 2,193 source tests and 334 real-stack cases (1,336stack executions total). Each installed cell passed 141 rule cases, 159 blueprint cases and 12 real PostgreSQL cases, including authentic Runtime 0.9.17 → 0.9.18 receipt recovery. Both reasoning jobs passed 31 cases and 58 control samples without live inference. All eleven original CI archive digests and source payloads were verified.

The wheel and source archive are the original successful CI bytes from run 42525783244. VERIFICATION-0.9.11.json, QUALIFICATION-0.9.11.tar.gz and SHA256SUMS bind source, SDK lineage, architecture/database counts, cleanup and artifact hashes. Independent post-merge and public-consumer evidence is added after actual completion. No live-provider certification is claimed.