Files
shard-wiki/research/260614-glamorous-toolkit-deep-dive/README.md
tegwick 25091dbd2e research: Glamorous Toolkit deep dive (moldable development); SHARD-WP-0004 T7
Moldable views (gtView) = open, type-keyed set of co-equal, computed
projections, none canonical = a moldable view registry refining the
projection model (T16). Lepiter live notebook over git files. Enrichment-
only (UC-47/48/54); no new UC. Marks T7 done.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-14 23:38:56 +02:00

34 lines
1.6 KiB
Markdown

# 260614 — Glamorous Toolkit (moldable development) deep dive
Date: 2026-06-14 · Source: **SHARD-WP-0004 T7**
## What this is
A deep dive into **Glamorous Toolkit** (GT, on Pharo): **moldable development** — cheap,
custom, **domain-specific views** (`gtView` methods) so any object explains itself through an
**open set of co-equal projections, none canonical** — plus **Lepiter**, GT's live notebook/
knowledge base (git-versionable JSON page files with live, inspectable code results).
## Why it matters
- Strongest prior art for **moldable, multi-view projection**: projection is not *a* view
but an **open, type-keyed set of co-equal, possibly-computed views, none privileged**
refines SHARD-WP-0002 **T16** and unifies replication-/derivation-/dimensional-/query-
projection under "many co-equal views."
- Generalizes ZigZag dimensional views (UC-47/48) and query/computed views (UC-54) into a
**pluggable view registry** keyed by content type (answers UC-55's open question on a
content-type registry).
- Reinforces **files-canonical, liveness-above, degrade-to-snapshot** (Lepiter files vs the
Pharo image; same boundary as Jupyter UC-84 / Squeak T6).
## Yield
- **No new UC** (design prior art, not a candidate shard — like the UseModWiki lineage dive).
- Enrich **UC-47, UC-48, UC-54**; links **UC-55, UC-83, UC-84, UC-79**.
## Contents
| Path | Role |
|------|------|
| `findings.md` | Moldable development & `gtView`, the Moldable Inspector, Lepiter, relation to ZigZag/query/derivation projection, INTENT mapping, UC disposition (enrichment-only), architecture notes, open questions |