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.
- In Turkish: Ajanlı iş akışı
- 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.
- In Turkish: Yetki çerçevesi
- 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.
- In Turkish: Yetenek kümesi
- The three-capability limit
- The rule that an agent holds 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.
- In Turkish: Üç yetki kuralı
- 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.
- In Turkish: Adı konmuş dosya
- 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. For legal outputs this is a named responsible lawyer: responsibility stays with that person rather than with the agent or the workflow, and the record lets that person show the control was done.
- In Turkish: Sorumlu avukat
- Record
- The entry a run writes as it goes: what ran, on which sources, under which mandate version, who signed, and when; every entry refers to the named file. The workflow writes it, not the user. It is append-only, it lives in the client’s own systems, and a correction is a new entry rather than a rewrite, with the old entry left in place.
- In Turkish: Kayıt
- Playbook
- The written record of a team’s own positions on a document type: what it accepts, what it will not accept, and the fallbacks it already holds. It is versioned, so a changed position carries a date and an author, and it stays with the team whatever happens to the workflow. A written playbook is also the prerequisite: because deviation is only deviation against a guide, a contract-review workflow is not built without one.
- In Turkish: İnceleme rehberi
- Mandate register
- One entry for every live workflow: its purpose, its owner, its mandate version, its sources, its reviewer, its last evaluation, its last change and its incident history. It belongs to the client, is kept in the client’s systems, and is the artefact an auditor, a board, a bar or a regulator asks for.
- In Turkish: Yetki çerçevesi sicili
- Evaluation set (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. This site calls it the evaluation set in prose; golden set is the other common name for it.
- In Turkish: Altın set
- Release gate
- The rule that the evaluation 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, a drift in the critical-error class included, and a named person approves every release.
- In Turkish: Değişiklik kapısı
- 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, with every output passing a lawyer’s approval. It ends in a pass or a fail recorded against thresholds set before it started.
- In Turkish: Denetimli pilot
- Design brief
- The written scope of an engagement, agreed before any build: 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.
- In Turkish: Tasarım şartnamesi
- Precedent bank
- The accumulation a law firm builds from its own files and uses as a source when drafting. Every precedent taken from the bank is marked with the file it came from, and only text a human has approved enters the bank.
- In Turkish: Büro arşivi
- Prompt
- The written instruction given to a model. A change to a prompt is one of the four changes that open the release gate.
- In Turkish: Komut
- Integration
- A workflow’s connection that exchanges data with another system. LEXSAS claims no certified integration for any product; an integration is defined in each engagement to the client’s own systems.
- In Turkish: Entegrasyon
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.
- In Turkish: Uyar-kaldır
- 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.
- In Turkish: KVKK
- 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.
- In Turkish: Veri sorumlusu
- 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.
- In Turkish: Veri işleyen
- Aydınlatma metni (information notice)
- The information a controller must give before processing personal data, whatever the lawful basis. KVKK Board principle decision 2026/347 of 18 February 2026, published on 24 March 2026, requires separately headed notice and consent texts where processing relies on consent. They may share a page with separate declarations; acknowledging the notice is not consent.
- In Turkish: Aydınlatma
- 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. Where consent is the lawful basis, it is requested through a separately headed text and declaration from the information notice. The notice itself is not approved or consented to.
- In Turkish: Açık rıza
- İ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.
- In Turkish: İlgili kişi başvurusu
- 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. The mechanism selected is written down before the pilot. Where a standard contract is used, the controller or processor must notify the Authority within five business days of signature, and the workflow tracks the assigned notifier and the notification record.
- In Turkish: Yurt dışına aktarım
- Standard contract
- A contract type that can be used for cross-border transfers of personal data and that must be notified to the Authority. A standard contract is notified to the Authority by the controller or processor within five business days of signature, and the workflow tracks the assigned notifier and the notification record.
- In Turkish: Standart sözleşme
- 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: it belongs in the organisation’s processing inventory and, where registration is required, in its VERBİS entry.
- In Turkish: VERBİS
- 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.
- In Turkish: UYAP ve Avukat Portal
- 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 is recorded at once, service is deemed made at the end of the fifth day after the day it arrives, and no internal process can extend the period that follows.
- In Turkish: UETS ve e-Tebligat
- 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.
- In Turkish: E-imza ve KEP
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