-
Notifications
You must be signed in to change notification settings - Fork 0
crates qa scribe core
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
Active contributors: Douwe de Vries, vriesd
qa-scribe-core is the reusable Rust library behind the desktop app and smoke harness. It owns the stable domain model and all local persistence behavior.
| File | Purpose |
|---|---|
crates/qa-scribe-core/Cargo.toml |
Crate metadata and dependencies. |
crates/qa-scribe-core/src/lib.rs |
Module exports and app status. |
crates/qa-scribe-core/src/domain/mod.rs |
Domain DTO exports. |
crates/qa-scribe-core/src/storage/mod.rs |
SQLite schema, migrations, indexes, and version checks. |
crates/qa-scribe-core/src/services/session_service.rs |
Service facade. |
crates/qa-scribe-core/src/attachments/mod.rs |
Managed files. |
crates/qa-scribe-core/src/generation/workflow.rs |
Generation workflow. |
crates/qa-scribe-core/src/ai/mod.rs |
Provider command construction. |
The crate uses rusqlite for SQLite, serde for DTOs, specta for exported types, thiserror for errors, uuid for IDs, chrono for timestamps, sha2 for attachment hashes, and base64 for previews and data URLs.
The Tauri app depends on this crate through the workspace dependency declared in Cargo.toml. See Rust core for architecture and Reference data models for domain objects.
- QA Scribe
- Download overview video (MP4)
- Architecture
- Getting started
- Glossary
- By the numbers
- Lore
- Fun facts
- Video overview
- How to contribute
- Development workflow
- Testing
- Debugging
- Patterns and conventions
- Tooling
- Applications
- Desktop app
- Smoke harness
- Systems
- Rust core
- Tauri command bridge
- Frontend shell
- Generation jobs
- Provider detection
- Release tooling
- Features
- Session capture
- Rich record editing
- Managed attachments
- AI-assisted Testware
- Settings and provider setup
- Crates
- qa-scribe-core
- qa-scribe-app
- Primitives
- Session
- Entry
- Finding
- Draft
- Evidence
- API
- Tauri commands
- Deployment
- Security
- Background
- Architecture decisions
- Migration context
- Cleanup opportunities
- TODOs and FIXMEs
- Complexity hotspots
- Reference
- Configuration
- Data models
- Dependencies