# Sources behind the status

Where every line of the development status comes from, and how to read the test counts.

Every line on the [development status](https://docs.vraelis.com/status) names its source. These are the sources.

| Source | What it is |
| --- | --- |
| Founder brief, 10 October 2026 | What is implemented, unfinished and never claimed. |
| Internal automated testing, runtime-policy revision | The 131 tests of the earlier runtime-policy revision, reproduced offline on a separate pinned Docker build. Runtime policy enforcement checked. |
| Internal automated testing, October 10, 2026 (runtime rejection-diagnostics revision) | 133 of 133 at source revision contour-runtime-status-rejection-v1, run with networking disabled (NetworkMode none before and after, exit 0). The retained test log was checked against its SHA-256 (441d44b4…08c5). |
| Internal automated review of the evidence app | Evidence app review: five findings, each addressed in the current version. |
| Specification v1.3 | Internal proposal, including the Kubernetes collector. Not applied, not frozen. |

## Reading the test counts

133 of 133 experiment tests at the runtime rejection-diagnostics revision, in the pinned network-disabled harness, reproduced by internal automated testing on a separate build on October 10, 2026 (Pacific). The earlier 131 of 131 belongs to an earlier revision and is history.

> **Never added together.** The counts of different revisions and suites are separate measurements. They are not summed, and none of them is production readiness, customer demand or independent review.

---

Vraelis documentation, Vraelis. https://docs.vraelis.com/sources