tegwick
3d137c96b6
Consolidates the 8 computational/interactive-knowledge dives into one source/derivation/projection model on two axes (replication<->derivation, live<->snapshot); four computational page shapes; recommendation that executable content is in scope as a page-model+projection concern, out of scope as an execution platform (capability-gated, degrade to snapshot; no INTENT amendment). Flips SHARD-WP-0004 status: done. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2.0 KiB
260614 — The computational page model (SHARD-WP-0004 synthesis)
Date: 2026-06-15 · Source: SHARD-WP-0004 post-batch synthesis (T1–T8)
What this is
The acceptance-criteria synthesis for SHARD-WP-0004 — "the computational page model" — reading the eight computational/interactive-knowledge dives across each other and distilling them into one model: source is canonical; everything rendered/computed is a projection, placed on two axes (projection-kind: replication vs derivation; liveness: live↔snapshot), with a recommendation on an executable-content capability.
The answer to the carried question
Can a shard-wiki page be a live computational artifact? Yes — as a page-model + projection concern, not as an execution platform. Every system externalizes to a canonical source and treats the live/computed form as derived; shard-wiki recognizes computational content, attaches the source, and presents derivations as provenance- and liveness-marked projections, with execution as a gated capability (off by default, degrade to snapshot). No INTENT amendment required.
Key contributions
- One model:
(source, derivation rule, projection with provenance + liveness)covers all four computational page shapes (one-source-many-projections UC-83; notebook UC-84; program-as-page; live/temporal content). - Two axes for T16: replication vs derivation-projection (timing / multiplicity / continuity facets) × the live↔snapshot axis (bounded at the irreducibly-live far end by Strudel).
- One snapshot-provenance record reused for notebook outputs, renders, recordings.
- Hard boundaries: never host a kernel/runtime as store; image-is-not-a-store; never present a derivation without output→source provenance.
Contents
| Path | Role |
|---|---|
findings.md |
The source/derivation/projection model, the two axes, the four page shapes, provenance/reproducibility, the recommendation, the SHARD-WP-0002 fold-in, escalated open questions |