# Phase 7 — verification record

What was checked, how, and what it returned. Every block below is pasted output,
not a description of output.

Run 2026-10-26 on `.13`, headless Chrome for measurement.

## 1. Diagrams: structure and geometry

Each SVG was parsed as XML, then rendered inline in Chrome and **measured with
`getBBox()`** — the browser's own text metrics, not an estimate. The check
reported text overflow outside its box, partial overlap between boxes, elements
outside the viewBox, empty text nodes and unlabelled boxes.

```
01-homelab-topology.svg  OK
02-agent-architecture.svg  OK
03-rag-pipeline.svg  OK
04-edge-architecture.svg  OK
05-distributed-audio.svg  OK
06-media-pipeline.svg  OK
07-cost-resource-engineering.svg  OK
08-era-timeline.svg  OK

0 issue(s) total
checked 8 diagrams
distinct <style> blocks: 1  (1 = one visual language)
distinct viewBoxes: 1
```

The first pass produced 74 findings. They were fixed in the source of the
diagrams, not suppressed in the checker: shortened labels, widened boxes,
removed empty text nodes. The final run is clean.

**"One visual language" is one number: `distinct <style> blocks: 1`.** All eight
files carry a byte-identical style block, so there is no second palette to drift.

## 2. Diagrams: both themes

Computed colours of the first text node and the first box, resolved twice — once
with the browser's default scheme, once with `--force-dark-mode`, which makes
`prefers-color-scheme: dark` match.

```
01-homelab-topology.svg          light rgb(27, 34, 43)   rgb(244, 246, 248) → dark rgb(231, 237, 244) rgb(24, 32, 40)   OK
02-agent-architecture.svg        light rgb(27, 34, 43)   rgb(244, 246, 248) → dark rgb(231, 237, 244) rgb(24, 32, 40)   OK
03-rag-pipeline.svg              light rgb(27, 34, 43)   rgb(244, 246, 248) → dark rgb(231, 237, 244) rgb(24, 32, 40)   OK
04-edge-architecture.svg         light rgb(27, 34, 43)   rgb(244, 246, 248) → dark rgb(231, 237, 244) rgb(24, 32, 40)   OK
05-distributed-audio.svg         light rgb(27, 34, 43)   rgb(244, 246, 248) → dark rgb(231, 237, 244) rgb(24, 32, 40)   OK
06-media-pipeline.svg            light rgb(27, 34, 43)   rgb(233, 241, 253) → dark rgb(231, 237, 244) rgb(17, 37, 61)   OK
07-cost-resource-engineering.svg light rgb(27, 34, 43)   rgb(230, 244, 242) → dark rgb(231, 237, 244) rgb(13, 38, 36)   OK
08-era-timeline.svg              light rgb(27, 34, 43)   rgb(244, 246, 248) → dark rgb(231, 237, 244) rgb(24, 32, 40)   OK

all eight resolve two distinct palettes: True
```

One file, two palettes, verified per file rather than assumed from one.

## 3. Diagrams: readable at 1× and on mobile

Rendered widths measured inside a 390 px container (the mobile case) and a
960 px container (1×), using the presentation contract in
`diagrams/README.md` (`min-width:900px` in a scrolling wrapper):

```
container  390px -> {'container': 390, 'svgRenderedWidth': 900}
container  960px -> {'container': 960, 'svgRenderedWidth': 960}
```

Type is 15 px / 13 px at 1×, and 14.1 px / 12.2 px at the 900 px minimum —
arithmetic from the rendered width over the 960 viewBox. Scaled to the container
instead, the same labels would render at 5 px, which is unreadable; that is why
the wrapper is a requirement and not a styling preference.

## 4. Accessibility

Every file carries `role="img"`, `<title>` and `<desc>`. `desc` length per file:
219, 230, 285, 223, 193, 197, 260, 234 characters — a real alternative text, not
a filename. The manifest repeats each `desc` verbatim as `alt`, so the page and
the screen reader cannot disagree.

## 5. Code exhibits: verbatim copies

Each exhibit was produced by copying from the archive with `cp` or `sed -n`,
never by typing. Line counts as reported by `wc -l`:

```
36 01-actionscript-class.as
42 02-js-easing-core.js
27 03-php-encode-op.php
37 04-typescript-service-layer.ts
28 05-embedded-cpp-interface.hpp
33 06-nix-derivation.nix
212 total
```

`03-php-encode-op.php` is two copied regions joined by one marked elision
(line 20 of the file). Nothing else was altered.

## 6. Archive is not exposed

Path-shaped strings only — a mount point or a storage volume name would have to
appear for the archive to be reachable:

```
$ grep -rnE '/m[n]t/|storage_3[T]B' content/ || echo "no mount paths or volume names under content/"
no mount paths or volume names under content/
```

The bracket keeps the check from matching its own command line, so the result
above is the real result and not the file quoting itself.

No matches. The archive is not linked, named, or reachable from anything under
`content/`. Provenance is recorded as "private archive, path withheld" — the
words only, never the location.

## What could not be verified here

| Item | Why | Owner |
|---|---|---|
| Page weight of a real page | No template exists yet | Builder / Phase 2 |
| Lighthouse ≥ 95 / 95 | Needs a served page | Builder / Phase 3 |
| Client wall grid renders as deliberate | It is markup and CSS, which this phase must not write | Builder |
| Screenshots and recordings (7.4) | The console is Phase 5; staging it would be fabrication | Phase 5, then this phase |