Vixe

Status: 0.1.0a2 is an experimental V1 fixture-execution boundary. It is not a usable AI platform, and its default providers fail closed: they do not establish mechanical network isolation or run a fixture.

The package exposes its identity and a deliberately constrained fixture CLI:

vixe --help
vixe --version
python -m vixe --help
python -m vixe --version
vixe execute FIXTURE_ROOT

Execution is only considered after an injected provider supplies independently verified mechanical network isolation. The built-in Windows and Linux providers do not supply that proof, so they return not-established / not-run and exit with code 10. Python alone is not such proof.

V1 accepts exactly one declared Python entry script and its declared fixture files. After an injected provider proves mechanical network isolation, Vixe materializes those files in a temporary workspace and returns redacted output and provider evidence. It does not expose a generic shell, arbitrary binaries, external modules, containers, a model loop, or a persistent runtime. This API boundary is not a claim that Vixe is ready to execute untrusted code: without a provider that supplies that proof, no workspace is materialized and no script runs.

Read the execution contract before using vixe execute. This release has no working mechanical Windows/Linux isolation backend, network access, shell or general subprocess interface, models, or Norte dependency. It has zero runtime dependencies.

Development

With the test dependencies installed, validate the project with:

python -m compileall src
python -m pytest
python -m build

The source repository is cereja-project/vixe.

Releases

Release artifacts are built by GitHub Actions and published to PyPI only through Trusted Publishing with OpenID Connect. The repository does not store a permanent PyPI token.

License

Vixe is available under the MIT License. Copyright 2026 Cereja Project.