Skip to content

Roadmap

Three questions: what is done, what is being worked on, and what comes next. Spectio stays below 1.0 until it has been checked with several use cases and several groups; the conditions are written down in the release stages.

Designnow

Specifications, screen designs, test pipelines on both engines, reviews before any code.

0.1 · Walking skeletonafter the go decision

One run crosses every part once: launch, watch, stop at a gate, resume, hand off to depictio.

0.2 – 0.4 · Private alphawith 3 to 5 EMBL groups

Installed from the docs in under 30 minutes, real pipelines every night, backups tested.

0.5 – 0.9 · Public betawith a demo instance

Open to everyone, demo instance on EMBL's Kubernetes, upgrades tested release after release.

1.0 · Stablewhen the 1.0 conditions are met

Several groups using it daily, both engines on SLURM and Kubernetes, frozen API.

Done

  • The design, reviewed before code: 13 specifications, about 60 screen designs, a decision log.
  • Test pipelines written for both engines, with 11 scenarios (stops at gates, failures, retries, resumes) passing on Nextflow 26.10 and 25.10 and on Snakemake 9.27, on every change.
  • A test corpus of 14 nf-core pipelines and 9 Snakemake catalog workflows on their own test data.
  • This documentation, written and reviewed at every step.

Now

The design phase runs in waves. Each wave is a set of steps, done by agents and checked before the next wave starts.

Each step has its own page under Progress.

Next

  • Reviews before code (waves W1 and W2): consistency, facts, constraints, security, screens, depictio.
  • Development setup and test clusters (wave W3): local SLURM and Kubernetes for tests, dev previews, end-to-end tests.
  • The go decision (wave W4), then the walking skeleton.

Ideas, not scheduled

  • CWL and WDL engines.
  • Other schedulers: LSF, PBS, SGE.
  • GA4GH WES and TES interfaces.