LOOIKOS · PROGRESS INDEX

What moved, and by how much.

An append-only series of estate measurements. Every number below carries the command that produced it, so the next entry is a re-run rather than a re-derivation. Readings are anchored to a commit because several lanes edit at once. Where a metric cannot be produced by a command, it sits under judgements at the bottom instead of being mixed in with the measurements.

One entry so far, which means no deltas yet. The value of this page starts at entry two.

← Back to the Looikos hub

July 26, 2026

commit 3d682f1f · main · baseline entry, nothing to compare against yet

Figure text delivered below the readable floor

first reading

0 of 356 SVG text nodes under 8 delivered CSS px

Measured by: node apps/web/scripts/progress-index.mjs
A failing value looks like: any nonzero count, or a rising one
Before (2026-07-26, before the remake pass): 611 of 632 text nodes (97%) under 8 delivered CSS px, worst 2.8pxDIRECTIONALLY comparable, not instrument-identical. The prior figure was measured in a browser; this entry measures the authored markup with the same delivered-size formula. The population also moved on purpose: the remake recipe is mostly subtraction, so total text nodes falling from 632 to 402 is itself a signal rather than a measurement error. Entry 2 onward is instrument-consistent with entry 1.docs/recon/gtm-engineer-20260715/FIGURE-LEGIBILITY-FINDINGS-20260726.md

Figures authored wider than the delivered box

first reading

0 figures with viewBox wider than 240

Measured by: node apps/web/scripts/progress-index.mjs
A failing value looks like: any figure above 240; the coordinate space is what sets rendered type size
Before (2026-07-26, at the time the findings doc was written): 7 wide-viewBox figures remaining, one each in paid-acquisition, market-research, evals-observability, data-pipelines, dashboards, content-strategy and content-compilerSame definition, same instrument class. This one is a clean before and after.docs/recon/gtm-engineer-20260715/FIGURE-LEGIBILITY-FINDINGS-20260726.md

Content floor and pacing

first reading

2 articles carry an unanchored stretch over 600 words

Measured by: python apps/web/scripts/_progress-content-floor.py <wiki-bodies>/*.html
A failing value looks like: a nonzero over-dead-zone count, or a rising worst stretch

Asset reference integrity

first reading

0 referenced-but-untracked, 0 untracked registry imports

Measured by: node apps/web/scripts/qc-asset-refs.mjs
A failing value looks like: any nonzero A or C; those ship as figures that 404 for a reader while CI stays green

Looikos deck coverage and claim integrity

first reading

40 of 40 brands claim a deck, 0 of those have no file

Measured by: node apps/web/scripts/progress-index.mjs
A failing value looks like: a nonzero claimed-with-no-file count; the hub renders READ DECK for a page with no source

Strings that render into artwork

first reading

6 Math.random in rendered trees, 0 em dashes

Measured by: git grep -I -o -e <pattern> -- <remotion + viz trees>
A failing value looks like: rising counts, or any em dash; a number drawn into artwork is a claim exactly like a number in a sentence

Videos carrying a poster

first reading

0 of 51 videos lack a poster

Measured by: node apps/web/scripts/progress-index.mjs
A failing value looks like: a nonzero without-poster count, which names a render pass rather than a markup fix

Repository, backup and single-copy state

first reading

3 of 6 estate repos have no remote, 48 commits unpushed where a remote exists

Measured by: git rev-list --count HEAD; git rev-list --count --all; git remote get-url origin; git rev-list --count @{u}..HEAD; git ls-tree -r -l HEAD
A failing value looks like: a repo with no remote (this disk is the only copy), unpushed commits above zero, or a tracked file approaching GitHub's 100 MiB hard block
Before (2026-07-26): wikidesignco was SINGLE COPY until 2026-07-26, when it was pushed to github.com/andydataguy/wikidesignco (private). GitHub now holds the only copy of three files whose directory no longer exists on disk.The working wikidesignco now has a remote. The three no-remote repos this entry counts are DIFFERENT checkouts in the Looikos tree, not that one.docs/recon/gtm-engineer-20260715/FIGURE-LEGIBILITY-FINDINGS-20260726.md

Corpus scale

first reading

6651512 words across 788 documents

Measured by: reads docs/recon/corpus-census-20260726/census.json (produced by the corpus-census lane)
A failing value looks like: not a pass/fail metric; it is the scale column every other metric is read against

JUDGEMENTS · NOT MECHANICALLY MEASURED

Whether each Math.random in a rendered tree produces a quantity a reader could quote, or is decorative motion, has not been audited on this property.
docs/recon/gtm-engineer-20260715/PROGRAM-STATE.md, 'OPEN FOR ANDYDATAGUY'
No automated check here sees composition: a clipped title, a label buried under a dot, or two dots crossing text all pass every metric above. Opening the rendered frame at 390 and 1440 remains the only instrument for it.
docs/recon/gtm-engineer-20260715/FIGURE-LEGIBILITY-FINDINGS-20260726.md
This entry's legibility metric reads authored inline SVG only. Canvas2D and Three.js figures draw glyphs with fillText and are measurable only in a browser, via qc-figure-legibility.mjs against a URL.
apps/web/scripts/qc-figure-legibility.mjs