Issues & Runs
How Certyn tracks work for auditability: issues, runs, and sessions.
Certyn uses issues and runs to track work and outcomes.
Not a replacement for your tracker
Certyn is not trying to replace Jira, Linear, or GitHub Issues. Internal issues and runs preserve Certyn's QA audit trail.
Runs
A run is an execution of a process (suite) or an ad-hoc task. Internally, a run is represented as:
- a parent run record
- child issue or execution records tied to the work
- one or more agent sessions that produce artifacts
Runs are how you answer: "Did this environment version actually work?"
Issues
An issue is a work item created from failures or exploration. A good issue includes:
- environment and run context
- evidence (screenshots, logs, traces)
- a clear statement of expected vs actual behavior
Verifying fixes
Certyn is designed for a fast verification loop:
- issue is created with evidence
- fix is deployed to an environment
- you re-run the relevant process/tests
- the new artifacts confirm whether the fix actually worked
The goal is to make verification evidence-based and cheap.