Skip to main content

Showcases

Explore 27 executable workflows organized by technical domain. Each page explains the workflow DAG, activity responsibilities, inputs, outputs, provenance, and execution considerations without embedding implementation code in the documentation.

The complete Dockerfiles, Python programs, generators, input fixtures, runners, and validators are maintained separately in UFFeScience/akoflow-examples. A single source-bundle link on each page connects the explanation to its versioned implementation.

Choose a category​

  • Machine Learning — training, tuning, inference, evaluation, conversion, vision, ensembles, and infrastructure selection.
  • Generative AI — retrieval, synthetic data, audio transcription, document extraction, and offline video creation.
  • Document AI — classification, structured extraction, and reconciliation.
  • Media intelligence — reproducible video inspection, segmentation, audio analysis, and timelines.
  • Rendering — procedural scenes, parallel frame shards, and animation composition.
  • Agentic workflows — bounded agents, supervised tool use, and multi-agent review.
  • Scientific AI — AI-assisted analysis, surrogate models, and experiment feedback loops.

Machine Learning

Executable training, tuning, inference, evaluation, and model-delivery workflows.

Generative AI

Executable data preparation and evaluation workflows for retrieval, generation, audio, and documents.

Document AI

Executable extraction and reconciliation workflows over auditable document corpora.

Media intelligence

Offline audiovisual inspection, segmentation, measurement, and timeline workflows.

Rendering

Procedural scene construction and parallel frame rendering workflows.

Agentic workflows

Executable bounded-agent workflows with explicit review, policy, and evidence stages.

Scientific AI

Executable simulation, analysis, surrogate-model, and experiment-feedback workflows.

Validation model​

Every source bundle is exercised by the centralized examples CI. The regression fixture verifies its declared local inputs and outputs; provider-specific execution on HPC, Kubernetes, or cloud infrastructure still depends on the environment and permissions described by the corresponding infrastructure guide.