OEP - Pilot Program:

Contact Us

Olexian is a local-first tool for reproducibility and verification. A pilot is a small, internal evaluation to confirm whether Olexian’s evidence bundles and verification reports are useful in your environment.

This pilot is designed for non-sensitive workflows (or synthetic/de-identified data) and does not require cloud services.

What you’ll test

You’ll run a small workflow and receive an offline-verifiable evidence bundle that answers:

  • What ran (inputs, configuration, and declared outputs)

  • What changed (artifact hashes and version identifiers)

  • Whether the bundle is intact (verification outcome and failure context)

  • Whether the run can be replayed deterministically (when applicable)

Olexian does not certify compliance, validate scientific conclusions, or guarantee safety outcomes. It produces verifiable evidence about execution.

What we need from you

Choose one of these options:

Option A — Minimal workflow (recommended)

  • A small script/notebook/pipeline step that runs in minutes

  • A synthetic or de-identified dataset (or a dataset you are allowed to share internally)

  • A definition of expected outputs (files or artifacts)

Option B — “Hello, Evidence” demo

  • No lab data at all

  • We run a provided example workflow to validate setup and artifact clarity

What you’ll get

After the run, you’ll have a folder (or archive) containing:

  • A run manifest describing declared inputs/outputs and run metadata

  • Cryptographic hashes for artifacts in the bundle

  • A structured stop/refusal record when something is missing, unknown, or altered

  • A deterministic verification report that yields a clear outcome (e.g., PASS/REJECT)

Everything is designed to be verifiable later, offline, on your own systems.

Time and effort

Typical pilot time:

  • Setup: 15–30 minutes

  • First run: 5–15 minutes

  • Review: 10–20 minutes

If your workflow is more complex, we keep scope small and focus on artifact quality rather than full integration.

Data handling and privacy

  • Local-first: data stays on your systems.

  • No automatic uploads: Olexian does not require cloud services.

  • Non-sensitive by default: pilots should use synthetic or de-identified inputs unless you explicitly choose otherwise.

If you need an NDA or internal review process, we can keep the pilot entirely “air-gapped” and limited to example workflows.

Success criteria

A pilot is successful if you can say “yes” to most of these:

  • The bundle contents are understandable without tribal knowledge

  • Verification outcome is unambiguous and repeatable

  • Failure modes produce actionable context (not vague logs)

  • It’s clear what changed between runs (hashes + identifiers)

  • The artifacts are useful for internal review, auditing, or later replay

What we ask in return

Feedback is the product. If the pilot is useful, we may request:

  • A short testimonial limited to tooling outcomes (artifact quality, replayability, verification clarity)

  • Optional permission to quote you by name/title or anonymously (your choice)

No testimonial will ever claim endorsement of research conclusions.

How to start

Send a message with:

  • Your preferred pilot option (A or B)

  • Your OS environment (Linux/macOS/Windows)

  • The workflow type (script, notebook, pipeline tool)

  • Any constraints (offline-only, air-gapped, no external dependencies)

I’ll respond with:

  • An evaluation build

  • A minimal pilot protocol (1 page)

  • A checklist for what the pilot will produce

Thank you for considering participation in the Olexian pilot program. We appreciate your time and feedback."

Contact