coulomb/shard-wiki
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

research: Processing / p5.js deep dive; SHARD-WP-0004 T4

Browse Source 
Program-as-page rendered live at view time (no cached output). Adds
materialization-timing (ahead-of-time vs view-time) + continuity
(one-shot vs continuous) facets to the projection model; execute-in-viewer
= capability+trust. Enrichment-only (UC-54/55). Marks T4 done.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-06-14 23:57:57 +02:00
parent 7fb90219b5
commit b676579407
6 changed files with 172 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
spec/UseCaseCatalog.md
View File

@@ -2486,6 +2486,30 @@ batch's spectrum). **No new UC.** Architecture logged for `SHARD-WP-0002` (T14/T
image-is-not-a-store binding boundary (export→files only); a live↔snapshot axis on every
projection.
### processing mapping
(Enrichment dive — **no new UC**; design prior art. Source: the **Processing deep dive**,
`research/260614-processing-deep-dive/findings.md`.)
| Processing mechanism (findings §) | Catalog UC / thread |
|-----------------------------------|---------------------|
| Sketch = program-as-page; presentation = view-time live render (§1) | UC-54 / UC-55 (enriched) |
| Render = derivation-projection run **in the viewer, continuously** (§1, §2) | links UC-83 (view-time variant) |
| No cached output; continuous/interactive → static = snapshot frame only (§2) | links UC-84, live↔snapshot axis |
| Client-side execution = capability + trust/sandbox surface (§2) | links UC-35 |
Note: Processing / p5.js is the cleanest **program-as-page** case — the whole page is a
program whose **presentation is its running output, rendered at view time** in the browser,
with **no cached output** (contrast notebooks UC-84). It adds two facets to the projection
model: **materialization timing** (ahead-of-time CDF/static vs **view-time** sketch render)
and **continuity** (one-shot vs **continuous/interactive**); a continuous artifact's only
static form is a **snapshot frame/recording** on the live↔snapshot axis. "Execute/render in
the viewer" is an explicit **capability with a trust/sandbox** sub-concern. **Boundary
recorded:** shard-wiki is **not a sketch runtime** — default attach the **source** + offer a
captured snapshot/recording; live in-viewer rendering is gated. **No new UC.** Architecture
logged for `SHARD-WP-0002` (T12/T15/T16/T11): program-as-page (source-canonical/render-
derived), materialization-timing + continuity facets, view-time-execute capability + sandbox.
---
## Open questions