Lithi Glossary

approved Mac task

A clearly defined network task that policy allows an eligible Mac to run.

When to use: Use for approved, non-private work another trusted Mac may handle. Never use it for private relationship work.

Also called: approved shared work, eligible shared work

batch

A grouped request made from many independent compatible tasks that Lithi can quote, route, run and check together.

When to use: Use when explaining grouped work. A batch still requires independent tasks and execution-equivalent checking.

battery protection

A rule that pauses or limits optional work to protect battery level and battery use.

When to use: Use when explaining why optional Mac work pauses or yields.

bulk work

A large amount of similar work that does not need the frontier agent to reason through every item itself.

When to use: Use for repetitive work suitable for independent execution. Do not imply every large request is safe, eligible or parallel.

consensus review

Independent approved checks agreeing strongly enough for the defined task.

When to use: Use sparingly in technical-public copy and explain the actual review rule.

device attestation

Evidence that a device and app match the security state required for a task.

When to use: Use in technical security and routing documentation with the mechanism and limits named.

device capability

A verified feature or resource a device can safely provide, such as memory, model support or an approved tool.

When to use: Use for device eligibility, not human skill.

distributed Mac fleet

The member-owned, opted-in Apple-silicon Macs eligible for approved connector-network work.

When to use: Use only with “member-owned” and “opted-in”.

independent Mac check

Another trusted Mac checks the work. The Mac that made it cannot check itself.

When to use: Use only when current evidence proves real eligible Mac reviewers participated.

Also called: independent check, trusted review, Verified Connector Mac review

large parallel batch

A set of many independent compatible tasks that Lithi can schedule in parallel across available approved workers.

When to use: Use only when the work is independently executable and the current policy allows parallel scheduling.

Lithi cloud backup

Runs an allowed task on an approved hosted path when no safe eligible Mac can accept it.

When to use: State the task and data boundary. Name a provider only from the current owning provider authority.

Lithi Connector Mac

A Connector’s approved Mac running Lithi Connect for Mac and eligible for defined Lithi Connect work.

When to use: Use for the device role; never call it an edge node in public copy.

Also called: Connector Mac, Your Lithi Mac

Lithi Routing Service

The coordination service that chooses the safest available place for an approved task.

When to use: Use on connector and technical-public surfaces; do not expose supernode codenames.

Mac Network Bonus

An optional positive account-health benefit from eligible Mac contribution, with no penalty when contribution is off or unavailable.

When to use: Use only if the current product exposes this named benefit and can explain it.

Mac Trust

A signal showing whether a Mac is ready and reliable for a defined class of work.

When to use: Use for device trust; do not use as a score of the human owner.

No-Void outcome

The rule that every task ends in a valid result: run safely, use approved backup, wait, or stop.

When to use: Use as the plain outcome rule; “No-Void Backup” may remain in historical copy only.

Also called: No-Void Backup

opt-in

A person actively choosing to enable an optional feature.

When to use: Use for optional Mac contribution and other optional processing; state how to turn it off.

Own Mac First

Use your own approved Mac when it is available, opted in, capable and safe for the task.

When to use: Use when explaining routing order and include the eligibility conditions.

private relationship work

Warm email and contact work that depends on your private relationship context. It stays on the Connector's own Mac.

When to use: Use when drawing the boundary between owner-Mac relationship work and approved non-private shared work.

Related terms: Lithi Agent Network · approved Mac task · independent Mac check

Routing Priority

The order in which eligible work is offered or assigned among qualified people or devices.

When to use: Use with an explanation of the material factors; do not imply a secret or pay-to-win ranking.

Sealed Task

An approved task packaged so the receiving Mac receives only the information required for that task.

When to use: Use for privacy-preserving task packaging; avoid unsupported cryptographic specifics.

spare capacity

Mac power that is free when you are not using it.

When to use: Use with “when available” and the relevant protections.

swarm coordination

The way approved Macs and services divide, check and combine eligible network work.

When to use: Use on technical or investor surfaces with the SwarmOS distinction stated.

Also called: swarm technology

task routing

Choosing the eligible person, Mac or service for one task.

When to use: Use in technical and connector workflow explanations.

thermal protection

A rule that pauses or limits optional work to keep the Mac within safe temperature conditions.

When to use: Use when explaining temperature-based yielding.

Trusted Connector Mac

Another approved Connector Mac eligible to help with a defined network task.

When to use: Use only for eligible connector-network tasks; never imply access to customer inbox content.

Also called: Trusted Connector Macs

usage limit

A boundary on how much optional work a device or account may perform in a period.

When to use: Use with the actual measured unit and consequence.

account start

A person began the approved account or setup journey.

When to use: Use only when the registered “account start” trigger occurs.

action ID

Identifies the visitor action that measurement records track.

When to use: Use in the analytics envelope as the stable “action ID” field.

analytics event

A small, structured record that a defined interaction or outcome occurred.

When to use: Use for privacy-safe journey and outcome measurement.

anonymous session ID

A temporary identifier used to group actions in one browsing session without naming the person.

When to use: Use only when the purpose and storage boundary are approved; “anonymous” must not be used if the data can reasonably identify the person.

confidence interval

A range showing the uncertainty around an estimated effect.

When to use: Use with the confidence level, method and sample context.

consent state

The recorded state showing which optional measurement or storage choices a person has made.

When to use: Use as a required field for consent-sensitive analytics and storage decisions.

consented visitor ID

Identifies a visitor only after the required consent or lawful basis applies.

When to use: Use only for approved consented measurement; never create it silently.

content surface ID

The stable identifier for the section, component or content surface involved.

When to use: Use in the analytics envelope as the stable “content surface ID” field.

control

The current or baseline experience used for comparison in an experiment.

When to use: Use with the experiment and population named.

CTA click

A person activated a tracked action.

When to use: Use only when the registered “CTA click” trigger occurs.

CTA impression

A tracked action became viewable under the defined threshold.

When to use: Use only when the registered “CTA impression” trigger occurs.

current-touch attribution

The most recent eligible source associated with the current journey or conversion.

When to use: Use only when reporting the current or latest touch.

destination ID

The stable identifier for where an action leads.

When to use: Use in the analytics envelope as the stable “destination ID” field.

device class

A broad device category such as mobile, tablet or desktop.

When to use: Use in the analytics envelope as the stable “device class” field.

download start

A person initiated an approved download.

When to use: Use only when the registered “download start” trigger occurs.

event deduplication

Preventing the same logical interaction or outcome from being counted twice.

When to use: Use across analytics adapters and provider delivery.

event envelope

The common set of fields carried by every analytics event.

When to use: Use in analytics contracts and adapters.

experiment

A controlled test comparing approved alternatives to learn which better achieves a defined outcome.

When to use: Use only for an actual controlled comparison, not an untracked design change.

Also called: A/B test

first-touch attribution

Credit assigned to the first recorded eligible source in a journey.

When to use: Use only when reporting a first-touch view; do not call it sole causation.

form error

A form could not continue because of a defined validation or submission error.

When to use: Use only when the registered “form error” trigger occurs.

form start

A person began interacting with a form under the defined rule.

When to use: Use only when the registered “form start” trigger occurs.

form submit success

The receiving system confirmed that the form submission succeeded.

When to use: Use only when the registered “form submit success” trigger occurs.

guardrail metric

A safety or quality measure that must not get materially worse while another outcome improves.

When to use: Use for privacy, safety, quality, performance and fairness protections in experiments.

holdout

A group deliberately kept outside a change so longer-term effects can be compared.

When to use: Use in experiment design with ethics, consent and business impact considered.

hypothesis

A testable statement predicting how a defined change may affect a defined outcome.

When to use: Use before running an experiment; avoid rewriting it after seeing results.

outcome metric

Names the main result an experiment aims to improve.

When to use: Use before the experiment starts and avoid switching it after results appear.

page variant ID

The stable identifier for the approved page or experiment variant shown.

When to use: Use in the analytics envelope as the stable “page variant ID” field.

page view

The page was rendered or viewed under the defined measurement rule.

When to use: Use only when the registered “page view” trigger occurs.

placement ID

The stable identifier for where an action appeared on the page.

When to use: Use in the analytics envelope as the stable “placement ID” field.

protected-trait proxy

A seemingly ordinary data point that closely reveals or stands in for a protected personal characteristic.

When to use: Use in data-governance and experiment reviews; exclude or control such proxies under approved policy.

referrer class

A controlled category describing the broad source of a visit.

When to use: Use in the analytics envelope as the stable “referrer class” field.

retention period

Defines how long Lithi keeps a data class before deletion or another approved action.

When to use: Use with a number or event and the data class named.

reward signal

A measured result used by a learning or routing system to prefer some choices over others.

When to use: Use in technical learning-system documentation.

route ID

The stable identifier for the page or logical route where an event occurred.

When to use: Use in the analytics envelope as the stable “route ID” field.

section view

A meaningful section became viewable under the defined threshold.

When to use: Use only when the registered “section view” trigger occurs.

statistical significance

Evidence that an observed difference is unlikely under a stated no-effect model, given the test assumptions.

When to use: Use with effect size, interval, sample and analysis plan.

treatment

The alternative experience or rule being tested.

When to use: Use with the exact variant and version named.

UTM parameter

Adds a controlled campaign label to a link so measurement can group visits by source and campaign.

When to use: Use for campaign attribution and keep values consistent and non-personal.

utm_campaign

The stable campaign name or identifier.

When to use: Use utm_campaign according to the central UTM taxonomy.

utm_content

A controlled label distinguishing creative, placement or link variants.

When to use: Use utm_content according to the central UTM taxonomy.

utm_id

A stable campaign identifier used where a name may change.

When to use: Use utm_id according to the central UTM taxonomy.

utm_medium

The controlled channel type, such as email, social or event.

When to use: Use utm_medium according to the central UTM taxonomy.

utm_source

The platform, publisher or referrer category that supplied the visit.

When to use: Use utm_source according to the central UTM taxonomy.

ACH bank debit

A bank payment method that requires explicit customer approval for its stated scope.

When to use: Use only when the payment authority confirms this method and its exact scope.

bank payment approval

Approval for a human to use a bank payment method; it is not standing autopay.

When to use: Use for bank-payment approval and keep it separate from account billing policy.

base value

The verified value created in establishing the original customer account or commercial baseline.

When to use: Use with the current deal-ledger rules; do not use the internal word “tranche” publicly.

Also called: base value / new value

billing rail

The approved system or process used to issue and collect a type of payment.

When to use: Use in technical or internal commercial documentation; customer copy usually says “payment method” or “invoice”.

clawback

A reversal of previously credited or paid value under a defined rule, such as a refund or invalid transaction.

When to use: Use only where the current contributor terms authorize it and show the reason.

credit

A non-cash amount applied against a current or future invoice.

When to use: Use with the source and expiry of the credit.

earnings record

Your earnings record shows which clients and actions support each amount, how Lithi calculated it and whether it is waiting, ready or paid.

When to use: Use on Connector surfaces to explain each earnings line in plain words. Put technical ledger fields in a labeled detail view.

Also called: earnings history

effective spend limit

The approved maximum spend for a named account, task or period.

When to use: Show the named limit and source before setup or paid work.

Enterprise plan

A plan for organizations needing an agreed commercial, deployment or governance arrangement.

When to use: Use “Enterprise plan” only when the current pricing and entitlement registry lists it as publishable.

finance API

A controlled connection for reading or projecting finance records with the customer's authority.

When to use: Use for a finance-system connection, not for payment authority.

finance sync

A controlled read and projection of finance records between Lithi and a customer-owned system.

When to use: Use for record mapping and reconciliation, never as proof that an external payment cleared.

invoice

A formal request for payment showing what is owed and why.

When to use: Use for amounts billed; do not call an estimate, quote or receipt an invoice.

Lithi Invoice Ledger

The governed record of what was invoiced, what cleared and which evidence supports it.

When to use: Use for the named invoice evidence surface only when implemented.

NET 30

Payment terms under which an invoice is due 30 days after the invoice date, subject to the contract.

When to use: Use only where the contract or invoice states NET 30.

Also called: NET-30

past due

A customer charge is due and has not cleared by its stated due date.

When to use: Name the invoice and safe next step; do not imply bank access.

per-Mac license

A license charged for each approved Mac covered by the plan.

When to use: Use only for plans whose current authority defines the license unit as one Mac.

plan

A commercial package states what it includes, its license unit, price and terms.

When to use: Use with the current named commercial package and effective commercial authority; never infer price from historical copy. Use plan alone only for a named commercial package; use Local Business Outreach Plan for Connector work.

Pro plan

A plan for one person, with more capability than Solo. It does not include team sharing.

When to use: Use “Pro plan” only when the current pricing and entitlement registry lists it as publishable.

purchase order policy

Your organization’s rule for when a purchase order is needed before a charge or invoice.

When to use: Ask the customer or authorized finance owner; never invent a PO rule.

renewal save

A confirmed action that kept an at-risk customer, credited for a set period.

When to use: Use only when the current rule and evidence support it; always say the credit is bounded.

Solo plan

A plan intended for one person using the customer product.

When to use: Use “Solo plan” only when the current pricing and entitlement registry lists it as publishable.

subscription

A recurring commercial arrangement that renews under the agreed billing terms until changed or ended.

When to use: Use for recurring plans and state cadence and cancellation terms from the current authority.

suspended for non-payment

Access is paused because an applicable charge did not clear under the current terms.

When to use: Name the affected scope and recovery step; do not claim permanent loss.

Team and Enterprise

The collective label for Lithi’s organization plans when discussing their shared licensing model.

When to use: Use only when both plans share the stated rule; otherwise name the individual plan.

Related terms: Team plan · Enterprise plan · per-Mac license

Team plan

A plan for an organization using approved team capabilities and licenses.

When to use: Use “Team plan” only when the current pricing and entitlement registry lists it as publishable.

Apple silicon

Apple-designed processor architecture used in current Mac computers.

When to use: Use when explaining the supported hardware family; pair exact requirements with the current compatibility evidence.

Also called: Apple-silicon

Apple silicon Mac

A Mac built with an Apple-designed processor.

When to use: Use for the supported modern Mac hardware class; do not turn it into an unqualified compatibility promise.

Also called: Apple-silicon Mac, Apple-Silicon Mac

Related terms: Apple silicon · customer Mac · Lithi Connector Mac

Ask Lithi

Ask a question about Lithi and get an answer — in the app or on the website.

When to use: Use for the named helper, launcher and conversational support surface.

Also called: Lithi helper

Connect apps

The paired Lithi Connect apps for Mac and iPhone. The Mac handles planning; the iPhone keeps field actions, events, approvals and replies close.

When to use: Use when explaining how the Mac and iPhone Connect apps work together. Do not imply that they run the same workload.

Related terms: Lithi Connect

customer operating loop

The customer side of Lithi: EmailOS for your inbox, SwarmOS for your team's shared knowledge.

When to use: Use in architecture or “how Lithi fits together” explanations.

Related terms: distribution loop

Demo Workspace

Try the real Lithi with sample data. You never connect your own inbox.

When to use: Use for sample-only demonstrations of the product.

Related terms: sample account

distribution loop

The Lithi Connect side: Connectors and their Macs helping local businesses find and adopt Lithi.

When to use: Use in architecture or “how Lithi fits together” explanations.

Related terms: customer operating loop

EmailOS

Prepares eligible inbound email replies on your Mac for you to review. Nothing sends until you send it.

When to use: Use for the customer inbox product, its Mac app and its customer-facing documentation.

Also called: Lithi EmailOS, the Lithi email assistant

Frontier tokens

A simple public term for the scarce, higher-cost model usage consumed by frontier AI agents such as coding and reasoning agents.

When to use: Use when explaining frontier-model cost, usage pressure, or why delegating suitable bulk work preserves premium agent capacity.

Related terms: Lithi Agent Network · Lithi Compute

Guided Setup

A booked session where a trained person helps you set up Lithi. You stay in control.

When to use: Use for scheduled setup assistance.

Help Center

Search setup guides, troubleshooting steps and practical answers.

When to use: Use for the public help destination and its article collection.

Intel Mac

A Mac built with an Intel processor.

When to use: Use only when explaining compatibility, migration or an unsupported-device path.

iOS

Apple’s operating system for iPhone.

When to use: Use when naming the iPhone platform or a supported iPhone companion workflow.

Lithi

Lithi makes EmailOS, SwarmOS, Lithi Connect and the Lithi Agent Network.

When to use: Use as the short company name and as the actor when Lithi itself performs a clearly scoped action.

Lithi Agent Network

Lithi turns spare power from approved Macs into a people-powered AI network. Mac owners choose when their computers can help with suitable AI tasks.

When to use: Use as the master public brand on customer, provider, connector, marketing, docs, trust and technical-public surfaces when naming the network itself. Use Lithi Compute when naming the technical execution subsystem or its API.

Related terms: Lithi Compute · Frontier tokens · Local-first routing

Lithi Compute

The technical execution system behind the Lithi Agent Network, and the name of its customer API.

When to use: Use when naming the technical subsystem, its API, its packages or its contracts. Use Lithi Agent Network for the public product story.

Related terms: Lithi Agent Network · Frontier tokens

Lithi Connect

Lithi Connect helps Connectors plan local business work by choice. You choose each action. It is separate from the Lithi Agent Network and Compute.

When to use: Use on connector, recruiting, distribution, event, attribution and contributor surfaces. Keep participation optional and preserve the current signed subscription and downstream rules.

Related terms: Local Business Outreach Plan

Lithi Connect for Mac

The Mac app where a Connector reviews matched businesses, complete outreach plans, prepared messages, events, earnings and device settings.

When to use: Use Lithi Connect for Mac in visible product copy. Keep LithiSidebar for implementation and search only.

Also called: Connect Mac app

Lithi ecosystem

Everything Lithi: the products, the apps, and the people behind them.

When to use: Use when a sentence genuinely covers more than one Lithi product or operating system.

Also called: Lithi system family

Related terms: EmailOS · SwarmOS · Lithi Connect · Lithi Agent Network

Lithi Technologies

The full company name, used in formal contexts.

When to use: Use in company footers, formal company descriptions and documents that require the company-facing name.

Local-first routing

When it can, Lithi tries to use trusted Macs closer to your business.

When to use: Use when explaining regional preference in routing.

Related terms: Lithi Agent Network

M-series chip

One of Apple’s M-series processors used in Apple silicon Macs.

When to use: Use for hardware guidance, then state the exact tested requirement separately.

Mac

An Apple personal computer that runs macOS.

When to use: Use the general word only when the more specific device role is not important.

Related terms: customer Mac · Lithi Connector Mac · Apple silicon Mac

macOS

Apple’s desktop operating system for Mac computers.

When to use: Use when naming the Mac operating system or a platform-specific requirement.

SwarmOS

Helps your team use approved company knowledge in EmailOS, with sources you can check. It does not pool private inboxes.

When to use: Use for customer team intelligence, approved knowledge sharing and shared customer context.

Related terms: Approved Team Knowledge · connection sharing · cited fact · shared timeline

Trust Center

See the evidence behind Lithi's security, privacy, data, billing and policy claims.

When to use: Use for /trust and for links that substantiate a public trust claim.

assignment

A prospect, account or task offered or given to an eligible person.

When to use: Use for owned work; distinguish “offered”, “accepted”, “declined” and “active”.

attendee choice

Each attendee chooses whether to explore Lithi, share contact details or receive follow-up after the event.

When to use: Use wherever a Cafe Hour asks an attendee to take a next step. Never bundle optional choices.

attribution

The evidence showing which source, person or campaign contributed to an outcome.

When to use: Use with the attribution model named; do not imply causation from one tracking parameter alone.

B2B

Business-to-business activity between organizations rather than consumer selling.

When to use: Spell out business-to-business on first use, then use B2B where the audience understands it.

business brief

A source-backed overview of the matched business, why it may fit and the current context that may matter.

When to use: Use for Lithi's prepared overview before People and Schedule. The Connector reviews it but does not rewrite source records.

Cafe Hour

A relaxed one-hour local Agent Network learning session. Lithi prepares the materials; the host chooses publication and people choose whether to explore the network.

When to use: Use Cafe Hour for one event and Cafe Hours for the program. Say what Lithi prepares and what the Connector chooses, shares, hosts and follows up.

Also called: Cafe Hours

campaign

A defined set of approved messages and actions for one audience, purpose and period.

When to use: Use for a governed initiative; avoid the word for one personal message when “conversation” is clearer.

complete plan approval

One approval for the complete current plan after you review its business, people, messages, timing, evidence and stop rules.

When to use: Use for the final current-plan decision. It does not approve a different person, purpose, message, action or timing window.

completeness grade

A clear score showing which required parts of a prospect or organization record are present and trustworthy.

When to use: Use with the rubric and missing fields visible.

Connector attribution

Shows which Connector introduced or helped a customer, so Lithi can assign eligible earnings.

When to use: Use for connector credit only when the required evidence exists.

Contacted

Records an approved first contact action.

When to use: Use as the exact pipeline state “Contacted” only when its acceptance rule is satisfied.

coverage

The share of required facts, sources, routes or cases that a system currently includes.

When to use: Use only with a clear numerator, denominator and date.

current business signal

A dated public indicator that may help explain the matched business's current needs or priorities.

When to use: Use only when the signal is visible, recent enough for the decision and relevant to the proposed plan.

demo request

A person asking to see Lithi or receive setup help.

When to use: Use for an explicit request, not an inferred interest signal.

device pairing

The verified setup that links your Connect Mac and iPhone for the approved shared account and companion tasks.

When to use: Use for Connect Mac and iPhone setup. Do not imply that pairing gives iPhone the Mac's local inference workload.

Engaged

The person has meaningfully responded or interacted.

When to use: Use as the exact pipeline state “Engaged” only when its acceptance rule is satisfied.

enquiry

A message or request from someone seeking information or help.

When to use: Use for an explicit inbound contact.

enrichment

Adding verified, relevant facts and sources to a prospect or organization record.

When to use: Use with the data source and allowed purpose; do not imply every fact is current or complete.

event capacity

The approved number of attendees the event and venue can support.

When to use: Use with the current event and venue. Never turn capacity into false scarcity or a guaranteed attendance count.

event details

The approved event name, purpose, date, time, format, location and attendance information shown to invited people.

When to use: Use for attendee-facing facts. Keep internal host notes, private attendee data and unapproved changes separate.

event follow-up

The relevant next message or task after an event, limited by each attendee's choices and current context.

When to use: Use after an event only for an approved purpose and eligible attendee. A reply, opt-out or complaint changes or stops the work.

event mode

Whether the event is in person, online or hybrid, with the attendance instructions that follow from that choice.

When to use: Use when the format changes what attendees or hosts must do. Never imply feature parity across modes without evidence.

event proof

Approved evidence that a named event step happened, without exposing unnecessary attendee or private venue information.

When to use: Use for the minimum evidence required by an event workflow. Never request a photo, identity or private detail without a defined need and consent.

Eventbrite

An external event-listing and ticketing platform an approved Lithi event workflow can use.

When to use: Name Eventbrite only when the current workflow actually uses it and the provider claim is approved.

HELP keyword

A text-message keyword commonly used to request program or contact information.

When to use: Write `HELP` exactly when documenting a supported SMS command.

Also called: HELP

intent signal

An observation suggesting that someone may be researching, evaluating or needing a relevant solution.

When to use: Use with cautious language such as “may indicate”.

lead

A person or organization that has shown a relevant signal or supplied contact information for follow-up.

When to use: Use according to the current lead-lifecycle definition and state.

Local Business Outreach Plan

Lithi builds one plan for a matched business. You check the people, messages, timing, sources and stop rules.

When to use: Use for the complete plan a Connector reviews before acting. Lithi prepares the business brief, selected people, sequence, likes, comments, connection requests with personalized notes and follow-ups. The Connector checks the evidence, reviews every prepared message, edits permitted wording, approves the current complete plan once and performs each action in the relevant product. If a source is stale or wrong, request a review; do not rewrite the source record.

Also called: Business Outreach Plan, local outreach plan

Related terms: assignment · sequence · public professional signal · signal · public-web enrichment · material change

local event

An approved nearby session, workshop or demonstration connected to Lithi.

When to use: Use as the general event category; name the format when known.

local group matching

Finding relevant local groups where an approved post may be useful and permitted.

When to use: Use for group discovery and suitability, not automatic publication.

local Lithi number

An assigned Lithi contact number for local outreach, separate from your personal number.

When to use: Use when explaining local outreach contact boundaries.

local match preference

Lithi favors a relevant nearby business when current evidence and your selected experience support the match.

When to use: Use to explain why locality matters. Do not promise the nearest business, an exclusive territory or a match within a fixed distance.

Lost

The opportunity will not move forward in its current form.

When to use: Use as the exact pipeline state “Lost” only when its acceptance rule is satisfied.

matched local business

The one business in your current assignment, selected because its location, needs and visible context may fit your experience.

When to use: Use for the business currently assigned to a Connector. Never imply ownership, exclusivity, guaranteed fit or a guaranteed local match.

material change

A change to the people, purpose, actions, timing or safety limits. You must approve the plan again.

When to use: Use when explaining why a changed plan needs review; a material change never silently inherits an earlier approval.

Also called: approval-relevant change

media consent

A person's specific choice about whether approved event photos, audio or video may be captured and used.

When to use: Use before capturing or publishing identifiable event media. Attendance alone is not consent.

Meeting

Records when someone books or completes a relevant meeting or demo; the substate shows which.

When to use: Use as the exact pipeline state “Meeting” only when its acceptance rule is satisfied.

offline action queue

Eligible actions saved on your device while offline and checked again before they run after reconnecting.

When to use: Use only for actions the current contract permits offline. Never queue uncertain sends, payments or publications as safe automatic retries.

opportunity

A qualified potential customer with a real next commercial step.

When to use: Use only after qualification; do not label every prospect an opportunity.

opt-out

A person’s request not to receive a defined category of future communication.

When to use: Use for the recipient choice and name the affected channel or purpose.

organization

A business, public body, charity or other entity represented in Lithi data.

When to use: Use instead of “company” when the entity may not be a company.

pairing code

A short-lived code that starts device pairing. Check both devices before approving the link.

When to use: Use for the code shown or scanned during pairing. Never call it a password or permanent device key.

pairing verification

The check that both devices, the account and the requested companion access are the ones you expect.

When to use: Use after a code is scanned or entered and before Pair takes effect.

person–organization membership

The dated relationship showing that a person holds or held a role at an organization.

When to use: Use for work history and current organization context; never overwrite history with one current employer field.

pipeline

The ordered view of prospects and customer opportunities as they move through defined stages.

When to use: Use for the sales or customer journey view and name the stage definitions.

plan evidence

The visible sources, dates and reasons supporting the business match, selected people and prepared plan.

When to use: Use for what a Connector checks beside Why this match, People and Schedule. Do not call an unsupported assumption evidence.

plan version

The saved current form of the complete plan. Approval applies only to the version you reviewed.

When to use: Use whenever edits or refreshed context can change the plan. Never carry approval to a materially changed version.

prospect

A person or organization that may be relevant to an approved Lithi Connect campaign but has not yet become a customer.

When to use: Use before a confirmed enquiry or qualified sales opportunity; name person or organization when precision matters.

prospect brief

A short, sourced explanation of why one prospect may fit the approved plan.

When to use: Use prospect brief on plain and guided Connector surfaces; retain prospect dossier only as a technical or legacy identifier.

public professional signal

A work-related signal visible from an approved public source, such as a role change or company announcement.

When to use: Use for public work context; name the source and date.

public-web enrichment

Researching approved public sources to add relevant, source-linked context.

When to use: Use for the public-source research engine; do not imply logged-in private access.

QR code

A scannable square code that opens an approved link.

When to use: Use with a visible text URL or action description for accessibility.

qualified conversion

A completed outcome that meets the current rules for counting as a meaningful conversion.

When to use: Use only with the qualifying rule and event version defined.

quiet hours

Times when Lithi pauses or defers a communication.

When to use: Use with the applicable timezone and policy source; never hard-code one universal window without authority.

request source review

Ask Lithi to check a source or fact that looks wrong, old or off topic. You do not rewrite the source.

When to use: Use instead of Edit source. The Connector may edit permitted message wording, not source records or enrichment facts.

same-thread follow-up

A follow-up sent as a reply in the original conversation thread.

When to use: Use when the message genuinely continues the same thread.

sample account

A clearly labeled Connect account with sample data. You can explore it before applying, and its actions never affect live data.

When to use: Use for the app-first Connect preview. Keep it distinct from Demo Workspace and always state the no-live-effects boundary.

Related terms: Demo Workspace · Connect apps

sequence

The planned order and timing of actions for one prospect, including when to pause or stop.

When to use: Use for the ordered prospect actions and timing; name the prospect and the pause or stop boundary where relevant.

signal

A recent, relevant observation that may explain why a conversation could be useful now.

When to use: Use only when the observed fact and source are available; do not call a guess a signal.

SMS

A mobile text-message channel.

When to use: Spell out the term on first use where needed, then use SMS. Do not imply a send capability without current evidence and approval.

STOP keyword

A text-message keyword commonly used to request that messages stop.

When to use: Write `STOP` exactly when documenting the supported SMS command; do not claim support without end-to-end evidence.

Also called: STOP

syndication queue

Holds approved or proposed posts until a person shares them through a permitted channel.

When to use: Use for publication work in progress; distinguish “prepared”, “approved”, “handed off” and “published”.

technology signal

Public evidence that a business uses or is changing relevant technology, shown with its source and date.

When to use: Use only when it helps explain a relevant, truthful opportunity, such as how EmailOS could improve eligible inbound reply work.

trial link

A link that takes someone to an approved trial or setup journey.

When to use: Use for the actual trial destination; do not place secret or personal data in the URL.

trial sharing

Sharing an approved trial or setup link while preserving who introduced it.

When to use: Use for approved trial invitations and attribution.

unsubscribe

The action used to stop future email or another defined subscription communication.

When to use: Use for email or subscription communication; use opt-out as the broader concept.

venue details

The location, arrival, accessibility and contact information people need to attend the event safely.

When to use: Use for practical attendance information. Do not expose private host or venue contact details beyond the approved event scope.

warm network

Optional on-device help finding people you already know who may care about Lithi.

When to use: Use with explicit permission, local processing and one-invite-at-a-time choice.

warm path

A genuine relationship or credible shared context that makes an introduction relevant.

When to use: Use when the relationship or context is real, relevant and explainable.

Also called: warm paths

Won

The opportunity has become a paid customer under the current definition.

When to use: Use as the exact pipeline state “Won” only when its acceptance rule is satisfied.

actor

The person, service or device requesting or performing an action.

When to use: Use in technical contracts; use “person”, “service” or “Mac” in plain copy.

API

A defined way for software systems to request data or actions from one another.

When to use: Spell out on first use for non-technical readers; name the API owner and scope.

Also called: application programming interface

append-only

The system adds new records without silently changing or deleting existing history.

When to use: Use for event or receipt history; do not imply legal data can never be deleted.

authority

The approved owner or source allowed to define, change or confirm something.

When to use: Use with the domain, owner and boundary named.

automation

A saved rule that starts from an approved event and performs only the actions listed for it.

When to use: Use for a saved rule that runs on an approved event.

backfill

Adding or correcting historical records in a new field or system from existing evidence.

When to use: Use in migrations and name the source, date range and validation.

backoff

Waiting longer between repeated attempts so a failing system is not overwhelmed.

When to use: Use in technical reliability documentation.

canonical human ID

The one approved identifier used to refer to the same human account across the system.

When to use: Use in identity architecture and migrations.

causation ID

The identifier of the command or event that directly caused another event.

When to use: Use in event contracts and replay analysis.

checksum

A calculated fingerprint used to detect whether a file or record changed.

When to use: Use for integrity verification and name the algorithm where relevant.

circuit breaker

A control that temporarily stops calls to a failing dependency so the wider system can recover.

When to use: Use in technical reliability documentation.

command

A request to perform a specific action.

When to use: Use for an action request, not for the resulting event.

connection

An approved link to one named provider account and the resources you allow EmailOS to use.

When to use: Use as the customer-facing label for a provider link. Keep plugin for the technical adapter.

content-free metadata

Small details can describe an event or item. They do not include the private message or file.

When to use: Use only with an enumerated field class; do not imply metadata is automatically harmless.

contract

A precise agreement about what data or behavior a system accepts and returns.

When to use: Use in technical documentation and name the contract version.

correlation ID

An identifier that links all records belonging to the same end-to-end journey or request.

When to use: Use in technical tracing and support evidence; do not place PII in it.

cryptographic hash

A one-way fingerprint of data used to detect changes.

When to use: Use for integrity and content addressing; do not call it encryption.

cutover

The controlled point when a new system becomes the active authority.

When to use: Use only when the switch and authority change are defined.

data silo

A separate store or workflow that prevents the rest of the authorized system from seeing consistent state or evidence.

When to use: Use in architecture diagnosis; do not call intentional privacy boundaries silos.

dead-letter queue

Holds work that exhausted its allowed processing attempts.

When to use: Spell out on first use, then use DLQ.

Also called: DLQ

device ID

The stable identifier for an approved device record.

When to use: Use as the exact typed identifier “device ID”; never reuse it for another entity type.

digital signature

Proves that the private-key holder signed the data and that nobody changed it afterward.

When to use: Use for signed builds, receipts or messages and state what key identity is trusted.

dual write

Temporarily writing the same logical update to an old and a new system during migration.

When to use: Use only in migration plans with a named validation and exit condition.

event log

An ordered record of events that occurred in a system.

When to use: Use in technical architecture; do not call every application log an event log.

fencing token

A steadily increasing token that prevents an older worker from acting after a newer one has taken over.

When to use: Use in technical concurrency and distributed-lock documentation.

forward repair

Fixing a problem by adding a corrected version or transition rather than rewriting history.

When to use: Use for append-only or irreversible domains.

health check

A safe check showing whether a component is available and working within its defined limits.

When to use: Use with the exact layer being checked.

idempotency

The property that safely repeating the same request does not create the action twice.

When to use: Use for retry-safe commands, payments, sends, jobs and webhooks.

idempotency key

The identifier used to recognize a repeated request as the same logical action.

When to use: Use for retry-safe external or internal commands.

identity alias

Another identifier that maps to a canonical identity for compatibility or migration.

When to use: Use for migration or integration mappings; do not treat every foreign key as a human alias.

immutable event

A permanent record that a defined event or state change occurred.

When to use: Use for durable workflow and audit facts.

job

A unit of work scheduled for a worker or service to execute.

When to use: Use in worker and queue architecture; distinguish it from a human task.

JSON

A text format for exchanging structured data as objects, arrays and values.

When to use: Spell out the term on first use in general documentation and state the schema or version when one exists.

migration

A controlled change from one data, contract or system version to another.

When to use: Use with the source, target and reversibility stated.

organization ID

The stable identifier for an organization.

When to use: Use as the exact typed identifier “organization ID”; never reuse it for another entity type.

outbox

A reliable list of events waiting to be delivered to another system.

When to use: Use in technical event-delivery architecture.

permission

A rule allowing a defined actor to perform a defined action on a defined resource.

When to use: Use with the action and resource named.

queue

Holds work in order until a worker can process it.

When to use: Use with the queue’s purpose and ordering guarantees named.

rate limit

A cap on how many requests or actions may occur in a period.

When to use: Use with the unit, scope and reset behavior.

raw content

The original message, document, attachment or other substantive data rather than a summary or metadata.

When to use: Use when drawing data boundaries and retention rules.

read model

A view of data prepared for a particular screen, report or question.

When to use: Use for dashboards, queues, timelines and summaries.

Also called: projection

redaction

Removes or masks information that people should not see or share.

When to use: Use when sensitive content is removed from support, logs, exports or examples.

registry

A governed list of named items and the rules or metadata attached to them.

When to use: Use for structured authoritative lists; do not use for an informal spreadsheet unless it truly governs the system.

retry

Trying a failed or incomplete operation again under a defined rule.

When to use: Use only where repetition is safe and bounded.

rollback

Returning to a previous safe version or path after a change causes a problem.

When to use: Use where reversal is actually possible; otherwise say “forward repair”.

RPC

A technical call that asks another service or database function to perform a defined operation.

When to use: Spell out on first use in technical documentation; do not expose raw RPC names in public copy unless they are a developer contract.

Also called: remote procedure call

scheduled job

A job configured to run at a defined time or interval.

When to use: Use instead of “cron” in public or general copy; “cron” may be used technically when it is the actual scheduler syntax.

Also called: cron job

schema

The defined structure and validation rules for data.

When to use: Use with the data object and version named.

schema version

The identifier showing which form of a data contract is in use.

When to use: Use in every durable event, receipt or external contract that may evolve.

source of truth

The current authority people should consult for a specific fact or rule.

When to use: Use only with the scope and owner named; avoid claiming one file is truth for unrelated domains.

state

The current recognized condition of an item or workflow.

When to use: Use the exact registered state label rather than inventing synonyms.

system of record

The approved system whose stored value is authoritative for a particular fact or state.

When to use: Use with the exact domain named, such as invoice status or application state.

tamper-evident

Designed so unauthorized changes can be detected.

When to use: Use only when the mechanism and verification path exist.

task

One defined unit of work inside a workflow.

When to use: Use for a unit of work; avoid using “task” for a durable business entity when a specific name exists.

task ID

The stable identifier for one task.

When to use: Use as the exact typed identifier “task ID”; never reuse it for another entity type.

template

A prebuilt starting point for one email question and one or more approved sources.

When to use: Use for a prebuilt starting point a person installs and configures.

tenant ID

The identifier for a governed customer or operating data scope.

When to use: Use as the exact typed identifier “tenant ID”; never reuse it for another entity type.

terminal state

A state in which the current workflow run is finished.

When to use: Use for final workflow outcomes.

trace ID

An identifier linking technical operations within one distributed trace.

When to use: Use for technical tracing; distinguish it from a business correlation ID when both exist.

transition

An approved change from one state to another.

When to use: Use for a lifecycle state change.

UUID

A 128-bit identifier designed to make accidental duplication extremely unlikely when generated correctly.

When to use: Spell out the term on first use, then use UUID. Do not expose one as proof of authorization.

webhook

A provider sending an event to a registered URL when something happens.

When to use: Use in integration documentation and explain how authenticity and retries are handled.

workflow

A defined series of steps that moves work toward an outcome.

When to use: Use for multi-step work; name the workflow when possible.

workflow run

One execution of a workflow for a particular item or request.

When to use: Use for one concrete execution rather than the workflow definition.

workflow run ID

The stable identifier for one workflow execution.

When to use: Use as the exact typed identifier “workflow run ID”; never reuse it for another entity type.

Approve

Accept the current proposed item for its stated next step.

When to use: Use as a button label only when the resulting action is clear nearby.

Approved Mac

A Mac that has passed the required identity, permission and security checks for a defined Lithi role.

When to use: Use only with the applicable product or task scope.

authorization

Permission for an app or person to perform a defined action.

When to use: Use for permission decisions, not identity proof.

Also called: authorization

CC rule

A rule for who should be copied on a message and under what conditions.

When to use: Use as part of Smart Controls; explain that the person can review the final recipients.

Also called: CC rules

connection health

The current sign-in, provider, host and policy state of a connection, with the next safe action.

When to use: Use for status and diagnosis without exposing credentials or provider records.

connection host

The approved customer device that keeps a provider credential and performs permitted provider requests.

When to use: Use when explaining personal, designated-organization or customer-hosted connection availability.

credential

Secret or signed information used to prove an identity or access a service.

When to use: Use in security and setup documentation; name the credential type when possible.

customer Mac

A Mac approved by a customer organization to run EmailOS or SwarmOS work.

When to use: Use for customer-owned or customer-approved product devices; do not call them Connector Macs.

device activation

The steps that register a Mac for an approved Lithi account and role.

When to use: Use for device registration and readiness, not for a person’s application approval.

draft

A proposed message you have not sent.

When to use: Use for AI-prepared or human-edited message content before sending.

Edit

Open the proposed item so you can change it.

When to use: Use as the standard action for changing a draft or task.

eligible inbound email

An incoming message that matches the approved rules for Lithi to prepare work from.

When to use: Use when a workflow applies only to a defined subset of messages.

first reviewable draft

The first eligible draft EmailOS prepares with enough context for you to review, edit, skip or send.

When to use: Use for the first-value checkpoint after setup. Do not turn it into a time guarantee or universal provider claim.

Related terms: draft · human approval

human-in-the-loop

A workflow in which a person reviews or decides at a defined point before the action can continue.

When to use: Use in technical or trust copy after stating exactly what the person reviews or approves.

inbox work

The reading, organizing and reply-preparation tasks people perform around email.

When to use: Use as an outcome-focused umbrella; name the exact action when describing a capability.

knowledge-gap view

A team view showing which topics lack enough approved information to answer well.

When to use: Use for constructive team knowledge improvement.

license unit

The item a Lithi plan licenses, such as one Mac when the current plan says so.

When to use: Use when explaining what a plan covers; state the exact unit from the current pricing authority.

Lithi Connection Kit

Lithi's local tools for adding, checking and governing approved business-tool connections.

When to use: Use for the named developer and IT product after its schema, broker and hostile-package tests are mounted.

local processing boundary

The clearly named content and operations that stay on approved customer Macs.

When to use: Use instead of a scope-free “zero-egress” claim. Always name the data class and operation covered.

Also called: on-device processing boundary

local-first

Designed to do eligible work on your Mac first, before any external path.

When to use: Use only with the exact boundary and exceptions nearby; it never means offline-only or zero network activity.

Related terms: local processing boundary · local inference

minimum-cell privacy

Hiding very small groups in reports so a person cannot be singled out from an aggregate.

When to use: Use in manager and analytics views that aggregate people or sensitive activity.

mobile companion

A mobile app for reviewing, confirming or continuing Lithi tasks when you are away from your Mac.

When to use: Use for iOS or mobile companion experiences.

Needs You

The EmailOS view for messages or choices that need your judgment before a draft can continue.

When to use: Use for the named EmailOS view and explain the decision or missing context instead of implying a generic error queue.

Related terms: review queue · human approval

no-surveillance principle

Team features should help people find approved knowledge without turning ordinary work into employee surveillance.

When to use: Use in manager, IT, analytics and team-knowledge design decisions.

personal connection

A connected account used only by you, on your own Mac.

When to use: Use to distinguish a person's own connection from an organization-governed team connection.

Related terms: connected account · team connection

provider connection

An approved link between Lithi on the Mac and a mail or business service.

When to use: Use for an active, evidenced connection; name the provider only where publication is approved.

provider credential

A credential that lets an approved connection access a provider within granted scopes.

When to use: Use when explaining provider access and protection.

recipient rule

A rule that changes how Lithi handles email for a particular person or group of recipients.

When to use: Use for recipient-specific behavior and state the effect.

reply-only draft

A draft reply prepared inside an existing conversation rather than a new outbound message.

When to use: Use when the workflow is explicitly limited to replies.

Also called: prepared reply

review

Checking a draft or proposed action before deciding what to do.

When to use: Use with “human review”, “Lithi Reviewer” or another precise qualifier when needed.

review queue

The ordered list of drafts and actions waiting for you to check.

When to use: Use for the place where a person reviews pending work.

seat

One person or device entitlement within an organization plan, as defined by that plan.

When to use: Use only after stating what one seat represents.

Send

Deliver the reviewed message through the connected email provider.

When to use: Use only for the actual delivery action; never label draft approval “Send” unless it truly sends.

sender rule

A rule that changes how Lithi handles mail from a particular sender.

When to use: Use for sender-specific eligibility or handling.

shared team intelligence

Approved knowledge and context that helps teammates answer without repeatedly asking one another.

When to use: Use as the plain-language benefit; use SwarmOS as the product name.

Skip

Leave this proposed item undone and move on.

When to use: Use where skipping is safe and its consequence is clear.

Smart Controls

The customer settings that control sources, tone, recipients, copied people and approvals.

When to use: Use as the named control group and list no more than the relevant five controls.

smart folder

A saved view that groups messages or work matching defined rules.

When to use: Use for rule-based organization in EmailOS.

team connection

A connection an organization has approved for scoped team use without sharing its credential.

When to use: Use only after connection-host, grant, revocation and no-custody proof exists; never imply a shared token or shared corpus.

Related terms: connection sharing · personal connection

topic rule

A rule for messages about a defined subject, such as invoices, orders or scheduling.

When to use: Use when the product behavior depends on message topic.

approved source

A named source a person or authorized team has allowed EmailOS to use for a defined scope.

When to use: Use when naming what a reply is allowed to draw on.

Approved Team Knowledge

Company knowledge that an authorized person has allowed the team to use for a defined purpose.

When to use: Use for customer team knowledge after the relevant approval and scope are established.

cached answer

A previously prepared answer stored temporarily so it can be reused quickly.

When to use: Use only when the retention and invalidation behavior is known.

chunk

A smaller section of a document prepared for search and retrieval.

When to use: Use in technical ingestion and retrieval documentation.

citation

A reference showing which source supports a statement.

When to use: Use wherever a person needs to verify the source of an answer.

cited fact

A fact shown with its source, so you can check where it came from.

When to use: Use for facts shared or generated from approved knowledge.

connected account

A business tool account you have authorized Lithi to use for a defined purpose.

When to use: Use for an actual authorized provider account.

Connected Context

The customer-facing view of approved connected accounts and knowledge sources available for a task.

When to use: Use only for the named product surface when it exists in the current build.

Related terms: connected account · Knowledge Base

connected resource

A specific mailbox, store, CRM, calendar or other resource available through an approved connection.

When to use: Use when a connection contains more than one resource.

connection sharing

An approved teammate’s connected account providing a scoped, cited fact without exposing credentials or the raw source.

When to use: Use for customer team sharing through an approved connection; always explain scope, citation and revocation.

context

The information supplied to an agent for the current task.

When to use: Use with a qualifier when needed, such as customer context, message context or model context.

context assembly

The step that selects and orders the approved information for a task.

When to use: Use in technical retrieval and agent architecture.

context pack

The approved bundle of information assembled for one agent task.

When to use: Use in technical agent and receipt documentation.

correction

You changing an AI-prepared result to make it accurate or better suited to the task.

When to use: Use for an edit that corrects content, not as an admission that every edit trains a shared model.

CRM

A system for managing customer and prospect relationships, history and next actions.

When to use: Spell out the term on first use, then use CRM. Name the specific connected scope rather than implying access to the whole system.

embedding

A numerical representation used to find content with similar meaning.

When to use: Use in technical search and privacy documentation.

expiry

The time when a grant, link or permission stops being valid.

When to use: Use with the exact date, duration or trigger.

freshness

Shows when someone last checked or updated information for the current decision.

When to use: Use with an actual checked-at date or freshness rule.

HRIS

A system for managing employee and workforce information.

When to use: Spell out the term on first use, then use HRIS. Do not imply that Lithi can read every workforce record.

hybrid search

Search that combines exact-word and meaning-based results.

When to use: Use in technical retrieval explanations.

keyword index

A search index that finds exact words and phrases.

When to use: Use in technical search architecture.

Knowledge Base

Your Knowledge Base holds the documents, facts and rules Lithi may use.

When to use: Use for the customer or connector source collection; name whose Knowledge Base it is when context is ambiguous.

Also called: KB

Knowledge Base upload

A file or document you deliberately add to a Knowledge Base.

When to use: Use for a deliberate customer or connector document addition.

Also called: Knowledge Base uploads

knowledge conflict

Two approved sources giving different answers to the same question.

When to use: Use when the system cannot safely choose one source.

knowledge gap

A question the approved knowledge cannot answer well enough yet.

When to use: Use for missing organizational knowledge and pair it with a constructive next action.

knowledge item

One approved unit of knowledge, such as a policy, fact, answer or source reference.

When to use: Use for an individual governed record.

Also called: knowledge card

knowledge source

An approved place or document from which a fact or answer may be drawn.

When to use: Use for the origin of retrieved knowledge.

learning loop

The process of using verified outcomes and approved corrections to improve future work.

When to use: Use when explaining improvement over time; name the evidence and boundary.

learning proposal

A visible suggestion to change a rule, example or memory after you edit. You can inspect, test, accept, reject or undo it.

When to use: Use for a proposed knowledge or writing-preference change that remains visible and reversible.

Related terms: correction · voice profile · recipient profile

local index

A search index stored and used on your Mac.

When to use: Use only when the current implementation proves the index is local for the named content.

memory

Information a system retains for future use.

When to use: Use only after naming what is retained and where.

messaging rule

An approved rule about what a draft should say, avoid or do for a particular situation.

When to use: Use for explicit drafting behavior, not an inferred preference that the person has not approved.

per-person scope

A sharing rule that grants access to a named person rather than a whole team.

When to use: Use when sharing is granted individually.

permitted knowledge

Private or approved team knowledge that current rules allow EmailOS to use for one reply.

When to use: Use when explaining which sources EmailOS may use for a specific reply. Name the source and current scope where useful.

Related terms: private knowledge · Approved Team Knowledge · knowledge source

portal integration

A provider connection configured through an approved web or account portal.

When to use: Use only for a mounted and approved portal integration; do not conflate it with an on-Mac connection.

prepared reply

A reply-only draft that has passed its automated checks and is ready for you to review.

When to use: Use for a draft ready for human review. Never label approving one as sending.

private knowledge

Knowledge only you, or the approved scope that owns it, can see.

When to use: Use when distinguishing personal or restricted context from team-approved knowledge.

provenance

The history of where information came from and how it changed.

When to use: Use in technical, trust and receipt documentation; explain plainly on first use.

Public source receipt

A record of the public information used to personalize or enrich a message.

When to use: Use for public-web enrichment evidence; do not call the activity “scraping” in public copy.

recipient profile

EmailOS keeps writing examples and choices for one person. That profile never changes another person's drafts.

When to use: Use for EmailOS per-recipient style learning.

Also called: your voice with this person, recipient-specific voice

retrieval

Finding the most relevant approved information for a task.

When to use: Use for the context-finding step before generation.

retrieval policy

The rules that decide which sources may be searched and used for a task.

When to use: Use in technical and trust explanations of knowledge access.

retrieval-augmented generation

Generating an answer using relevant source material found at request time.

When to use: Spell out on first use in technical documentation; prefer “answers grounded in approved sources” in plain copy.

Also called: RAG

semantic search

Search that looks for similar meaning, not only matching words.

When to use: Use when the search genuinely uses meaning-based matching.

shared timeline

A short, team-visible history of approved customer facts and actions.

When to use: Use for the customer team history feature and explain its sources and scope.

sharing controls

The settings for who may receive which facts, how much, for how long and with what evidence.

When to use: Use as the umbrella for team-sharing permissions; list the actual controls rather than leaving it vague.

source authority

How much a source should be trusted for a particular kind of fact.

When to use: Use when resolving or ranking competing sources.

source document

The original file or page from which knowledge was extracted.

When to use: Use when referring to the original evidence rather than its index representation.

source fact

A specific statement taken from an approved source.

When to use: Use for a fact before it is presented as a cited answer.

source priority

The order in which eligible sources should be checked for a particular answer.

When to use: Use in retrieval-policy and conflict-resolution documentation.

source receipt

A record of the facts and sources used for a prepared reply.

When to use: Use when naming the evidence shown beside a prepared reply.

source scope

Defines which people, topics, organizations or tasks a source can support.

When to use: Use whenever a source is not universally available.

stale source

A source that may be too old for the current question or action.

When to use: Use as an honest state; provide the checked date and next step.

standard operating procedure

An approved step-by-step way of completing a recurring task.

When to use: Spell out on first use, then use SOP.

Also called: SOP

team knowledge

Approved company knowledge that can help authorized teammates answer consistently.

When to use: Use as a plain category after the approval boundary has been explained.

Related terms: Approved Team Knowledge

tone bounds

The approved limits for how formal, direct, warm or concise a draft should be.

When to use: Use as part of Smart Controls and explain the actual options in the UI.

un-share

You revoke a sharing grant so Lithi stops using it and handles cached answers under the approved policy.

When to use: Use for the named sharing-revocation action; state what happens to cached results.

vector index

A search index that finds items with similar numerical representations.

When to use: Use in technical retrieval architecture.

Also called: vector database

verified outcome

A result that has enough evidence to show what happened.

When to use: Use when an outcome has been confirmed rather than merely predicted.

voice and knowledge profile

The approved writing preferences, role context and knowledge sources used to personalize Lithi’s help.

When to use: Use as the preferred plain label for the personalized context previously called an AI Twin or digital twin.

Also called: personalized Lithi profile

voice profile

Approved writing preferences that keep drafts sounding like you or your organization.

When to use: Use for the account or organization baseline. Use recipient profile for one person's examples and choices; never imply identity cloning.

Related terms: recipient profile · learning proposal

watermark

Shows where shared information came from and how people may use it.

When to use: Use for shared-fact provenance and scope cues.

adapter

A smaller set of learned changes that adjusts a base model for a task.

When to use: Use in technical model packaging and provenance.

Advanced

Extra technical controls for people who need to inspect versions, policies and traces.

When to use: Use when naming the disclosure that reveals technical controls.

Agent system

The Advanced view of the software roles, checks, versions and limits used to prepare replies.

When to use: Use for the Advanced view of the roles that prepare replies. Never present worker slugs in normal mode.

AI agent

Software that can work through a defined task using approved tools and rules.

When to use: Use for a bounded software worker. Do not use “agent” for a human Lithi Connect member.

AI assistant

Software that helps a person understand information or prepare work.

When to use: Use when the main role is helping a person rather than independently completing a workflow.

AI model

Software trained to recognize patterns and generate or classify information.

When to use: Use for the underlying model, not the complete product, agent or workflow.

benchmark

A standardized task set used to compare model performance.

When to use: Use in technical comparisons with date, model version and conditions.

checkpoint

A specific saved version of a model’s weights.

When to use: Use when exact model reproducibility matters.

context window

The maximum amount of input and generated text a model can consider in one run.

When to use: Use in technical capacity and model-selection explanations.

evaluation

A structured test of how well a model or agent performs on defined tasks and risks.

When to use: Use for quality and safety assessment, not as a synonym for one anecdotal test.

excessive agency

Giving an AI system more tools, permissions or freedom than it needs for the task.

When to use: Use in agent safety and architecture documentation.

execution boundary

The place and rules that define where an action can run and what it can reach.

When to use: Use when explaining safe agent or tool execution.

grounded answer

An answer backed by approved sources you can open and check.

When to use: Use only when the cited evidence actually supports the answer.

guardrail

A rule or control that limits unsafe or out-of-scope AI behavior.

When to use: Use as an umbrella only when the actual controls are also named.

hallucination

An AI output that states something unsupported, false or invented as though it were reliable.

When to use: Use in technical, support or educational explanations.

hardware tier

A group of devices with enough memory and performance for a defined model workload.

When to use: Use for capability-based routing, not as a judgment of the person who owns the device.

human approval

You check the work and choose what happens next. Approval covers only the exact plan you reviewed.

When to use: Use for any workflow where a person remains the final authority.

inference

Running a trained model to produce an answer, score or classification.

When to use: Use in technical explanations; use “the AI runs on your Mac” in plain customer copy.

latency

How long a system takes to start or finish a result.

When to use: Use with the exact measured boundary and percentile.

Lithi CLI tools

Command-line tools for approved technical inspection and management tasks.

When to use: Use in technical documentation only; public technical pages may show customer-supported commands, while repository scripts remain internal. Do not expose unsafe commands or imply every operation is available.

Also called: CLI Tools

Lithi Drafter

The fast local agent role that prepares a first draft or classification.

When to use: Use for the named drafting tier, not a fixed model slug.

Lithi Edge Agents

The named Lithi agents that run eligible work on approved Macs.

When to use: Use on connector and technical-public surfaces when provenance and hardware execution matter.

Lithi Edge Pack

The signed package that installs the approved local agent runtime and its supporting files.

When to use: Use for the installable agent package on eligible Connector Macs.

Lithi Heavy

The higher-capacity local agent tier for work that needs more context or reasoning.

When to use: Use for the named high-capacity tier without promising a fixed model or speed.

Lithi local agents

The small, specialized AI helpers inside Lithi that prepare, check and organize work on a Mac.

When to use: Use as the plain umbrella for on-Mac Lithi agent roles.

Lithi MCP tools

Approved Lithi functions made available to compatible AI applications through MCP.

When to use: Use in technical documentation only for mounted, tested tools.

Also called: MCP Tools

Lithi Reviewer

The local agent role that checks a result for fit, tone, quality and policy issues.

When to use: Use for the named automated review tier.

local AI agent

A software helper that does one kind of AI work on your Mac.

When to use: Use when the model inference genuinely runs on the local Mac and the sentence names any external connections separately.

local inference

Your device runs the model work instead of sending it to a hosted service.

When to use: Use when the current runtime evidence proves on-device execution for the named operation.

MCP client

The application that connects to an MCP server and makes approved requests.

When to use: Use in technical MCP documentation.

MCP prompt

A reusable prompt template an MCP server makes available to a client.

When to use: Use for MCP-provided prompt templates.

MCP resource

Context or data an MCP server makes available for an application or model to use.

When to use: Use for MCP-provided context, not executable functions.

MCP server

A service that exposes approved tools, resources or prompts through MCP.

When to use: Use in technical MCP documentation.

MCP tool

A function an MCP server allows an AI application to request.

When to use: Use for executable MCP capabilities.

Metal

Apple’s graphics and compute technology used by software to access GPU capabilities.

When to use: Use in technical hardware and runtime documentation.

MLX

Apple’s machine-learning framework for efficient model work on Apple silicon.

When to use: Use in technical implementation and provenance documentation only.

Model Context Protocol

A standard way for AI applications to discover approved tools, prompts and context from a server.

When to use: Spell out on first use, then use MCP.

Also called: MCP

model provenance

The record of where a model came from and how Lithi packaged or changed it.

When to use: Use in settings, trust, release and technical documentation.

model version

The specific release of a model used for a result.

When to use: Use in provenance, receipts and evaluation evidence.

model weights

The learned numerical values that make up a trained model.

When to use: Use in technical model packaging and provenance discussions.

Also called: weights

on-device

Your current device runs the named operation.

When to use: Use before a noun only when the named operation genuinely runs on that device; state external connections separately.

open-weight model

A model whose trained parameter files are available under stated license terms.

When to use: Use when describing model availability or provenance precisely.

output validation

Lithi checks an AI-produced result before another system shows, stores or uses it.

When to use: Use in agent, tool and integration workflows.

policy pack

A versioned set of rules that limits what an agent may do and how it must respond.

When to use: Use in agent-release and technical governance documentation.

prompt

The instructions and information given to a model for one task.

When to use: Use in AI and technical documentation.

prompt injection

Malicious or misleading content that tries to make an AI system ignore its rules or reveal or perform something it should not.

When to use: Use in AI security and trust documentation.

prompt pack

A versioned set of approved prompt templates for a Lithi agent release.

When to use: Use in Lithi Edge Pack and agent-release documentation.

prompt template

A reusable structure that turns task data into consistent model instructions.

When to use: Use for reusable model instruction templates.

quantization

Reducing the numerical precision of a model so it uses less memory and can run faster.

When to use: Use when explaining local hardware fit and model packaging.

Also called: quantization

refusal

The agent declining a request because it is unsafe, unauthorized, unsupported or outside scope.

When to use: Use for a clear policy-based non-action.

sensitive information disclosure

Private or restricted information being exposed to someone or something that should not receive it.

When to use: Use in AI security and privacy documentation.

system instruction

A high-priority instruction that defines how a model should behave for a task.

When to use: Use in technical AI documentation.

Also called: system prompt

throughput

How much work a system completes in a period of time.

When to use: Use with the unit, workload and test conditions.

tool

A defined function an agent may request to use, such as searching approved data or creating a draft.

When to use: Use for callable agent capabilities; name the specific tool when possible.

tool calling

A model producing a structured request for the application to run a tool.

When to use: Use in technical agent documentation.

tool permission

The rule that says whether an agent may use a particular tool for a particular task.

When to use: Use when explaining or implementing agent authority.

Admin

The person on a customer team who manages the settings the owner has allowed.

When to use: Use for the named product role and list its exact permissions in the current role matrix.

capability

Retired vocabulary for a capability path; it is not authoritative. Use scoped capability grant instead.

When to use: Keep only for history and search; use capability for the current server grant.

Also called: capability / certified

customer

A person or organization using a Lithi customer product.

When to use: Use in general customer-facing explanations; use “customer organization”, “organization owner” or “member” when precision is needed.

customer organization

A business or other organization using Lithi under one governed account.

When to use: Use when describing organization-level settings, billing, roles or data scope.

Also called: customer org

HR

The customer-team role responsible for approved people-policy mappings and access-lifecycle signals.

When to use: Spell out human resources on first use outside a familiar team-role table, then use HR.

human reviewer

A person who checks what the AI prepared before it goes ahead.

When to use: Use whenever a human decision is required, especially for sends, permissions, money, publication or sensitive changes.

IT Admin

A person responsible for deploying, configuring and supporting Lithi devices for an organization.

When to use: Use for organization-side technical deployment and device management responsibilities.

Manager

A person allowed to view or manage a defined team or workflow.

When to use: Use only when the current role contract defines what the manager can see or do.

member

A person who belongs to a Lithi customer organization or, when explicitly stated, to Lithi Connect.

When to use: Use for people inside a defined organization or program; introduce the scope at first use.

organization owner

The person responsible for the organization account and its highest-level settings.

When to use: Use only when the current contract grants the stated organization-level action.

Also called: org owner

Security Admin

A person responsible for security settings, evidence and access rules.

When to use: Use when the action is security-specific and the current permission contract grants it.

Viewer

A person who can see approved information but cannot change it.

When to use: Use for read-only access and name the scope when it matters.

accessible name

The name assistive technology uses to identify a control or element.

When to use: Use in accessibility tests for interactive elements and images.

AI-share action

A page-menu action that lets a reader share the validated page source with a preferred AI assistant.

When to use: Use for the Copy/View Markdown and Ask-AI menu behavior; keep provider URL construction and query details out of article copy.

Also called: Ask-AI action

alternative label

An accepted synonym, abbreviation or spelling variant that points to the preferred term.

When to use: Use for genuine synonyms and abbreviations; do not use for misleading or banned phrases.

Also called: SKOS altLabel

alternative text

Text that communicates the purpose or meaning of non-text content.

When to use: Use for meaningful non-text content and describe function or information rather than appearance alone.

Also called: alt text

breadcrumb

A short navigation trail showing where the current page sits in the site.

When to use: Use on nested documentation, help and trust pages; make every linked ancestor valid.

breakpoint

Lets a layout change when the screen reaches a defined width.

When to use: Use only when the content layout needs a deliberate change.

browser zoom

A browser control that enlarges or reduces page content.

When to use: Use when specifying accessibility test levels such as 200% or 400%; do not confuse it with operating-system display scaling.

Also called: zoom

call to action

A clear invitation to take a useful next step.

When to use: Spell out on first use, then use CTA in technical copy.

Also called: CTA

canonical URL

The preferred public URL for a page when more than one URL could show similar content.

When to use: Use one canonical URL per indexable page and keep redirects and metadata aligned to it.

clay canvas

The quiet warm-neutral page background used across the Lithi public website.

When to use: Use as a design-system term, not as marketing copy.

color contrast

The visual difference between foreground content and its background.

When to use: Use with the applicable WCAG criterion, element type and measured ratio.

Also called: color contrast

copy key

A stable identifier used by software to retrieve approved wording.

When to use: Use for repeated UI or content copy so wording is governed once.

DefinedTerm

A Schema.org object representing one glossary concept.

When to use: Use when projecting glossary entries into public structured data.

DefinedTermSet

A Schema.org object representing a glossary or controlled vocabulary.

When to use: Use for the public Lithi glossary structured-data projection.

design token

A named design value reused across components, such as a color, spacing or radius.

When to use: Use instead of copying raw values into many files.

embedded tab

A distinct content view shown inside a shared page rather than at a separate rendered page.

When to use: Use for trust or documentation content that is logically distinct but compositionally embedded.

focus indicator

The visible outline or change showing which control currently has keyboard focus.

When to use: Use and test for every keyboard-focusable control.

hidden label

A misspelling, retired label or internal code kept only so search and migration can find the right concept.

When to use: Use for legacy, typo and internal search aliases.

Also called: SKOS hiddenLabel

HTML

The markup language used to structure web pages and their meaning.

When to use: Spell out the term on first use for non-technical readers, then use HTML.

impact CTA

A selectively emphasized primary action used only for a small number of high-value conversion moments.

When to use: Use only on centrally allowlisted high-value routes; never as the default button style.

JSON-LD

A common format for adding linked structured data to a web page.

When to use: Spell out or explain on first use outside technical audiences.

keyboard trap

A place where keyboard focus enters a control or region but cannot move out normally.

When to use: Use in accessibility requirements, testing and defect reports.

llms.txt

A proposed website file that gives AI systems a concise map of useful public content.

When to use: Use as an experimental public-content index and label its support honestly.

locked copy

Wording that must remain exactly the same until its owner approves a new version.

When to use: Use for money, legal, security or other sensitive statements whose exact wording is controlled.

Markdown-first page

A public page authored in plain Markdown first so its readable source can project consistently to the page and related outputs.

When to use: Use for the governed page authoring model; do not claim that every existing route has migrated to it.

Also called: Markdown-first document

metadata

Information about a page, such as its title, description, language and sharing image.

When to use: Use for page description and discovery fields; keep claims aligned with body copy.

minimum target size

The minimum clickable or tappable area needed for a control to be comfortable and reliable to use.

When to use: Use in component and responsive acceptance tests.

mobile-first

Designing the smallest-screen reading order and controls first, then expanding the same meaning for larger screens.

When to use: Use as an implementation principle, not a claim that the product itself runs on mobile.

Open Graph metadata

Page information used to create a social or messaging link preview.

When to use: Use for accurate previews; do not make stronger claims than the page body.

page deck

The short introduction below a page title that answers what the reader can do or understand here.

When to use: Use for the one visible page introduction; write it as an answer, not as a repeated metadata description or status line.

Also called: hero deck

PDF

A fixed-layout document format designed to preserve a document’s appearance across systems.

When to use: Use for downloadable fixed-layout documents; name whether the file is sample, generated, signed or authoritative.

plain language

Writing that helps the intended reader find, understand and use the information the first time.

When to use: Use as the default writing standard for all public and UI copy.

PNG

A lossless raster image format commonly used for screenshots and graphics.

When to use: Use for approved raster assets such as screenshots; provide useful alternative text when the image conveys meaning.

preferred label

The one approved name used for a concept in a language and context.

When to use: Use as the displayed glossary term and copy-authority name.

Also called: SKOS prefLabel

primary action

The most useful next step on the current page.

When to use: Use one clear primary action per page or decision surface.

quiet eyebrow

A small orientation label above a title that tells the reader where they are or what type of page this is.

When to use: Use for page orientation only.

Read next

A contextual link to the most useful next page after the current one.

When to use: Use to continue the reader’s task or learning journey.

reading measure

The width of a line of body text, kept comfortable for reading.

When to use: Use for prose-heavy pages and documentation.

redirect

A rule that sends an old or alternate URL to the current destination.

When to use: Use for intentional route changes and preserve the correct status and canonical destination.

reduced motion

A user preference to limit or remove non-essential animation.

When to use: Use and test whenever a component includes motion.

reflow

Content adapting to a narrow or enlarged view without forcing two-dimensional scrolling for ordinary reading.

When to use: Use in responsive and zoom testing; state viewport, zoom and any justified exception.

render route

The page entry that actually renders a public route or embedded view.

When to use: Use in technical route reconciliation when public and rendering routes differ.

responsive design

A layout that adapts clearly to mobile, tablet, desktop, zoom and print without losing meaning.

When to use: Use for cross-device behavior; test content, not only component boxes.

robots.txt

A website file giving compliant crawlers instructions about which paths they may crawl.

When to use: Use for crawler guidance, never to protect private data.

route

The public URL path or logical destination for a page or action.

When to use: Use for public navigation and route registries; distinguish route from source file.

scope note

A short rule explaining where a term applies and how it differs from similar terms.

When to use: Use whenever a correct term could still be misleading outside its intended context.

screen reader

Software that presents digital content through speech, braille or another non-visual output.

When to use: Use when describing compatibility or human testing; never treat one automated scan as screen-reader proof.

search engine optimization

Helping search systems and people understand, find and navigate content.

When to use: Spell out on first use, then use SEO.

Also called: SEO

secondary action

A quieter alternative next step for someone not ready for the primary action.

When to use: Use only when it serves a distinct visitor need.

selective glass

A restrained translucent surface used only where it improves hierarchy.

When to use: Use at most where the shared component contract permits it; never build every section as glass cards.

semantic token

A design token named for its purpose, such as text-primary or surface-soft.

When to use: Use for component APIs and theming; avoid naming only by raw color or size.

sitemap

A machine-readable list of public URLs a site wants crawlers to discover.

When to use: Use for crawl discovery; do not include blocked, duplicate or private routes.

slug

The readable part of a URL that identifies a page or item.

When to use: Use lowercase, durable, human-readable slugs; avoid dates or jargon unless meaningful.

source-attributed copy

Wording linked to the source that supports it.

When to use: Use for factual statements that may change or require verification.

structured data

Machine-readable information describing what a page is about.

When to use: Use when a recognized schema type accurately represents the content.

SVG

A scalable vector format for graphics that remain sharp at different sizes.

When to use: Use for logos and code-rendered diagrams when vector scaling and semantic control are useful.

terminal CTA

The one final action that gives an action-bearing page its clear next step.

When to use: Use for an action-bearing page's final decision; keep any secondary action distinct and never duplicate its destination elsewhere.

Also called: terminal call to action

text alternative

Text that communicates the purpose or information of non-text content.

When to use: Use for meaningful visuals; use empty alternatives only for genuinely decorative content.

URL

The web address of a page, file or other resource.

When to use: Spell out the term on first use for non-technical readers, then use URL.

audit trail

A history showing who or what changed something and when.

When to use: Use for governance and compliance history; use “Lithi Receipt” for the public proof of one action.

evidence

Information that supports or challenges a statement, decision or outcome.

When to use: Use instead of “proof” when the material supports a decision but does not independently establish it.

evidence pack

A grouped set of records used to review one change, workflow or claim.

When to use: Use in implementation, review and release processes.

Lithi Receipt

Every accepted Agent Network task leaves a timestamped receipt showing what Lithi did and where relevant data stayed.

When to use: Use as the public name for action proof; show the plain explanation before any type code.

Also called: Proof available

Lithi Receipt ID

The non-content identifier used to find one Lithi Receipt.

When to use: Use when linking, downloading or discussing one receipt.

Also called: receipt ID

log

A timestamped technical record produced while software runs.

When to use: Use for diagnostic records, not as the authoritative business event unless designated.

LTH identifier prefix

The shared `LTH` prefix used by several Lithi public identifier families.

When to use: Use when teaching people how to distinguish Lithi identifier families; never assume every `LTH-` value is a receipt.

Also called: LTH

Related terms: Lithi Receipt ID

metric

A measured number used to understand performance, quality or outcomes.

When to use: Use only with a definition and denominator where applicable.

observability

The ability to understand what a system is doing from its recorded signals.

When to use: Use for system understanding; do not claim observability from one dashboard or health endpoint.

proof

Evidence that supports a specific statement about what happened.

When to use: Use with the exact claim named and the evidence made inspectable.

read-back

Checking the stored result after a write or change rather than assuming it succeeded.

When to use: Use in completion and migration criteria.

receipt digest

A cryptographic fingerprint used to bind receipt evidence to a result or state without publishing the private content itself.

When to use: Use when explaining receipt integrity and content minimization.

receipt type

The category showing what kind of action a receipt records.

When to use: Use the plain category in normal copy and expose the code in technical details or receipt IDs.

replay

Running a recorded event or request through a controlled test again.

When to use: Use for debugging, recovery and verification; never replay production side effects blindly.

span

One timed operation inside a trace.

When to use: Use in technical tracing documentation.

trace

A linked view of technical operations that handled one request or workflow path.

When to use: Use for technical request-path analysis, not as a synonym for a business receipt.

verified work

A timestamped action tied to a customer outcome with enough evidence to count.

When to use: Use for contributor work only after the verification rule passes.

Also called: verified work / proof

accessibility

Designing information and interactions so people with a wide range of disabilities can perceive, understand and use them.

When to use: Use as an end-to-end requirement, not a single automated score.

active consent

Consent given through a clear affirmative action rather than silence or a preselected choice.

When to use: Use for non-essential storage or comparable optional processing where applicable.

AES-256

The Advanced Encryption Standard using a 256-bit key.

When to use: Use for the algorithm family only; use AES-256-GCM when the verified mode is Galois/Counter Mode.

Related terms: AES-256-GCM

AES-256-GCM

An authenticated encryption method using the Advanced Encryption Standard with a 256-bit key.

When to use: Use only for data and components whose current implementation proves this algorithm.

App Sandbox

An Apple security control that limits which resources a Mac app can access.

When to use: Use when the current target and entitlements prove sandboxing; list important exceptions or helper boundaries where material.

attribute-based access control

Granting or denying access using attributes such as organization, device, purpose, capability or resource state.

When to use: Spell out on first use, then use ABAC in technical documentation.

Also called: ABAC

CAA record

A DNS record stating which certificate authorities may issue certificates for a domain.

When to use: Spell out the abbreviation on first use and use it only for the current domain evidence.

CIDR

A notation for an IP network range, such as 10.0.0.0/24.

When to use: Use only in technical network configuration; spell out on first use if the audience may not know it.

Also called: Classless Inter-Domain Routing

code signing

Cryptographic signing that lets a system verify who signed an app and whether its code changed.

When to use: Use for build and distribution integrity; name the signing identity or policy only in technical evidence.

consent

A person’s freely given, specific, informed and unambiguous agreement to a defined use.

When to use: Use with the exact purpose and withdrawal path; do not treat continued browsing as consent.

Customer Content

Content a customer supplies, connects or generates through an approved Lithi product workflow.

When to use: Use only with the current contractual definition and do not treat it as a synonym for all customer data.

Customer Personal Data

Personal data processed for a customer under the customer relationship and applicable agreement.

When to use: Use only with the current contractual definition; do not infer the scope from the capitalized label.

data minimization

Collecting and using only the data needed for the stated purpose.

When to use: Use as a design and review rule across forms, analytics, logs, AI context and support.

data protection law

A law controls how organizations collect, use, share, secure and retain personal data.

When to use: Use in legal definitions; name the exact law when making an obligation or compliance statement.

Also called: Data Protection Laws

data region

A named geographic area used for a specifically scoped data or service operation.

When to use: Use with the data class, service, provider, effective date and transfer boundary.

data residency

Names the countries or regions where an organization stores or processes a defined data class.

When to use: Use only with the data class, environment and current provider evidence named.

data subject

A person whose personal data an organization processes.

When to use: Use in legal and privacy content; use “person” in ordinary product copy unless the legal role matters.

Data Subject Access Request

A request from a person to exercise applicable rights over their personal data, such as access.

When to use: Spell out on first use, then use DSAR; do not promise a universal right or deadline without legal context.

Also called: DSAR

data subject request

A person’s request to exercise an applicable privacy right over their personal data.

When to use: Use as the umbrella; name the specific right and jurisdiction when known.

Also called: Data Subject Request, DSR

Related terms: Data Subject Access Request

default deny

Blocks access until an approved rule explicitly allows it.

When to use: Use for access-control design only when the implementation behaves this way.

encrypted in transit

Encryption protecting data while it travels on a named protected network path.

When to use: Use only with the named protected path and current evidence.

encryption at rest

Encryption protecting stored data on disk or in a database.

When to use: Use with the data class, environment and key boundary named; do not claim “all data” without evidence.

encryption in transit

Encryption protecting data while it travels between systems.

When to use: Use with the path and protocol version named when verified.

envelope encryption

Encrypting data with one key and protecting that key with another managed key.

When to use: Use only where the current key architecture implements it.

fingerprinting

Combining device or browser characteristics to recognize or single out a person or device.

When to use: Use in privacy and analytics prohibitions; do not deploy cross-context fingerprinting without explicit approved authority.

Gatekeeper

A macOS security feature that checks downloaded software before it runs.

When to use: Use in Mac installation and trust guidance.

HMAC

A keyed cryptographic code used to verify that data came from someone holding the shared secret and was not changed.

When to use: Spell out on first use in general documentation and name the algorithm where relevant.

HSTS

A browser security policy that tells supported browsers to use HTTPS for a site.

When to use: Use in technical web-security documentation and do not claim deployment without header evidence.

international data transfer

Makes personal data available in another country or legal jurisdiction.

When to use: Use in legal/privacy copy with jurisdiction-specific review.

ISO certification

Independent confirmation by a certification body that an organization meets a named ISO standard within a stated scope.

When to use: Use only with the certified entity, standard, scope, certification body and current evidence.

ISO standard

An International Standard published by ISO after expert agreement.

When to use: Name the exact standard and edition; never use “ISO” alone as proof of Lithi compliance.

key rotation

Replacing a cryptographic key according to a defined schedule or security event.

When to use: Use with the key class and process named.

Keychain

The Apple system for storing passwords, keys and other credentials securely on a device.

When to use: Use for Apple credential storage only when the implementation uses Keychain.

least privilege

Giving a person, service or agent only the access needed for the current job.

When to use: Use as a design and review rule for accounts, tools, models and integrations.

MDM deployment

Deploying and configuring Lithi through an organization’s mobile device management system.

When to use: Use for the deployment workflow; spell out mobile device management on first use.

Also called: MDM Deployment

mobile device management

Software used by an organization to configure and manage approved devices.

When to use: Spell out on first use, then use MDM; name supported deployment controls only when evidenced.

Also called: MDM

multi-factor authentication

Signing in with evidence from more than one factor, such as a password plus a security key or authenticator.

When to use: Spell out on first use, then use MFA; name supported factors only when evidenced.

Also called: MFA

Mutual Non-Disclosure Agreement

A contract in which both parties agree to protect defined confidential information.

When to use: Spell out on first use, then use MNDA; do not imply one exists until executed.

Also called: MNDA, NDA

non-essential cookie

A cookie not strictly necessary to provide the service the person requested.

When to use: Use in consent controls and policies; classify by purpose, not vendor preference.

notarization

Apple’s automated service for checking and recording software distributed outside the Mac App Store.

When to use: Use British spelling in en-GB copy and “notarization” in en-US; do not call it Apple approval of product claims.

Also called: notarization

OAuth

A standard way for an application to receive limited access to a service without receiving the person’s password.

When to use: Use for delegated provider access and name the scopes and revocation path.

OpenPGP

An open standard for encrypting or digitally signing messages and files using public-key or symmetric cryptography.

When to use: Use for the disclosure encryption key or compatible encrypted messages; say PGP only as a familiar shorthand after first use.

Also called: PGP

personal data breach

A security breach causing accidental or unlawful loss, change, destruction, disclosure of or access to personal data.

When to use: Use in incident and legal procedures; do not substitute “incident” when the legal threshold matters.

Also called: Personal Data Breach

processing of personal data

Any operation performed on personal data, from collection and use to storage, sharing or deletion.

When to use: Use in legal and privacy explanations; use a specific verb in ordinary product copy.

purpose limitation

Using personal data only for clear, specified and compatible purposes.

When to use: Use in privacy, analytics, knowledge and AI governance.

redacted support bundle

Removes or masks private content before someone shares diagnostic information with support.

When to use: Use only where the person can see what is included and the implementation enforces the redaction policy.

RFC

A numbered publication in the Internet technical-document series maintained through the RFC Editor.

When to use: Spell out Request for Comments on first use for general audiences, then cite the exact RFC number.

role-based access control

Granting permissions according to a person’s approved role.

When to use: Spell out on first use, then use RBAC; name the role and action rather than saying “admin access”.

Also called: RBAC

row-level security

Database rules that decide which rows a request may read or change.

When to use: Spell out on first use, then use RLS; treat it as one control in a wider access model.

Also called: RLS

secret

Sensitive value used to authenticate or protect access, such as a private key, password or API credential.

When to use: Use as the umbrella only when the specific secret type cannot be named safely.

Secure Enclave

A hardware-based security component on supported Apple devices that can protect certain cryptographic operations and keys.

When to use: Use only with current hardware and implementation evidence.

security key

A physical authentication device used as a strong sign-in factor.

When to use: Use for supported hardware authentication and name the compatible standard or product only when verified.

security.txt

A standard text file that tells security researchers how to report a vulnerability.

When to use: Use for the published disclosure-discovery file and link it to the responsible-disclosure policy.

sensitive data

Information that could cause greater harm or requires stronger protection if misused or exposed.

When to use: Use as an umbrella only when the data classes are also named.

Service Level Agreement

A contract that states measurable service commitments and the remedies or process when they are not met.

When to use: Spell out the term on first use, then use SLA. Publish only with current legal and commercial approval.

Also called: SLA

SHA-256

A cryptographic hash that turns data into a 256-bit fingerprint.

When to use: Use for checksums and hashes with the purpose stated.

signed for integrity

A cryptographic signature showing that an approved message or result envelope has not been silently changed after signing.

When to use: Use when describing signed envelopes and integrity checks.

single sign-on

Using one organization identity service to sign in to multiple approved applications.

When to use: Spell out on first use, then use SSO; do not claim support without current integration evidence.

Also called: SSO

Standard Contractual Clauses

European Commission-approved contract clauses used as one safeguard for certain international personal-data transfers.

When to use: Spell out on first use, then use SCCs; never imply they alone make every transfer lawful.

Also called: SCCs, SCC

storage and access technology

Technology that stores information on, or reads information from, a person’s device, including many cookies and similar identifiers.

When to use: Use in UK consent and analytics documentation rather than treating cookies as the only technology in scope.

subprocessor

Another organization a processor uses to help process personal data.

When to use: Use provider names only in the current approved subprocessor authority.

TLS

Transport Layer Security, the protocol used to protect many network connections such as HTTPS.

When to use: Spell out on first use for non-technical readers and claim a version only for verified paths.

Also called: Transport Layer Security

UK International Data Transfer Addendum

A UK transfer safeguard that can supplement certain contract clauses for restricted UK personal-data transfers.

When to use: Use only in legal documentation with current legal review.

Also called: UK Addendum

VPAT

A standard template used to document how a product supports accessibility criteria.

When to use: Spell out on first use and do not claim one exists until an approved report is published.

WCAG 2.2

The current W3C Web Content Accessibility Guidelines version used as the public-web accessibility target.

When to use: Use for web accessibility requirements and state the target level where approved.

Web Content Accessibility Guidelines

The W3C guidelines for making web content more accessible to people with disabilities.

When to use: Spell out on first use, followed by WCAG; name the version and level when stating a target or result.

Also called: WCAG

XPC

Apple’s mechanism for communication between separate local processes or services.

When to use: Use in technical macOS architecture; explain as “isolated helper service” in plain copy.

Also called: XPC service

zero trust

A security approach that does not grant trust merely because something is inside a network or previously connected.

When to use: Use as an architecture approach and name the implemented controls.

accessibility test

A test checking whether people using different input methods or assistive technologies can use the experience.

When to use: Use as an umbrella only when the actual test methods are listed.

blocked

Policy, permission, safety or an owner gate prevents the action.

When to use: Use with the blocking rule and next authorized step.

BLOCKED verification state

The named verification or action could not proceed because of a stated dependency or gate.

When to use: Use exactly in verification records with the blocker named.

Also called: BLOCKED

canceled

The work was deliberately stopped before completion.

When to use: Use with actor, time and side-effect handling where relevant.

completed

The defined work finished successfully and passed its terminal checks.

When to use: Use only after required read-back and receipt creation.

contract test

A test that confirms data or interface behavior matches its declared contract.

When to use: Use for API, event, component and workflow contracts.

deferred

The work is intentionally waiting for a required condition or safe capacity.

When to use: Use with the condition and review or expiry time.

deployment

Putting an approved software version into an environment where it can run.

When to use: Use only for an actual deployment; creating an archive is not deployment.

deterministic safety validator

A rule-based check that gives the same result for the same validated input and rule version.

When to use: Use instead of unexplained “L1” on public or support surfaces; name the checked rule family where useful.

diagnostic

A safe check used to understand why something is not working as expected.

When to use: Use for checks; distinguish diagnostics from fixes.

downloadable document pack

A versioned set of approved guides sent or made available together for a specific stage, such as before orientation.

When to use: Use when several related documents form one intentional pack; name the included documents and version.

Also called: doc pack, starter docs

empty

The request succeeded, but there are currently no items in this defined scope.

When to use: Use only after a successful read; include a useful next step where possible.

end-to-end test

A test of a complete user or system journey from start to final outcome.

When to use: Use only when the whole declared path is exercised.

error

A problem prevented or degraded the requested result.

When to use: Use with a plain explanation and next step; never show only a code.

fail closed

When a required check cannot complete safely, the action stops instead of continuing by default.

When to use: Use only when the actual failure path has been tested for the named operation.

Also called: fails closed

failed

The work ended without the intended result.

When to use: Use with a plain reason, safe retry rule and support path.

hostile-path test

A test deliberately using invalid, malicious, repeated or out-of-order input to confirm the system fails safely.

When to use: Use for security and reliability verification.

Ideal Customer Profile

A defined description of the organizations most likely to benefit from a product or campaign.

When to use: Spell out on first use, then use ICP; distinguish it from an individual person profile.

Also called: ICP

incident

An event that harms or threatens service, security, privacy or customer outcomes and needs coordinated response.

When to use: Use according to the incident policy and avoid minimizing or exaggerating impact.

incident severity

A measure of an incident’s current impact, scope and risk.

When to use: Use with the current incident rubric; do not infer severity from a task’s P-number.

integration test

A test of two or more real components working together.

When to use: Use when dependencies are genuinely integrated; state which are real or simulated.

Lithi Doctor

The diagnostic system that checks whether Lithi is installed, healthy, secure and connected as expected.

When to use: Use for the named diagnostic system; state that sensitive changes still need a person.

Lithi Support

The official help function for product issues, account questions and approved support requests.

When to use: Use for official product support; do not assign product support responsibility to Connectors or Customer Success by default.

Lithi Support Agent

Walks you through diagnostics with your permission. It does not read your private email or team knowledge by default.

When to use: Use only for the implemented support agent and state what it can inspect.

Lithi Test Lab

The testing system used to prove changes before release and detect regressions.

When to use: Use for the named quality system; passing one test type is not end-to-end proof.

loading

The system is actively trying to retrieve or prepare the information.

When to use: Use only while work is in progress and provide an accessible status.

materialized view

A stored result of a database query that can be refreshed for faster reads.

When to use: Use in database architecture and spell with “s” in en-GB, “z” in en-US where required.

Also called: materialized view

not checked

The system has not yet verified this value or capability.

When to use: Use instead of a fabricated number, zero or “working” state.

NOT_AUTHORISED verification state

The current task or actor did not have authority to perform the named action.

When to use: Use exactly where lack of authority—not technical failure—prevented action.

Also called: NOT_AUTHORISED

NOT_RUN verification state

The named verification or action was not performed.

When to use: Use exactly in verification records; it is not a pass or fail.

Also called: NOT_RUN

P0 priority

The highest-priority defect class in a defined Lithi work or bug-tracking rubric.

When to use: Use only after defining the current rubric; in general public copy prefer “highest-priority defect”.

Also called: P0

P1 priority

A high-priority defect class below P0 in a defined Lithi work or bug-tracking rubric.

When to use: Use only after defining the current rubric; in general public copy prefer “high-priority defect”.

Also called: P1

partial

Some expected information is available, but the result is incomplete.

When to use: Use with the missing portion and consequence explained.

paused

The work is temporarily stopped and can resume under the defined rule.

When to use: Use with the reason, such as battery, thermal or user choice.

priority

The order in which work should be addressed based on impact, urgency and dependency.

When to use: Use with an explicit scale and rationale; do not assume that P0 or P1 means the same thing in every system.

production proof

Evidence from the real released environment showing a defined capability or outcome works as claimed.

When to use: Use only when the released environment and exact claim were observed.

publication

Making approved content publicly available.

When to use: Use only after the public content is actually available and verified.

queued

Lithi accepted the work and is waiting to start it.

When to use: Use only after durable acceptance; show cancellation or priority rules if relevant.

rollup

A summary created from more detailed records, such as counts or totals.

When to use: Use with the aggregation rule and source named.

running

The work has started and has not reached a terminal state.

When to use: Use for active execution and provide progress only when measured.

safe review path

The ordered checks and fallback decisions an eligible action must pass before it can continue.

When to use: Use when explaining the complete review sequence rather than one validator.

Related terms: deterministic safety validator · semantic safety review · fail closed

self-heal

A safe, pre-approved fix the system may apply automatically for a known problem.

When to use: Use only for fixes explicitly approved for automatic execution; never imply unlimited repair authority.

semantic safety review

A meaning-based review for risks that simple rules may not catch.

When to use: Use instead of unexplained “L2”; do not name a provider or model family unless the current runtime evidence supports it.

stale

The information may be out of date under the current freshness rule.

When to use: Use with the last checked time and refresh path.

success

The stated action completed and its result was confirmed.

When to use: Use only for the specific confirmed action, not general system health.

support bundle

A diagnostic package prepared to help investigate a product issue.

When to use: Use only with the exact included data classes stated.

support request

A recorded request for help with a specific issue or question.

When to use: Use for a formal support case; avoid placing private message bodies in general analytics.

test fixture

A controlled sample input or system state used to run a repeatable test.

When to use: Use in test and verification documentation.

unavailable

Lithi cannot currently provide the information or action.

When to use: Use when a dependency, permission or contract is absent; do not render a real-looking zero.

unit test

A test of one small piece of logic in isolation.

When to use: Use for isolated logic; do not call it end-to-end proof.

Vault

A general label for an approved secure secret store.

When to use: Prefer “secure secret store” in plain copy; use a product name only when evidenced.

verification

Checking evidence against a defined requirement or expected result.

When to use: Use for what was actually checked; do not turn presence of code into proof it works.

visual regression test

A test comparing rendered interfaces to detect unintended visual changes.

When to use: Use for visual changes and keep human review for meaningful differences.

warning

Attention is needed, but the current task may still continue safely.

When to use: Use with text and an icon; color must not be the only signal.