Decisions and tradeoffs
Numbered markers index the same readable decisions below. On narrow screens, use the list. Summaries describe the accepted contract and portfolio integration; they are not verbatim historical quotations.
Playback ownership
- Question
- Who advances the sequence?
- Options
- Host-controlled state, or component-owned playback.
- Choice
- The package owns playback; the host supplies the scripted flow.
- Consequence
- Hosts get consistent controls, but version 0.1.0 does not offer fully controlled playback.
Bounded graph
- Question
- How much graph layout should the player solve?
- Options
- Arbitrary branching graphs, or a small ordered lane.
- Choice
- Two to six ordered nodes, with edges only between neighbours.
- Consequence
- The boundary keeps the model explicit; branching and automatic layout are outside this release.
Readable explanation
- Question
- How can a visitor follow a step beyond animation?
- Options
- Visual highlighting alone, or visual state plus authored text.
- Choice
- Supply a title and description for each step; show the current explanation with the graph.
- Consequence
- The host must write meaningful descriptions. The portfolio additionally provides a complete server-rendered trace outside its dynamically loaded player.
The portfolio’s complete trace is available on the architecture page.
Host styling
- Question
- How should the player fit a host site?
- Options
- Global style changes, or scoped styles and custom properties.
- Choice
- The package scopes its styles; the portfolio maps semantic tokens through its adapter.
- Consequence
- The host must maintain its token mapping and check contrast as themes change. This screenshot shows the light theme only.
The captures show the interface in English and in a light theme.
See the interface anatomy