Taleem Browser Engine

The Taleem Browser Engine is an index-based slide navigation engine.

It renders exactly one complete slide at a time and moves strictly by explicit slide index.

The browser engine does not know about time, progression, or playback.

What the Browser Engine Does

• accepts a valid deck-v1 Taleem deck
• renders one full slide at a time
• selects slides by numeric index
• provides deterministic, manual navigation

What the Browser Engine Does Not Do

• track or evaluate time
• partially reveal slide content
• interpret showAt values
• animate, delay, or sequence items
• guess author intent

These responsibilities belong to other layers of the system.

Public API

The browser engine exposes a single factory function.

import { createTaleemBrowser } from "taleem-player";

const browser = createTaleemBrowser({
  mount: "#app",
  deck
});

This creates an index-driven controller over a validated deck.

Browser Instance API

{
  currentIndex: number,

  next(): void,
  prev(): void,
  goTo(index: number): void,

  getCurrentSlide(): Slide,
  getSlideCount(): number
}

Navigation Model

Navigation is explicit and manual.

Calling a navigation method immediately replaces the currently visible slide with the target slide.

No intermediate states exist.

Mental Model

Which slide should be visible right now?

The browser engine answers this question directly, without evaluating time or state history.

Relationship to Player Engine

The two engines serve different, non-overlapping purposes.

Browser Engine moves by slide index, not by time.

• Browser Engine selects slides explicitly
• Player Engine reveals content progressively

The browser engine is not a preview mode of the player, and the player is not a timed version of the browser.

Failure Mode (By Design)

If slide indices are invalid:

• navigation may fail
• no slide may be rendered

These failures are intentional.

The browser engine does not guard against invalid navigation, because doing so would hide application-level errors.

Stability

The Browser Engine API is stable and frozen.

Internal optimizations may continue, but public behavior will not change without a schema version bump.