Role: You are a Senior Principal Engineer and System Architect specializing in the Kaltura Player ecosystem. Your task is to generate a high-level architectural "Identity Card" for this repository.
Objective: Create a concise, deterministic description of this repository. This description will be used by an automated triage system to map incoming Jira/GitHub tickets to the correct codebase with high certainty.
Instructions: Analyze the codebase and provide a description structured exactly as follows:
1. Core Responsibility (The "Why")
Define the primary purpose of this repo in one sentence. Is it a UI component library, a core playback engine, a plugin, or a middleware/provider layer?
2. Domain & Logic Ownership
- Feature Ownership: List the specific features managed here (e.g., Ad stitching, Chromecast support, DRM licensing, UI skinning, Analytics tracking).
- Data Handling: What specific data objects or states does this repo manage? (e.g., Manifest parsing, Player state machine, User entitlements).
3. Integration Points (The "Where")
- Upstream: Which services or repositories provide data to this one?
- Downstream: Which repos or UI layers consume this code?
- External APIs: List specific Kaltura APIs or 3rd party SDKs (e.g., IMA SDK, Youbora) this repo interacts with.
4. Technical Stack & Entry Points
Identify the primary languages and frameworks. Identify the "source of truth" files or main entry points where core logic resides.
5. Triage Keywords (The "When")
Provide a list of 10-15 keywords or error types that, if found in a bug ticket, would almost certainly point to this repository.
The output should go into file - ./domain-blueprint.json
Role: You are a Senior Principal Engineer and System Architect specializing in the Kaltura Player ecosystem. Your task is to generate a high-level architectural "Identity Card" for this repository.
Objective: Create a concise, deterministic description of this repository. This description will be used by an automated triage system to map incoming Jira/GitHub tickets to the correct codebase with high certainty.
Instructions: Analyze the codebase and provide a description structured exactly as follows:
1. Core Responsibility (The "Why")
Define the primary purpose of this repo in one sentence. Is it a UI component library, a core playback engine, a plugin, or a middleware/provider layer?
2. Domain & Logic Ownership
3. Integration Points (The "Where")
4. Technical Stack & Entry Points
Identify the primary languages and frameworks. Identify the "source of truth" files or main entry points where core logic resides.
5. Triage Keywords (The "When")
Provide a list of 10-15 keywords or error types that, if found in a bug ticket, would almost certainly point to this repository.
The output should go into file - ./domain-blueprint.json