Skip to content

feat(python): add experimental Extropic execution integration - #18

Merged
jeremydixon22 merged 3 commits into
mainfrom
feat/extropic-execution-prototype
Aug 11, 2026
Merged

feat(python): add experimental Extropic execution integration#18
jeremydixon22 merged 3 commits into
mainfrom
feat/extropic-execution-prototype

Conversation

@jeremydixon22

Copy link
Copy Markdown
Member

Summary

  • add an optional Extropic-backed Python execution handler integration without widening the portable runtime contract
  • checkpoint create/upload/start/supervision boundaries and fail closed around Extropic create ambiguity
  • map cancellation, provider status, bounded artifacts, explicit seeds, and JSON results into existing Vyral execution semantics
  • add deterministic coverage, a guarded CPU-only live smoke, and current-state user documentation

Verification

  • scripts/verify-python-runtime.sh (223 tests; 79.0% combined branch coverage; 81.9% Extropic module coverage; strict mypy; wheel/sdist/clean-install gates)
  • clean vyral-runtime[extropic] install against extro-sim 0.5.0 with local serialization round trip and pip check
  • scripts/verify-public-export.sh --allow-dirty (823-file deterministic export; secret, ownership, and history scans clean)
  • publication policy and public SDK surface checks

Posture

  • prototype only; not added to the adapter qualification matrix
  • no Z1 support claim and no public contract/decorator change
  • live smoke is manual, CPU-only, token-required, double opt-in, and was not run in this change
  • package publication remains withheld

@jeremydixon22
jeremydixon22 force-pushed the feat/extropic-execution-prototype branch from 4ff6966 to f984b43 Compare August 11, 2026 05:17
@jeremydixon22
jeremydixon22 merged commit 5510585 into main Aug 11, 2026
9 checks passed
@jeremydixon22
jeremydixon22 deleted the feat/extropic-execution-prototype branch August 11, 2026 06:37
jeremydixon22 added a commit that referenced this pull request Aug 11, 2026
## Summary

- add a real Torx parameterized-stochastic-circuit workload behind the
registered Vyral Extropic boundary
- prove local execution and by-value workload packaging in a clean
process with no application module available
- add a path-scoped CI check plus a separately guarded, credit-consuming
L4 live proof
- pin the current `extro-torx`/JAX compatibility line without narrowing
the base runtime Python floor

This is stacked on #18 and intentionally makes no hosted-sandbox,
Thermalizers, or Z1 qualification claim.

## Verification

- 223 Python runtime tests; 79.0% combined branch coverage
- strict mypy across 79 source files
- wheel, sdist, server extra, and clean-install verification
- clean `vyral-runtime[extropic-torx]` install with `pip check`
- real Torx local + clean-process packaging proof
- deterministic public export, secret/ownership/history scans,
publication policy, and Markdown links

The hosted L4 proof was not run: it remains double-opt-in, token-only,
and credit-consuming.

Co-authored-by: jeremydixon22 <jeremydixon22@users.noreply.github.com>
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