Dokime

Docs version: v0.1.0-297-gb5ac806

Dokime is a desktop test-operations product for planning test cycles, running cases, collecting evidence and telemetry, and reviewing or exporting the result. It serves engineers and operators who need a durable record of what was planned, what ran, what happened, and what was reported.

This site maps the product that exists in this repository. It distinguishes working product paths, code-defined examples, and disconnected-safe integration contracts; it does not present roadmap items as features.

The Product Today

Area	What exists
Desktop	A Tauri 2 application with Plan, Execution, Cycle, Explore, and Settings views.
Runtime	A Rust runtime that owns cycles, reports, prompts, evidence, telemetry, traceability, installed artifact state, and supervised jobs.
Persistence	A Harmos journal, snapshot, series store, and artifact store beneath the configured storage root.
Artifacts	Six installed artifacts, including four sidecar-bound integrations, in the default composition.
Interfaces	An Axum REST service, a Rust CLI, and Python bindings.
Distribution	Desktop-only Windows NSIS and Linux DEB/RPM installer configurations.

The Main Workflow

flowchart LR
    A[Plan a cycle] --> B[Start execution]
    B --> C[Run and observe cases]
    C --> D[Collect evidence and telemetry]
    D --> E[Review in Explore]
    E --> F[Generate reports and documents]

The GUI is the primary operator surface. REST exposes the same runtime to automation and agents. Harmos is the runtime substrate for durable state, streams, artifacts, installed artifacts, and sidecars; Dokime owns the test-product model and its user workflows.

Where To Go Next

• Build and run Dokime.
• Follow the core test-cycle workflow.
• See the product map for crate and interface ownership.
• Read the product ladder before changing architecture.