Skip to content
AJUTIA.

Glossary

The concepts, in plain terms

Concepts to understand the project. These definitions do not establish that a feature has been deployed.

Tenant

An organisation's logical space within a shared service. Data separation requires permissions and isolation tests.

Token

In authentication, an access credential that must be protected. In AI, it can also mean a unit of text used to calculate consumption; these are different meanings.

Gateway

An entry point that applies configured checks to requests. Which connections actually pass through it must be verified.

Core

The shared part of a system that coordinates rules and services. Its scope depends on the implementation.

RLS

Rules governing access to records according to the user and context. Both allowed and denied access need testing.

Model router

A component that selects a model using configured criteria such as capability, privacy and cost.

Quota

A consumption limit defined for a service. A counter alone does not guarantee that spending will be blocked.

Fallback

An alternative when a service fails, if configured and authorised. An uncertain result must be checked before repeating an action.

AI Regulation

Europe's risk-based AI framework. Applicable obligations depend on the system, its use and each actor's role.

Provider vs deployer

Different roles in developing and using AI systems. They must be determined by the specific activity, not just the trading name.

Vertical

An application adapted to the needs of a sector or activity.

Offline-first

A design that prioritises local features. It does not mean that every feature in an app works without internet.

Idempotency

A property that allows the same operation to be repeated without duplicating its effect. It requires a server-side mechanism; disabling a button is not enough.

This site uses its own technical cookies. We do not use advertising or third-party cookies. More information(Catalan only)