grafik 0.1.0-alpha.1

Living diagrams for executable product explanations
Documentation
# Scope

- **Status:** Active experimental contract
- **Kind:** Normative project scope
- **Authority:** Canonical for project purpose, first tracer, and non-goals
- **Owns:** What Grafik is, what the bootstrap proves, and what it does not claim
- **Does not own:** Module seams, event fields, rendering mechanics, commands, or proof procedure

## Purpose

Grafik is an open-source explanation system for seeded living diagrams and executable product
explanations. It is a visual practice and simulation contract, not a generic animation library or a
product-specific application.

A living diagram uses semantic events to evolve one spatial field around explanatory panels.
Published runs are seeded and replayable. Simulated and intentionally published recorded results
enter through one bounded semantic vocabulary before spatial evolution; neither source grants the
browser infrastructure authority. Product-specific meaning and data mapping, brand styling, browser
geometry, and accessibility remain in consumer adapters; Grafik owns the renderer-neutral scene tree
generated from bounded display content.

## First tracer

The first tracer proves one end-to-end path:

1. One Rust package owns the product and workspace root.
2. A browser reports two panel rectangles and selected edge ports.
3. A seeded simulation evolves an orthogonal sparse connector from hero to receipt.
4. The connector grows segment by segment and retracts from its leaf.
5. WASM returns renderer-neutral spatial events.
6. A shallow SVG adapter renders those events without crossing panel interiors.
7. Replaying the same input and seed yields the same event trace.
8. Reduced motion applies the final readable state without animated traversal.

## Result seam

The result tracer accepts one simulated or recorded final disposition and preserves it through the
public renderer-neutral trace. This is not a stable cross-product protocol, receipt parser, live
product client, or claim that a recorded result proves infrastructure truth.

## Receipt-scene tracer

The next vertical tracer generates one complete, renderer-neutral receipt scene from bounded content,
an explicit seed, one curated recipe, and hard budgets. Rust owns the content/layout tree, diagram
topology, style roles, effect targets, seeded pattern application, phase ordering, and interaction
script. The browser renders those roles, measures actual node rectangles and ports, and returns that
geometry for a complete timed trace.

“Rust-owned view” means a typed scene plan, not Rust-authored HTML, SVG, CSS, or DOM mutation. Receipt
content remains caller-provided data; Grafik does not parse product records or define product result
meaning. The standalone Grafik lab is the development and review adapter. A consumer product should
need only the generated WASM, two JSON calls, and its concrete renderer.

## Non-goals

- Generic animation framework, runtime plugins, or speculative package seams
- A second product showcase or live outcome transport
- Full-screen effects or effects that move readable content
- DOM access from Rust/WASM
- Remote gateway integration, hosted service behavior, or infrastructure work
- Browser credentials, infrastructure authority, or product signing keys
- A product-specific receipt schema, brand renderer, or source-level dependency on a consumer
- Stable public compatibility or production-readiness claims

## Exit condition

The bootstrap is complete when the documented default gate passes, the browser tracer can be
served locally, and review reports explicit residual risk. Visual polish and remote clients remain
future work.