Reference
How Dummy Run works and the documents that govern it. Most pages are rendered from the repository’s own Markdown, so there is one source of truth.
- How it works
- A run from cast to results board, and the words we use
- Architecture
- Adapters, the evidence pipeline and data residency
- Telemetry
- How runs map to OpenTelemetry traces, metrics, logs and Grafana annotations
- Grafana
- Four dashboards and a local stack for the telemetry a run emits
- Run record
- The JSON a run writes, field by field, with an example
- Plan
- What ships, in what order
- Licensing
- What the Apache-2.0 licence lets you do
- Trademark policy
- What you may do with the name and logo
- Security
- Reporting a vulnerability, and findings about apps you do not own
- Contributing to Dummy Run
- How to contribute, the automated checks, and the rules on evidence and privacy
- Writing and citation guide
- How we write and cite
- Type scale and minimum sizes
- Body text at 17px, nothing read below 15px and headings that scale with the viewport
- Brand
- The logo, mascot and colours
- How the name was chosen
- Why the project is called Dummy Run, and the cautions on the mascot