Skip to content

First-Party Artifacts

Dokime compiles three first-party sidecar-bound artifacts. They are worked examples of independent suite and domain registrations, but they do not all represent live third-party service integrations.

validation-synthetic is the source identity of the Synthetic plugin under plugins/synthetic. Its startup, steady-state, protection and recovery suites exercise one simulated AC DUT per execution. The shared app-runtime model owns voltage/current waveforms, phase, inrush and latched faults; steps and the SDK sampler share each execution’s device.

AC voltage, load and duration are template parameters. The steady-state voltage list and load linspace produce nine Cartesian cases. images.directory is a separate path setting used by the optional startup reference-image attachment. The synthetic.status route is read-only process readiness. SDK execution and samplers shut down before the plugin stops its embedded Harmos runtime.

The Mini plugin’s Pulse template can enable capture_system to lease its system sampler only while the stream step runs. Its completion criterion checks ctx.gaps::<SystemRow>(), so a refused or interrupted channel cannot silently count as complete evidence. The default leaves this optional capture off.

plugins/fabric is one crate with a library and native entry point. Its microsoft-fabric plugin contributes workspace settings, a fabric.token credential binding, options, and fabric.workspace.connect / fabric.sync.queue routes. It is deliberately disconnected-safe: the current implementation validates and records the contracts but performs no external Fabric I/O.

plugins/zephyr likewise contains one library and native entry point. Its atlassian-zephyr plugin contributes settings, credentials, actions, and the zephyr.site.connect, zephyr.results.sync, and zephyr.status routes. It is also disconnected-safe and performs no external Zephyr I/O.

For exact ids, contribution types, and bindings, use the Installed Artifact.

Dokime markDokime · Stokker Technologies