Terminology Guide
Why this guide exists
The Zaqenimorux system uses a specific vocabulary to describe its components and processes. Some of these terms have meanings within the platform that differ from their everyday usage, or that are more precise than a general reading might suggest. This guide is intended to help prospective and current users understand what these terms mean in the context of the platform, so that descriptions of the system's functions can be understood accurately.
Terms are listed in the order in which users are likely to encounter them, rather than alphabetically, to reflect the sequence of a typical introduction to the platform.
Core platform terms
Information-organisation system
This is the general term used to describe what Zaqenimorux is. An information-organisation system is a digital environment designed to receive, arrange, and present structured content in a form that users can navigate and review. It is distinct from a file storage system, a communication tool, or a general-purpose productivity application. The defining characteristic of an information-organisation system is that it imposes a defined structure on the content it holds, rather than storing content in an undifferentiated way.
Category
A category is a named grouping within the Zaqenimorux system that holds related items. Categories are defined by the operator and reflect the logical divisions appropriate to the information the system contains. A category can contain sub-categories, allowing for a hierarchy that ranges from broad groupings at the top level to specific sets of records further down. Users navigate the system by moving through the category hierarchy.
Classification
Classification is the process of assigning an item to a category. When information enters the Zaqenimorux system, it undergoes a classification step in which its characteristics are assessed and a category is selected. The classification process in Zaqenimorux uses a combination of rule-based logic and AI-assisted analysis. Classification decisions are not always final: users with appropriate access can view the classification assigned to an item and request a review if they believe it is incorrect.
Record
A record is an individual item of information within the system. It is the basic unit of content in Zaqenimorux. Each record belongs to a category and has a set of fields that hold its identifying and descriptive information. The structure of a record depends on its type and the category it belongs to. Users interact with records through the summary and detail views described on the functions page.
Classification engine
The classification engine is the component of the Zaqenimorux system that carries out the automated classification of incoming information. It analyses the characteristics of each item, compares them against the existing category definitions, and proposes or applies a classification. The engine is designed to reduce the manual effort involved in categorising large volumes of information, but it does not replace human review entirely. Its outputs are subject to oversight and correction through the platform's review process.
Interface terms
Summary view
The summary view is the default display when a user enters a category. It shows a list of the records within that category, with a selection of key fields displayed for each one. The summary view is designed for quick scanning and navigation: users can assess the contents of a category and select a specific record to examine further without loading the full detail of every item. The fields shown in the summary view can be adjusted through display preferences.
Detail view
The detail view shows the complete content of a single record. It is opened by selecting a record from the summary view. The detail view presents all available fields for the record, arranged in a structured layout appropriate to the record type. Users can use the navigation controls within the detail view to move to adjacent records without returning to the summary view.
Contextual navigation panel
The contextual navigation panel is the part of the interface that shows the user's current location within the category hierarchy and provides quick links to related areas. It updates as the user moves through the system. On the summary view, it shows the current category and its parent categories. On the detail view, it shows the category the current record belongs to and may show related subcategories.
Display preferences
Display preferences are settings that each user can adjust to change how information is presented to them. They do not affect the underlying data or the classification structure; they affect only the visual presentation of the interface for that user's session. Common display preferences include the sort order of records in a category, the fields visible in the summary view, and whether certain panels are shown by default.
Access and support terms
Access level
An access level is a designation that determines what a user can see and do within the platform. Different access levels provide different combinations of permissions: for example, a standard user can review records and submit enquiries, while a more elevated access level might allow correction requests, export functions, or visibility of additional categories. Access levels are assigned by the operator when access is established and can be revised through discussion with the support team.
Access request
An access request is a formal submission by a prospective user asking to be granted access to the Zaqenimorux platform. It is submitted through the contact form on this site and reviewed by the support team. An access request is not a guarantee of access; it initiates a review process in which the team assesses whether the described intended use is consistent with the scope of the platform and the access arrangements available.
Enquiry
An enquiry is any question, request, or comment submitted by a user or prospective user through the contact form on this website, or through the integrated enquiry tool within the platform (if applicable). Enquiries are reviewed individually and addressed through the email address provided by the submitter. The term is used deliberately to avoid implying a specific type of request; an enquiry may relate to access, a specific function, a classification decision, or a general question about the system.