← eijex home

ValidationHub · Public code

Versioned evidence, without collapsing scientific states.

ValidationHub is the open evidence-registry foundation for canonical identity, append-only lineage, review state, and evidence-package references across Eijex research workflows.

Evidence registryAppend-only lineagePermissioned records

Evidence lineage

Keep the chain inspectable from design to reviewed package.

Each stage has its own identity and version. Links preserve provenance; they do not make a prediction equivalent to an experiment or turn a review decision into a biological result.

  1. 01

    Design package

    candidate identity

  2. 02

    Construct

    material identity

  3. 03

    Experiment

    protocol context

  4. 04

    Outcome

    observed result

  5. 05

    Evidence review

    human decision

  6. 06

    Evidence package

    versioned projection

identity + version + content hash + reviewer state

Scientific-state separation

Related records are not interchangeable evidence.

Prediction

A model or design method proposes an expected property. It remains a computational statement.

Computational check

A deterministic or analytical check records what the software measured, with version and artifact identity.

Experimental observation

A wet-lab outcome is linked to its construct and experimental context without inheriting a computational claim.

Registry v0

A testable foundation, not a completed platform.

The public repository provides the local standard-library SQLite registry foundation, schemas, policy documents, tests, and synthetic examples needed to inspect the contract.

Public implementation

  • • Append-only local ledger
  • • Schema and hash checks
  • • Synthetic fixtures and tests
  • • Public-safe intake contracts

Not yet represented

  • • No hosted public evidence database
  • • No live PostgreSQL connection
  • • No automatic public claim generation
  • • No regulatory or clinical authority

Data boundary

Open infrastructure does not mean open experimental records.

Code, public schemas, documentation, and synthetic fixtures are open. Raw sequences, partner documents, personal information, and permissioned experimental evidence are governed separately and are not published in the software repositories.

Public summaries require separate consent and review. The registry preserves references and decisions; it does not silently publish the underlying permissioned material.

Inspect the public registry foundation.

Review the schemas, policies, tests, and synthetic examples.

Open ValidationHub on GitHub ↗