Frequently Asked Questions

OEP is built to answer the hard questions—what ran, what changed, and can we prove it later—without overpromising outcomes. This FAQ explains what we provide, what we don’t, and how local-first, offline verification fits into real QA and regulatory workflows.

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

  • OEP is offline, deterministic evidence tooling that turns a run into a self-contained evidence bundle that can be verified later—independently and without network access.

  • No. OEP produces verifiable evidence artifacts and verification outputs. It does not certify compliance, guarantee regulatory outcomes, or replace auditors, notified bodies, or regulators.

  • No. OEP does not guarantee safety outcomes or system correctness. It helps teams document and verify what ran so safety, quality, and compliance work can be evaluated with stronger evidence.

  • PASS/STOP describes the state of the evidence bundle and verification checks:

    • PASS means required evidence is present and integrity/verification checks passed.

    • STOP means required evidence is missing, unknown, altered, or a verification check failed.
      PASS/STOP is not a regulatory approval or compliance verdict.

  • No by default. OEP is local-first: evidence is generated and verified in your environment. Nothing is transmitted unless you explicitly export and share an evidence bundle.

  • Yes—when you provide the evidence bundle. Verification is designed to run offline so an auditor or partner can validate integrity and check results without needing access to your internal systems.

  • At a minimum, it records what ran (inputs/toolchain context/outputs) plus integrity and verification metadata needed to check that the bundle hasn’t been altered and that verification checks can be repeated.

  • OEP fails closed. If required artifacts are missing, unknown, or altered, OEP produces a STOP outcome with a clear reason so you can remediate instead of guessing.

  • OEP is designed to integrate into existing test, release, and QA processes. It does not replace your tools; it adds an evidence layer that makes runs easier to audit and reproduce later.

  • No. OEP is designed for local/offline operation. If you choose to move evidence bundles into your own storage or systems, that’s your decision and your environment.

  • No. OEP is evidence tooling. Any telemetry or capture functionality is explicit and user-directed, not continuous monitoring by default.

  • You do. You control the environment and custody of your evidence bundles. (If you need specific IP and output-rights language for procurement, use the legal section of the site or your contract pack.)

  • Use OEP as evidence support for your existing quality and regulatory workflows. For legal or regulatory interpretation, consult your own qualified counsel and regulatory advisors.

  • We renamed the public product to OEP (Olexian Evidence Platform). If you see “OCP” in public-facing materials, please notify us so we can correct it.

  • Contact us for a short workflow review. We’ll identify where evidence bundles fit naturally in your run/release process and what “offline verification” looks like in your environment.