Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

TelePulse: Bookmarks & Timeline Navigation

Named time markers (e.g., "First pickup", "HOS warning") with time offset from scenario start, optional camera position for map view, and jump-to-bookmark capability for...

Problem

Named time markers (e.g., "First pickup", "HOS warning") with time offset from scenario start, optional camera position for map view, and jump-to-bookmark capability for...

Capability

Named time markers (e.g., "First pickup", "HOS warning") with time offset from scenario start, optional camera position for map view, and jump-to-bookmark capability for...

How it works

  1. 1 Scenario bookmark/time-marker system with timeline navigation and quick jump capabilities.
  2. 2 Replayability and demo pacing improvements through deterministic timeline control.

Operational outcomes

  • Scenario bookmark/time-marker system with timeline navigation and quick jump capabilities.
  • Replayability and demo pacing improvements through deterministic timeline control.

Integration boundaries

  • Simulation Engine
  • HOS (Hours of Service) Simulation

Proof model

Feature-level proof

  • Bookmarks & Timeline Navigation scope is defined in product module catalog.

    verified

    docs/products/telepulse/product.md · Module Catalog > Bookmarks & Timeline Navigation

  • TelePulse simulation engine behavior is implemented as first-class simulation modules.

    partial

    docs/products/telepulse/product.md · Module Catalog > Simulation Engine

    Code: backend/services/telepulse/internal/modules/simulation

    Contract: proto/telepulse/simulator/v1

  • TelePulse simulation workflows are implemented in service runtime modules.

    verified

    docs/products/telepulse/product.md · Module Catalog > Simulation Engine

    Code: backend/services/telepulse/internal

    Contract: proto/telepulse/simulator/v1

Solution routes that reuse this feature

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (0).

This feature is currently not linked to a named solution route. Review this behavior directly, then validate continuity through adjacent solution and feature-map routes.

Continuity routes for this capability

Route-level continuity checks where this feature appears in product-pair workflows.

This capability is currently mapped in adjacent solution and continuity routes. Browse linked solution routes first, then return here when cross-route continuity is expanded.