Compatibility

Olexian is an offline-first verification platform that produces deterministic, verifiable evidence bundles for runs. This page describes current platform support, required tooling, and determinism boundaries for evaluation and deployment.

Supported Platforms

Operating systems

  • Linux (primary): Olexian’s primary operational target. Most development and verification workflows are designed and exercised here.

  • Windows (supported for evaluation; expanding): Many workflows run on Windows, but Windows operational support may vary by workflow and toolchain configuration.

Not currently supported as a target platform

  • macOS: Not currently a supported operational target. Some scripts may include cross-platform handling, but macOS is not a focus for supported deployments.

Toolchain Requirements

Olexian is built around strict role separation between languages:

  • Rust — custody/authority components (hashing, state machines, verification-critical logic)

  • Python — orchestration/glue only (process execution, JSON IO, file operations)

  • Julia (workflow-dependent) — used only when a workflow includes universe/numerics steps

Required tooling (typical)

  • Python 3.x (3.10 commonly used in current tooling; if your environment is pinned differently, we’ll provide an evaluation path that matches)

  • Git

  • Rust toolchain (repo-pinned; includes rustfmt/clippy in the toolchain file)

Workflow-dependent tooling

  • Julia runtime + hydrated environment only if you run workflows that include Julia-based kernels/universes.

Offline and Network Posture

Offline-first verification

  • Evidence bundle verification is designed to run offline. No telemetry is required for verification.

  • Proof-pack style verification is intended to operate without network access.

Notes on builds and dependencies

  • Fully offline builds are feasible when dependencies are already present and locked. Some environments may need an initial dependency fetch step before operating strictly offline.

Determinism Boundaries

What is deterministic

  • Verification is deterministic given the same evidence bundle contents and schemas.

  • Verification outcomes are reported as:

PASS — The evidence bundle is intact and can be verified offline.
REJECT — Verification refused: one or more required artifacts are missing, unknown, or altered. The report includes structured failure context.

What depends on your workflow

  • Replay determinism depends on whether your workflow itself is deterministic (fixed seeds, pinned dependencies, controlled clocks, controlled floating-point behavior).

  • Olexian can prove what ran and whether the bundle is intact; deterministic replay requires a workflow that avoids nondeterministic sources.

Cross-OS expectations

  • Evidence artifacts (especially JSON-based evidence) are intended to remain consistent across platforms when inputs and schemas are stable.

  • Binary artifacts are inherently platform-specific and should be treated as OS-scoped outputs.

Julia and “Full Strict” Runs

Some strict checks and workflows include Julia-based kernel/universe steps.

  • Verification-only / evidence integrity evaluation: Can be performed without Julia, depending on configuration and which checks are enabled.

  • Kernel/universe-including workflows: Require Julia to be installed and the environment to be hydrated; otherwise the workflow will refuse/stop with structured context.

If you’re an external evaluator, we recommend starting with the verification-only path, then enabling Julia-dependent checks only if you need to evaluate universe/kernels.

Distribution and Deployment

  • Current evaluation and verification handoff is typically delivered as bundles (e.g., zip-based proof packs / verification kits).

  • Optional signature verification tooling may be available depending on the bundle type and workflow. If signature verification is required for your evaluation, we will specify that explicitly in the evaluation protocol.

Getting Started (Evaluation)

For external evaluators

  1. Receive an evaluation bundle and extract it locally.

  2. Run the included verification command(s) for your platform (Linux shell or Windows PowerShell).

  3. Review the verification outcome (PASS/REJECT) and the produced evidence bundle contents.

For teams evaluating from source

Follow the repo’s “start here” / operator guidance for installing the toolchain and running the strict verification runner. For Windows environments, ensure the required Rust toolchain components and Python runtime are installed.

Thank you

Thank you for considering an Olexian evaluation or pilot. Practical feedback from real workflows is what drives improvements in artifact clarity, verification reliability, and deployability.