Interfaces & Data
Interfaces
| Interface | Type |
|---|---|
| React web UI (Vite) | Frontend |
Tauri Rust backend commands (generate_output, validate_document) | IPC surface |
@tauri-apps/api | IPC transport |
File import/export (.sdb.json, JSON, YAML, Schema) | Filesystem |
| React Flow drag/drop graph UI | Workflow editor |
CLI scripts (pnpm, node workflow-smoke.mjs) | Build/test tooling |
Produces
- Structured data outputs: JSON, YAML, TOML, XML, JSON Schema
- Workflow YAML files (Structra YAML, GitHub Actions, GitLab CI targets)
- Project files (
.sdb.json) - Desktop bundles/installers (NSIS, MSI — per release notes)
Consumes
- Visual UI input (the document model itself)
- JSON inputs
- JSON Schema inputs
- Workflow YAML imports
- Project
.sdb.jsonfiles
Depends on
- Node.js, pnpm, Vite, TypeScript, React, Tailwind CSS, Zustand
- Tauri, Rust,
tauri-plugin-opener - React Flow, Monaco editor (implied by sampled evidence)
Used by
Not recorded — used_by is empty. Standalone operator tool.
Notable governance detail
docs/release-notes-v1.0.0.md already contains artifact filenames and SHA-256 values, and the Tauri config version (1.0.0) matches manifest.project.version (1.0.0) — but none of that is reflected as verified fields in the manifest itself. This is a recurring pattern across several DRS projects in this portfolio: real release evidence exists in a human-readable doc, but hasn't been transcribed into the manifest's machine-checkable verification fields yet.