EUMOSA Dictionary

A permanent Enterprise-ready subcheck asking whether public content can be crawled, understood and cited correctly, whether interactive controls have clear semantics, and whether private data is reliably isolated.

A projection layer that turns approved public EUMOSA canonical data into machine-understandable public semantics for search and AI. It is not a second master database and cannot bypass private Workspace permissions.

The shared workspace where a brand team creates, maintains and uses brand master data, content, store models, items, expansion capabilities and permissions.

EUMOSA’s shared AI work assistant. It understands context through the current function, canonical master data, permissions and relevant memory rather than isolated bots on each page.

A data-loss protection layer for editable Workspaces combining dirty-state tracking, browser-local draft auto-save, leave guards and explicit canonical Save. Local Draft never replaces formal Save.

Every EUMOSA function is reviewed for Enterprise-ready, Finance-ready, Evidence-based and Learning-ready qualities.

EUMOSA Global Components own their complete normal, hover, active, focus, disabled, responsive and readable-contrast styling in the global layer and do not rely on any feature Page CSS to render correctly.

EUMOSA Dense Table/List Workspace page-level actions default to a right-side Action Zone: Primary is right-most, Danger sits to its left with danger styling, Secondary flows further left, and the right-most table column is normally Edit/Action.

The W3C JSON-based Linked Data format. EUMOSA can use it to expose machine-readable semantics for Brand, Item, Course, Credential and Dictionary facts already visible on public pages.

Uses Valid From and Valid To to define when data is effective instead of simply overwriting history.

EUMOSA Unique Identifier. A permanent, semantics-free identity assigned to a canonical EUMOSA record in XXXXX-XXXXX format. It does not encode Item, Brand, Branch, Category or other classification.

The authoritative master record EUMOSA recognizes for an entity. ERP, POS, websites and import files map to it instead of each becoming a competing truth.

Allows a lower scope to use its own permitted value without changing the canonical identity. Governance rules explicitly define what may and may not be overridden.

The level at which a record applies, such as Global, Brand, Market, Store Model or Branch.

The formal rule that identifies which source is authoritative for a type of data, preventing Brand, Branch, ERP and channels from keeping conflicting answers.

Creates formal versions for data that must retain history and traceability instead of erasing the previous state.

A Brand-owned reusable attribute specification containing name, optional code, Attribute Class, Value Type, optional default UOM and order.

The user-facing business Item code owned by the Brand. It remains unique within the Brand and, once assigned, stays reserved in that Item’s Code History instead of being reused for another Item. It may drive daily communication, file finding and media naming without replacing permanent EUID identity.

An intrinsic Item characteristic primarily intended for user-facing reading, product content and presentation, such as colour, material or a fixed sensory description; it excludes per-sale sweetness, ice, size and topping choices.

The Item data domain for intrinsic, fixed or descriptive characteristics. it is fully independent from Product Option: Classification organises Brand shelves, Attribute describes the Item itself, and Product Option handles choices made again for each purchase.

The system-level classification that describes what an Item fundamentally is, such as Raw Material, Semi-finished, Menu Product or Packaging Material.

An Item characteristic intended for measurable, verifiable or technical use, commonly represented with typed Number values and UOM.

One of the eight Item Data Domains. It owns user-facing Item content such as multilingual formal name, short name, descriptions, marketing copy and media relationships, separately from permanent identity such as EUID.

A source media file owned by the Brand and registered by EUMOSA. The physical file keeps a user-readable path and filename while Asset ID, checksum and Item Media Relation manage use and traceability.

A translation workspace that uses the Default Content Language as the source for Item Formal Name, Short Name, Product Summary and Product Introduction. It fills only blank target fields, preserves existing manual content, and records translation state and source language.

A display URL version value derived from the current file identity so browsers fetch updated media even when the user-readable source filename intentionally stays unchanged.

The sales-layer workflow that turns an existing Item into sellable configuration. Products / Menu creates the Sellable Offering relationship, followed by Product Options, Pricing, Sales Scope / Channels, and Listing Schedule / Availability. Data dependency follows the same order as navigation.

An Item promoted into the sales layer as something that may be sold or served on a menu. EUMOSA stores a Sellable Offering relationship keyed to the original brand_item_id / EUID instead of creating a second Product Master.

Indicates whether the Products / Menu step is still Draft or Ready. Ready means the Item may proceed to Product Options; it does not mean currently published, available or sold in any channel.

A Product Option that records how the order is chosen without requiring each value to have its own Item Master record.

An optional benchmark pack for the TWEU example Brand that creates seven common international tea-chain Product Option definitions: SIZE, TEMPERATURE, MILK_TYPE, TEA_BASE, TEA_STRENGTH, SWEETENER_TYPE and CREAM_TOPPING. It creates only missing codes, does not overwrite existing data, does not auto-assign options to Products and never guesses Item Master links for Material-linked values.

A Product Option whose leaf choices represent real consumed/added ingredients or semi-finished items and can therefore link to Item Master for Inventory, Costing and Recipe / Production. Authoring may continue while links are completed progressively.

The optional middle layer between a Product Option and its Option Values. In TOPPING → POPPING → PASSION, POPPING is the Option Category while PASSION is the final Option Value. Saved categories use archive/restore rather than hard delete so historical and ERP/BOM relationships remain traceable.

An operational relationship between a Material-linked Product Option Value and a real ingredient/semi-finished Item Master record. It answers which Item is actually represented/consumed by the option; it does not control whether that option is offered on a Product or its Price Adjustment, which remain Apply Product Options responsibilities. The central workspace uses Material-linked List First. A single record is handled from its actionable Item Link Status; Quick Batch selection can narrow candidate Items by Classification/search and Smart Match v3 works inside the current Classification/search candidate scope, can stage unlinked and suspicious relationships automatically when nothing is preselected, proposes only unique exact Item Code or name matches from Raw Material / Semi-finished candidates, and separately explains link quality before an explicit Save current links. Manual-only view focuses unresolved exceptions. Progressive Save commits only rows that currently have a valid target Item and leaves unresolved rows pending. The Quick Link Workspace ? exposes the same contextual guidance; selected rows/candidate Items/Smart Match proposals are unsaved work protected by Local Draft, while Classification/search alone are passive filters. Choice Only values are excluded. The standard maintenance ladder is single record → quick batch → Smart Match → Excel Bulk Import.

The amount added to or subtracted from a product base price for an option value. Zero means no change, positive increases price and negative decreases price. It belongs to sales configuration, not Item Attribute.

A reusable independent Brand-level sales-choice definition. User-facing hierarchy is Product Option → [Option Category] → Option Value, where Option Category is optional. A Product Option owns a stable code, multilingual labels, Input Type, Option Nature, Selection Rules, optional Brand Media and Sort Order. Structure is derived from actual relationships rather than manually duplicated. Internal data may still use Group / Subgroup / Value terminology.

The relationship and configuration that applies a Brand-level Product Option to a specific eligible sellable Item. It controls enabled values, default and Price Adjustment. an eligible Item can be selected even before a Sellable Offering exists; first save creates only a Draft offering relation without copying definitions, duplicating the product master or changing the Item EUID. the Assignment Workspace main page uses a List First Dense Table showing Image, Item Code, Product/Menu Name, Applied Options, Item Links Needed, Status and Edit; Item Links Needed counts only enabled Material-linked leaf values without a valid Item Master link; Edit opens the canonical Item Workspace Product Option tab. Hierarchical options support expand/collapse, while direct-input types store only assignment-level required/optional and sort settings until POS / Order Runtime renders the input control.

The transaction-configuration domain that describes what is chosen for a sale. A Product Option may have zero, positive or negative price adjustment and does not replace Item Attribute, Variant / Separate Item or Recipe / Production Mapping.

Classifies a Product Option as Choice Only or Material-linked. It is not a price classification; it answers whether the choice represents real material consumption/addition.

Indicates whether a Product Option currently uses a single-level or three-level structure. It is derived from actual relationships rather than manually duplicated: direct Option Values mean single-level; Option Categories with their Values form the three-level structure. Structure is independent from Product Option Nature.

A workspace for multilingual Product Option, Option Category and Value display text. the Default Content Language can be used as the one-click translation source; automatic translation fills blank target fields only, preserves existing manual text, and lets users review/edit/save one language at a time. Codes are language-neutral and are not translated.

The final orderable value selected by customer or staff and recognized by POS / kitchen. It may live directly under a Product Option or under an Option Category. Product Option Value ID is the permanent internal identity while Value Code is a Brand-defined editable business code. A real ingredient/semi-finished relationship is handled through Option Item Link, either centrally or directly from the Option Value editor Item Link tab. Option Value lifecycle can be archived/restored without deleting the linked Item.

Maps selected Product Options to actual production instructions such as ingredient quantities, machine programs or preparation steps. It does not define the sales choice itself and does not belong in Item Attribute.

When a difference creates a distinct SKU, GTIN, barcode, inventory, procurement, cost or permanent product identity, it should not be represented only by Product Option; use a Variant or Separate Item.

A Brand-defined business classification used to organize Items. Categories may be hierarchical and one Item may appear in several categories; Category is not Item Type.

A classification system defined by a Brand or connected system. EUMOSA allows multiple schemes to coexist and an Item may belong to multiple classifications.

The stable base unit of measure for an Item. Purchasing, recipe, inventory and sales may use different units linked through formal conversions.

Bill of Materials. Describes the materials, quantities and version that make up a semi-finished, finished or menu item, including multi-level structures.

A materially different operating or food-service model. A separate Store Model is warranted when products/menu, process, equipment, staffing, space or regulatory conditions materially differ.

A canonical event that translates real business activity into accounting rules, journal entries and general-ledger outcomes.

The canonical financial classification profile attached to an Item. It stores classes such as Revenue, COGS and Tax Product Class rather than hard-coding one GL account or tax rate.

Important functions share one knowledge structure across definitions, Help, sources, examples, tool practice, common mistakes, knowledge checks and practical tasks.

EUMOSA links Learning Topics, objectives, practices, verification rules, evidence and progress into one competency pathway. Academic and Cultivation views change presentation only; they do not duplicate learning content or progress.

Presents the same Learning & Competency Graph using formal education and enterprise-training terminology: course modules, learning objectives, practical assessment, competency evidence and completion.

EUMOSA reads actual platform results and applies repeatable deterministic rules to assess completion automatically while preserving competency Evidence and Progress; since learners do not trigger a separate Verify action.

Presents the same curriculum and competency data through immersive cultivation terms such as core methods, arts, manuals, practice, automatic assessment, understanding and exit from seclusion. The game experience does not alter formal learning outcomes or Evidence.

A platform competency expressed as a core method, real practice, automatic deterministic assessment and Evidence. The system reads current results and updates Progress without requiring the learner to repeat the work through a separate verification action. Foundation arts build Qi Refining; completing the required set establishes Foundation before star-level progression.

EUMOSA Course View and Cultivation View are different presentation experiences over one Learning & Competency Graph, Progress and Evidence state; the same competency cannot be complete in one view and incomplete in the other.

An automatic deterministic practical assessment that reads real Product Option definitions, hierarchy, option semantics, product assignments, Item Master links and multilingual content as competency Evidence.

The principle, purpose, definition and decision logic behind a function. Understand why it works before practising the art.

Organises cultivation arts by Track, Realm and Chapter. Each art owns its core method, real practice, automatic assessment rules, Evidence and Progress, while the map shows passed, criteria-met, in-practice and prerequisite states.

Since the manual Verify action is retired. The system reads real work for the specified practice, compares it with disclosed completion criteria, updates Progress automatically and records Evidence. Historical Attempt records are retained but no new learner-triggered attempts are created.

A credential record of assessed learning outcomes acquired through a small volume of learning. EUMOSA connects outcomes, practical assessment, evidence, awarding body, quality assurance, portability and stackability in one credential record.

Formal master data defining what a credential proves, who awards it, assessment, workload, quality assurance, stackability and external mappings. It is separate from the learner-specific award record.

Transparent rule that determines when a learner qualifies for a credential. It may reference verified Practices, completed Learning Outcomes, Assessment Evidence or other formal competency conditions.

State in which a learner satisfies the credential award rule and required data readiness, but the actual credential award record has not yet been issued.

Europass common data model for qualifications, learning opportunities, credentials and accreditations. EUMOSA reserves mappable credential fields, while ELM-ready does not mean EU or Europass accreditation.

Typical estimated learning time needed to achieve a set of learning outcomes. It transparently describes learning volume and is not the individual learner actual time. Providers not using ECTS may describe it in estimated hours.

Europass verifiable native digital learning credential format, which may include micro-credentials and uses an electronic seal to support origin and integrity verification. EUMOSA preserves an EDC-ready data boundary without claiming completed EDC issuance.

The learner-specific award record created when a credential is actually issued. It preserves Credential UID, learner identity reference, issue date, learning outcomes, workload, assessment, quality assurance and evidence snapshots.

EUMOSA provides a no-login public verification entry. Third parties may enter the exact Credential UID or use an opaque verification token shared by the learner to confirm the Learner Award lifecycle status and SHA-256 payload integrity. Public results mask learner personal data by default.

The lifecycle result of a credential at verification time. EUMOSA evaluates Credential Status such as VALID, EXPIRED, REVOKED or SUSPENDED separately from payload integrity: an unchanged record does not automatically mean the credential is currently valid.

Policy in the Credential Specification defining when an award becomes valid, whether it needs an expiry date and whether advisory refresh guidance applies. EUMOSA foundational credentials default to no_expiry; fixed validity is reserved for genuinely time-sensitive competencies.

An advisory refresh date that does not itself change Credential Status. It suits learning that evolves over time without justifying automatic invalidation of an older award. After the recommendation date, the credential may remain VALID unless the specification defines hard expiry or the issuer changes its lifecycle status.