Skip to main content

maf-sandbox-mxc

PyPI Python License

Experimental. The API may change without notice. Importing the package emits MafSandboxMxcExperimentalWarning.

Durable MXC Python sessions, bounded helper transports and mutual-TLS coordination. This package is unreleased and experimental. MxcSandboxBackend supplies a closed-network native Python program channel with bounded input and output files. The initial adapter/CodeAct workloads passed independently on Linux/KVM and Windows/WHP in run 44001109808; this records the initial retained file profile. Review changes to recovery and program errors require a new native run; MXC 1.1 console qualification and production acceptance remain separate.

Runtime surfaces

  • shared_store, native_journal and shared_call provide SQLite publication, checkpoint recovery, result replay, quotas, freshness and cleanup ownership.
  • remote_authority, remote_api, remote_host and remote_control provide fenced ownership and mutually authenticated checkpoint transfer between configured hosts.
  • files and streams provide bounded transport for the separately qualified custom-kernel profiles.
  • host_call supervises the pinned native helper with bounded output. The legacy single-owner CLI and crash probes remain in repository tooling.

The adapter depends on maf-sandbox; the underlying journal and transports use the Python standard library. Native helper binaries, kernels and rootfs images are provisioned separately, with exact identities supplied by the host. Installation does not download, compile or launch them. Existing stores retain their original helper/profile bindings; packaging does not migrate checkpoints or change wire/store formats.

Native adapter

Construct MxcSandboxConfig with the host-owned helper, startup directory, private journal root, a runtime profile name, expected helper SHA-256, startup_identity(startup), Limits and ScratchLimits. Pin identities from qualification evidence rather than accepting assets from an untrusted request. Keep the configured assets immutable while the backend is open. Call await backend.initialize() once for a new root; subsequent backend instances reopen that journal on acquisition and refuse a missing or mismatched store. await backend.aclose() releases ownership while retaining checkpoints and completed results. Disposal retires the selected session and collects checkpoint payloads while preserving retained results and permanent retry identities. Key disposal and scope purge retry retired epochs that still own native resources, including epochs not acquired by this process. Acquisition visits a bounded batch of retired epochs for checkpoint collection and due result expiry; execution also maintains the active session.

The result allowance must cover base64-encoded artifacts and both streams. For the default transfer envelope, the native qualification uses Limits(..., result_bytes=32 * 1024**2). Scratch admission must also cover two configured maximum checkpoints plus bounded input, output and metadata staging; the transport refuses insufficient budgets before starting a guest.

The first channel uses the retained MXC 1.0.1 file-capable custom profile with the directory-collection helper extension. The MXC 1.1 console profile is a separate qualification and cannot supply this file/independent-stream contract. Allowlisted and unrestricted network requests, guest images, shell execution and host tools are refused. Use ProgramRequirements(max_program_bytes=65536) and a call timeout of at most 90 seconds. Configure CodeAct file transfer limits within the default 16 MiB / 64-file envelope. Stage uploads beneath their allocated call directory, such as call-id/input.csv relative to /workspace/calls; root-level uploads are refused because no native call owns them. Directory collection includes input files still present after execution, so they count toward the output envelope. Output exceeding either independent one-MiB stream allowance refuses publication rather than returning an apparently complete ExecResult.

Fresh interpreter state is the default. Set persistent=True and explicitly select router Cleanup.RECLAIM to retain Python state across successful calls and router restarts. Recovery binds the exact stored contract and remains distinct from a fresh baseline; RESET and DISPOSE never authorize it. Persistent recovery requires core 0.55 or the repository workspace containing that prepared release; core 0.54 supports fresh mode and refuses persistent configuration before allocating backend resources. The router's normal disposal policy remains appropriate for fresh calls. Every successful native call collects its bounded directory, reclaims native call files and commits the checkpoint with its result before acknowledgment. Collected files are immutable host-side snapshots for delivery; they are not paths into the host filesystem. The backend rejects concurrent direct access outside its call_admission scope and waits for native shutdown on cancellation.

Guest-language failures return bounded stdout, stderr and a nonzero exit status, including the traceback. They release scratch without publishing a checkpoint or successful retry result; the next call restores the last successful state. Native transport failures still refuse the call.

Direct run_call users supply a stable call ID and the exact original request when retrying after recovery. replay_result retrieves the full retained result envelope using the original instance ID, call ID and files.request.Request, including after disposal and without native assets; it requires matching call admission. An unknown, interrupted or expired identity is refused rather than executed again. Collected output snapshots become new inputs only after an explicit host upload. CodeAct allocates a new call directory for each new tool call; issuing a new tool call does not automatically replay an earlier one. The existing coordinator and freshness-witness APIs remain separate from this local adapter. Whole-machine recovery, allowlist enforcement and production qualification remain outside this candidate.

Development and qualification

Install from this directory with pip install ., or use the repository's uv workspace. Build and qualification tooling remains under scripts/experiments, importing this package. Generated reports belong outside Git and hosted reports remain workflow artifacts subject to retention.

MXC 1.1 rich-state qualification is recorded separately from the 1.0.1 custom file/stream profiles. A package build or offline test pass does not establish native isolation, cross-platform checkpoint portability, physical power-loss recovery or production readiness. Networking remains closed for the qualified Hyperlight profile.

The MXC research record contains the accepted design, implementation status, native evidence, reproduction instructions and workflow entry points.

Metadata

Release files for maf-sandbox-mxc 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for maf-sandbox-mxc 0.1.0
File Size Uploaded Provenance Actions
maf_sandbox_mxc-0.1.0.tar.gz 69.9 kB With provenance Details for maf_sandbox_mxc-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for maf-sandbox-mxc 0.1.0
File Interpreter ABI Platform Actions
maf_sandbox_mxc-0.1.0-py3-none-any.whl Python 3 none any Details for maf_sandbox_mxc-0.1.0-py3-none-any.whl

Total release size: 157.1 kB

Release files / maf_sandbox_mxc-0.1.0.tar.gz

Download URL maf_sandbox_mxc-0.1.0.tar.gz
Size 69.9 kB
Tags Source
SHA-256 checksum
How to use checksums
bd44b85d8095c1f5aed38dd9bdc0ec258ccc7792ec319c70769d63729a1a59aa
BLAKE2b-256 checksum
How to use checksums
e6c41ccaf0136d9b0fa960b0428910b609d05efa007135408737f7c1c49799c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.

Transparency log

Release files / maf_sandbox_mxc-0.1.0-py3-none-any.whl

Download URL maf_sandbox_mxc-0.1.0-py3-none-any.whl
Size 87.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9dd7aa62b31c1bb806a2a4541169c3b2cb30395ade83a554d907ded5e5e3aaca
BLAKE2b-256 checksum
How to use checksums
52a5dc0f352eeec56df5a8bf6bb860922c2c6da9511b84f4408db3940dbb22b2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.

Transparency log

Security for maf-sandbox-mxc 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for maf_sandbox_mxc-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 20, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page