_edited.png)
TECHNICAL ARCHITECTURE
How Chraimus Is Structured as a Context-First Business Atmosphere Platform
Chraimus is built around structured business data, venue-point mapping, content profiles, rights-documented content, explicit rules, weighted scoring, device authorization and controlled terminal playback.
TECHNICAL CHALLENGE
Business Music Requires More Than Playlists
Chraimus addresses the technical gap between simple playlist playback and structured, context-driven audio management for different business environments.
CHALLENGE
01
Playlist Logic Is Not Enough
A playlist can play content, but it cannot apply business type, venue point, scenario, time, crowd setting or defined operational rules.
CHALLENGE
02
Different Points Need Different Rules
A lobby, spa, gym, bar, restaurant, store or salon may require different atmosphere, energy, tempo, vocal mode, language and timing rules.
CHALLENGE
03
Manual Selection Breaks Consistency
When music decisions depend on staff, the business atmosphere can change from shift to shift and lose brand consistency.
CHALLENGE
04
Content Suitability Must Be Structured
Business-use content requires source and rights documentation, structured metadata, contextual matching, acceptance checks and controlled publishing before it becomes available in a venue environment.
SYSTEM OVERVIEW
A Modular Platform Built Around Business Context
The system connects companies, venues, points, devices, access rules, content profiles, approved content pools and controlled playback into one structured architecture.
SYSTEM
01
Company Layer
The platform starts with the business entity and supports venue, point, device, access and operational configuration within one central structure.
SYSTEM
02
Venue and Point Layer
Each venue can be divided into functional points such as lobby, bar, spa, gym, restaurant, retail area or salon, with point-specific context and playback rules.
SYSTEM
03
Context Profile Layer
Each point can follow a structured profile that defines atmosphere, energy, tempo, vocal mode, language, scenario, time and crowd logic.
SYSTEM
04
Terminal Layer
The terminal presents approved, point-relevant content through a simplified business-side playback interface according to the assigned point and active rules.
DATA FLOW
From Content Source to Terminal Playback
Content moves through a structured flow: source and rights documentation, metadata classification, rule-based matching, review, publishing and point-based terminal delivery.
FLOW
01
Content Source Preparation
Rights-documented content may be supplied by approved music production partners according to Chraimus technical, metadata and business-use acceptance criteria.
FLOW
02
Metadata Classification
Content is organized with structured metadata such as venue point, scenario, time, crowd setting, energy, tempo, vocal mode, language, genre and intended usage context.
FLOW
03
Review and Publishing
Content may remain in REVIEW during preparation and validation, but only content approved as PUBLISHED becomes available in the MVP demo or a future live environment.
FLOW
04
Point-Based Delivery
PUBLISHED content is delivered to the terminal according to the assigned venue point, active scenario, time settings, crowd setting and defined business rules.
TECHNICAL MODULES
The Core Components Behind the MVP
Chraimus combines business administration, content data management, rule-based matching, device authorization, terminal playback and the Chrayer protected playback path into a connected technical system.
MODULE
01
Admin Management
Admin structures manage companies, venues, points, devices, staff access, permissions and operational configuration from a central layer.
MODULE
02
Content Data Management
The content layer organizes source information, rights documentation, technical metadata, business-use fields, review status and publishing readiness.
MODULE
03
Rule-Based Matching
The current MVP uses structured metadata, explicit rules, contextual filters and weighted scoring to retrieve and order relevant content. There is no AI decision layer in the current MVP.
MODULE
04
Venue Terminal
The terminal delivers PUBLISHED content to the assigned business point through a controlled and simplified playback experience.
DEMO CONTROL
A Controlled Environment for Startup Review
The demo architecture keeps review data stable while showing how PUBLISHED point-based content pools are delivered through a controlled terminal experience.
DEMO
01
Demo Strict Mode
The MVP demo uses strict logic so selected review data, approved scenarios and point-based content pools can be shown in a stable and controlled way.
DEMO
02
Status-Based Control
Content availability is controlled through REVIEW and PUBLISHED status logic. Only PUBLISHED content becomes available for controlled demo use.
DEMO
03
Point-Based Content Pools
The demo environment limits visible content by venue point, scenario and slot so each terminal view remains relevant to the selected business context.
DEMO
04
Chrayer Protected Playback
Chrayer has been developed to application-certificate readiness and is designed to support encrypted local music storage, authorized playback and controlled offline operation. Application signing and commercial distribution will be completed after the Estonian company is incorporated and the required company certificate is obtained.