Skip to main content

Terminology

This page clarifies terminology used across the LiVi documentation.

Consistent terminology helps maintain clarity across technical, product and architectural discussions.

Platform​

LiVi is referred to as a platform rather than a single application.

This reflects its evolving multi-layer structure.

Product Layer​

The part of the system that directly interacts with users.

Example:

  • AI Scriptwriter interface

Billing Layer​

The system responsible for plan selection, payment flow and billing logic.

Example:

  • Pricing interface

Backend Access Logic​

Server-side logic responsible for determining user access state.

This includes entitlement validation.

Entitlement​

A backend record that determines whether a user has a certain level of access to the product.

Payment Order​

A stored record representing a payment event and its processing state.

Component​

A functional layer of the platform that represents a product or system module.

Example:

  • Scriptwriter
  • Video Editor
  • Pricing System

Infrastructure Layer​

A broader structural system that supports platform capabilities.

Example:

  • interactive systems
  • production workflows