-
Notifications
You must be signed in to change notification settings - Fork 0
primitives evidence
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
Active contributors: Douwe de Vries, vriesd
Evidence links a Finding or generated output back to supporting Entries and managed attachments. It keeps conclusions traceable to raw testing material.
| File | Purpose |
|---|---|
crates/qa-scribe-core/src/domain/finding.rs |
EvidenceLink domain type. |
crates/qa-scribe-core/src/services/session_service/findings.rs |
Evidence validation and persistence with Findings. |
crates/qa-scribe-core/src/services/session_service/generation.rs |
Generation context and evidence-related persistence. |
crates/qa-scribe-core/src/attachments/mod.rs |
Attachment files that can be referenced as evidence. |
Evidence connects Entry, Finding, Managed attachments, and AI-assisted Testware.
- 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