docs: elmyra answered, and the site map lost a layer

TASK-36 said the load path had never executed. It ran 2026-08-11 —
LoadNanoappResponse decoded, success byte set, and six gauges came off a flat
baseline at 2502 and 2990 against a 2500 floor. Recorded with Casey's numbers
and the two things that would otherwise compress away: the margin carries
intent, and the proximity veto is a separate job from the threshold.

TASK-66 corrected. The shipped front page promoted ViewTop to a peer of the
substrate, the OS and the agent; the canonical map never agreed. Three layers
now, plus the delivery defects found by auditing served bytes.

docs/tasks/36-chre-nanoapp-host.md

@@ -203,6 +203,42 @@ the next piece of work) or a `deliver_message_from_host failed` with an errno.
 If the doorbell dies again on the load, THAT is a real signal about the load;
 if it dies without the drop-in, it is TASK-34.
 
+## 2026-08-11 — the load ran, and elmyra answered
+
+Casey's account the same evening, recorded as his evidence and not yet
+re-verified by a second observer:
+
+> Fifty-two bytes climbing back out of the DSP through HexagonFS … a root at
+> offset sixteen and a vtable at six. *Message type seven.* LoadNanoappResponse.
+> Transaction one … Byte forty-seven: one.
+
+So `LoadNanoappResponse` decodes, and the success byte is set — item 3 of the
+remaining work is done for the load path, and item 4 (load `elmyra`) has its
+unambiguous pass. The response was hand-decoded at offsets rather than through
+a generated reader; the verification discipline that caught the FlatBuffers
+padding bug above still applies to `NanoappMessage`.
+
+The squeeze itself produced numbers, against a baseline that had been flat:
+
+> Six gauges … 0.240, 0.295, 0.176, 0.359, 0.329, 0.342 … and the numbers came
+> up off that flat line: twenty-five-oh-two. Twenty-nine-ninety. Against a floor
+> I set at twenty-five hundred.
+
+Two observations worth keeping before they compress into "squeeze works":
+
+- Some squeezes barely cleared 2500 and some cleared it outright. The margin is
+  information — attenuation carries *how fast the flex released* and how much of
+  the squeeze was decision versus reflex. A bare threshold discards that.
+- A proximity veto already covers the pocket/tabletop case, so the 2500 floor
+  only has to separate intent from noise once "not reaching for me at all" is
+  ruled out. Those are two different jobs and they are correctly separate — the
+  same shape as §4 confidence versus §10 source health.
+
+**Not yet done:** the acceptance list below still wants "survives a cold boot as
+a unit" and "reaches the device as a package". Until those hold, this is a live
+rail on a running device, not a shipped capability — and nothing public should
+describe it as one. TASK-31's dial is still what a squeeze should open.
+
 ## Shape of the remaining work
 
 1. ~~**Message pump.**~~ Built — reader thread on method 4, send on method 5.

docs/tasks/66-souveraineai-overhaul.md

@@ -71,4 +71,37 @@ Owner: Rook, under Casey's direction. Casey took the site's identity decision: s
 - [x] `npm ci` + `astro build` green (31 pages), pushed to the forge and
       rebuilt from the merged tree on the server.
 
+## Correction, 2026-08-11
+
+The shipped front page mapped four layers — substrate, system, session,
+presence — which promoted ViewTop to a peer of Souveraine, SouveraineOS and
+Souvie. `~/Projects/AGENTS.md` has never agreed: viewtop owns the compositor
+the way the other `souveraine-*` repositories own their named components.
+Casey called it on sight. The map is now three layers, and ViewTop has its own
+front-page section carrying the 2026-08-05 tiling screenshot.
+
+Delivery defects found by auditing the served bytes rather than the repo, all
+fixed in `a584e6f` and `f41149c`:
+
+- nginx rebuilt directory redirects on port 80, so every internal link took a
+  plaintext hop before Cloudflare bounced it back. `absolute_redirect off` plus
+  trailing-slash hrefs.
+- Canonicals declared the slash-less form the sitemap does not list, and which
+  301s.
+- Every page but the homepage shared a 538-byte placeholder SVG as its
+  `og:image`, under `twitter:card=summary_large_image`. No platform renders SVG
+  cards. Replaced with a real 1200×630 built from the power menu.
+- The workbench photo shipped at 4080×3072 / 2.4M. Moved to `astro:assets`;
+  hashed filenames also close the trap where `immutable` froze a replaced image
+  at the edge for a year.
+- Fonts self-hosted (latin woff2, OFL, 181K). The site arguing for owned
+  infrastructure was blocking first paint on fonts.googleapis.com.
+- The two stock Starlight sample pages were live and in the submitted sitemap.
+- Repo links now read `docs/src/config.ts`, so the move to
+  gitea.caseytunturi.com is one edit. Two links cannot reach it: the YAML
+  frontmatter in `docs/index.mdx` and the citation in `pronoun-problem.md`.
+
+Still open: the site has no contact, hire, or funding path, and no dated
+activity signal. Audit at `~/souveraineai-audit-2026-08-11.html` §04.
+
 Connections: canonical map in `../AGENTS.md` §websites; empty.