schemaxis/Agent’s HandsDelivery choices · offer under review
The five-point product explanation
In the strict declared-work interface, the agent never runs code or directly handles source data. It declares where the data comes from or how it is generated, which operations it passes through, and how it is output. Schemaxis marshals immutable input captures, sealed execution and outputs retained by digest.
This describes who operates on the inputs: no agent-supplied arbitrary scripts, shell or direct source-filesystem manipulation. The agent can receive bounded observations and receipt content; this does not promise that data is hidden from the model. Sealed container execution requires an explicitly configured, qualified backend. Native applications execute trusted runtime code. The historical local MCP demonstration alone does not establish that isolation.
Admission, the declared schema, task scope and budget reservation are checked before execution. A request outside its authority is refused before a native job can run. Planning and inspection can run without launching the applications; native result verification is a separate step that reports the checks actually performed. In the retained MCP demonstration, a NumPy request under a SymPy-only scope returned SCOPE_EXCEEDED. Calls stopped at planning: zero native execution, all four prior NumPy output digests unchanged, and no successful current invocation to claim.
Historical prepared-recipe local MCP demonstration, core 5cfe1b0. It is separate from both the comparative study and the hosted container-isolation proof.
Haiku 4.5: 22/110 without → 110/110 with Schemaxis; Sonnet 4.6: 22/110 without → 110/110 with Schemaxis; GPT-5.6 Luna: 68/110 without → 110/110 with Schemaxis. Haiku 4.5’s native initial output had 32/32 images rejected, while its retained transcript called the result “production-ready”. The Schemaxis artifacts passed the required checks. The core supplies the verification state and receipt instead of relying on the agent’s success sentence. This records a misleading claim and changed artifact outcomes; it does not measure a general reduction in false-reporting propensity.
29 September 2026: one authoring conversation per model and method, older model versions, 110 checks across an initial task and revision on small, purpose-built serial ParaView fixtures. Checks are not independent tasks. Some historical Schemaxis runs inspected implementation details or used helper code; one revision wrapper was broken despite passing artifacts. These are artifact outcomes, not qualification of the new strict no-shell authoring interface. The Opus native control was excluded after provider substitution.
A supported declared recipe can be repeated with varied authorised inputs and parameters; each execution produces its own receipt. The reusable document and bounded parameter contract are the mechanism, not a measured advantage for junior staff. Anyone using the supported, configured environment and authorised inputs can repeat it. Compatible runtimes, scope and checks still apply; the record preserves honest failure and unknown states.
The downloadable two-case SymPy example checks local-core binding and host planning only: no native execution or new receipt was created by those preflight checks, and no hosted file-template endpoint is implied.
Frontier models passed either way in the retained paired studies, and Schemaxis was slower.
GPT-5.6 Luna with Schemaxis passed all 110 checks at about one tenth of Astra’s native historical scored API cost (US$0.0815 versus US$0.8828); n=1 conversation each, older versions and 29 September 2026 prices. This is not current pricing or a total compute/support-cost estimate.
Apache-2.0 distribution boundary: declared operations, inspection/planning, reusable templates and parameter forms, local execution, verification and evidence. The source is available on GitHub; own compute, application rights, installation and maintenance are needed.
A template holds the recipe; parameter files describe particular jobs. Keeping those files does not keep a hosted account active. Local reuse needs fresh inputs, configuration and verification; old task/upload IDs and keys are not portable.
Provider-operated execution, containment, fresh checks, result/receipt lifecycle, deletion controls and bounded support during access. It is not a charge for one conversion or unlimited use of all applications. Buyer value and the C$400 proposal remain under review.
No GUI paywall or licence change is adopted. A private team hub and integrated history/context service are separate directions, not included current runtime-pilot features. No paid subscription or maintained workflow library is being promised.
Earlier hosted proposal · under review
Per project · 14 elapsed days / 336 hours
Earlier draft before applicable tax; not a final offer.
No purchase or payment action is available here.
Weekdays 09:00–17:00 Winnipeg time, excluding locally observed holidays, with a next-business-day reply target. Two combined hours of onboarding and workflow support per project.
This is a reply target, not an uptime SLA. The monitored support channel still needs confirmation. If ordinary support would exceed two hours, pause and agree a narrower acceptance task or a refund decision. No extra charge is automatic.
Proposed first cohort: up to two independent organisations and three projects. The final order must bind the release, task limits, data terms and absolute UTC start/end instants.
100 verified outcomes per UTC month is an upper quota, not a guarantee of success or a 100-run whole-trial entitlement. A month-spanning 14-day term can permit up to 200 across the two months; unresolved reservations reduce availability.
Input, operation and capacity bounds ↗Prototype state explorer
Only preparation is current. Every later state below is a labelled design example. Changing this selector cannot activate, charge, run or delete anything.
All states remain documented without JavaScript in the expanded reference below.
Current real availability
An enquiry can start a fit discussion. No account, payment or working customer access is available in this prototype.
No charge or credential.
An enquiry can start a fit discussion. No account, payment or working customer access is available in this prototype. No charge or credential.
The task is outside the admitted scope or capacity is not available. A fit discussion does not reserve a project. No charge or access promise.
The earlier C$400 CAD / 14-day proposal is under review, not an issued offer. Price, scope, eligibility, tax, terms and exact UTC dates need the eventual reviewed order. Draft quote AH-PILOT-2026-01 · unsent.
An issued invoice, payment redirect, manually marked paid invoice or pending payout is not bank-reconciled settlement. No collection is connected here. No payment was requested or received.
In a real pilot, independently matched per-payment bank settlement would still be followed by host readiness, accepted terms and operator-confirmed activation. Synthetic example · no funds exist.
An approved project would use the invitation’s tested endpoint and short-lived key, with the final quota, support channel and absolute UTC expiry. No reusable key appears on the website. Synthetic example · no access has been issued.
A failed or unverified result is not success. An unknown outcome requires operator reconciliation; do not replay it with a new idempotency key. No result or quota reset is implied.
Cancellation remains requested until the exact worker cleanup settles. Unknown outcomes and reservations stay visible. Requested is not completed.
A deletion request is recorded, but worker reconciliation or physical removal is still pending. Poll the owned deletion status. Backup expiry remains separate.
Only actual deletion-status evidence could establish physical deletion. This example does not prove forensic erasure or expiry of every backup. Synthetic status · nothing was uploaded.
The 336-hour term ends at the agreed absolute UTC instant. No automatic renewal or silent extension. Arrange export, deletion and closure with support before expiry. Expiry does not certify backup deletion.
A refund request or initiated refund is not a settled return. The agreed cancellation/refund terms and actual finance evidence govern each state. Draft policy not yet adopted; no payment or refund exists.
Suspend admissions, preserve unknown outcomes and contact support. Do not automatically replay jobs or clear reservations after restoring a host. No uptime SLA or recovery guarantee.
Before an invitation
A small, deliberate pilot