GLOSSARY

The words on this site, defined

Every word below is used on this site in one sense only, and this is the sense. Where a term is defined by law rather than by me, that is said. Definitions are short on purpose, so that they can be quoted.

Last reviewed 5 September 2026.

The method terms

Agentic workflow: A legal workflow in which software does more than answer: it reads named sources, holds tools, takes steps and stops at a person. It is agentic because the steps are chosen inside a set frame rather than dictated one by one, and the frame is the mandate.
Mandate: The written frame an agent works inside, agreed before the run, in three parts: what it may read, what it may keep, what it may do. A mandate is versioned, is never wider than the matter needs, and is enforced in configuration rather than in an instruction.
Capability set: The concrete list of tools, sources and permissions that gives effect to a mandate. Where the mandate is the sentence, the capability set is what is actually switched on.
The three-capability limit: The rule that an agent should hold at most two of these three within one run: access to private client data, exposure to content nobody in your organisation wrote, and the ability to act or send something outside the workflow. Where all three seem necessary, the run is split into stages or a person stands between them.
Named file: A matter with a type, an owner, a clock and a place in a queue, created before any work starts. Loose material is bound to a named file before an agent reads it, and every record entry refers to the file.
Reviewer: The person named before the pilot who signs an output and answers for it afterwards. Review depth follows how much an output matters and how hard it is to reverse, not whether it happens to leave the team.
Record: The entry a run writes as it goes: what ran, on which sources, under which mandate version, who signed, and when. It is append-only, it lives in the client’s own systems, and a correction is a new entry rather than a rewrite.
Golden set: A set of examples from the client’s own matters, with the right answer recorded by the lawyer who would otherwise do that work. It starts small, grows with the failures that sampling finds, and carries a version number.
Release gate: The rule that the golden set must be re-run and must pass before any change to a model, prompt, retrieval source or connector reaches live use. A failing gate stops the change, and a named person approves every release.
Supervised pilot: The first stage of every engagement: one workflow, one measure agreed in advance, a named reviewer, a fixed end date, and nothing running unattended. It ends in a pass or a fail recorded against thresholds set before it started.
Design brief: The written document produced before anything is built: stages, mandate, reviewer, record format, measure, data handling and exit terms. If a question is not answered in the design brief, it is not settled.

Türkiye: data protection, courts and service

Notice and takedown: The process by which a platform receives a complaint about content and decides whether to remove or block it, within a period set by law. In Türkiye the core regime is Law No. 5651, and the operational point is that the clock starts with receipt, not with attention.
KVKK: The Turkish personal data protection authority and, in common use, the Turkish data protection law itself. Its requirements sit in the design brief of any workflow that touches personal data.
Veri sorumlusu (data controller): The organisation that determines the purposes and means of processing personal data, and that answers to KVKK for it. In a LEXSAS engagement this is always the client, never LEXSAS.
Veri işleyen (data processor): A party that processes personal data on the controller’s instructions. Which role each participant in a workflow holds is decided and written down before the pilot, not assumed.
Aydınlatma metni (information notice): The notice a controller must give data subjects about processing. A KVKK Board principle decision of 18 February 2026, published in the Official Gazette on 24 March 2026, requires it to be a separate document from the consent text.
Açık rıza (explicit consent): Consent that is specific, informed and freely given, and one of several lawful bases rather than the default one. Under the same 2026 principle decision it must be collected separately from the information notice, with its own heading and its own checkbox.
İlgili kişi başvurusu (data subject request): An application by an individual exercising rights over their personal data, which a controller must answer within the period the law sets. It is one of the queues the compliance operations workflow is built for.
Yurt dışına aktarım (cross-border transfer): The transfer of personal data outside Türkiye, lawful only through a mechanism the legislation recognises, such as an adequacy decision, a standard contract or an undertaking. Where a standard contract is used, the notification duty and its period sit with the controller.
VERBİS: The Turkish data controllers’ registry, in which registered controllers record their processing activities. An AI workflow that processes personal data is an activity like any other, and it belongs in the entry.
UYAP and the Avukat Portal: The Turkish national judicial information system and the portal through which lawyers work with files, hearings and enforcement. LEXSAS workflows are designed to respect its deadlines and outputs, and claim no integration with it.
UETS and e-Tebligat: The national electronic notification system through which formal service is made in Türkiye. For a workflow it matters as a clock: an arrival there starts a period that no internal process can extend.
E-imza and KEP: The Turkish qualified electronic signature and the registered electronic mail system. Where a workflow output has to be signed or served formally, it lands in these rather than replacing them.

Each of these words is used in the operating standard in the sense given here, and on each of the eight workflow pages. The data terms are worked through on the security and data page. Get in touch