> ## Documentation Index
>
> Fetch the complete documentation index at: https://lithi.ai/llms.txt
>
> Use this file to discover all available pages before exploring further.

# Lithi Glossary

## Agent Network Routing And Edge

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

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

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

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

**consensus review** — Independent approved checks agreeing strongly enough for the defined task.

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

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

**distributed Mac fleet** — The member-owned, opted-in Apple-silicon Macs eligible for approved connector-network work.

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

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

**Lithi cloud backup** — Runs an allowed task on an approved hosted path when no safe eligible Mac can accept it.

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

**Lithi Routing Service** — The coordination service that chooses the safest available place for an approved task.

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

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

**No-Void outcome** — The rule that every task ends in a valid result: run safely, use approved backup, wait, or stop.

**opt-in** — A person actively choosing to enable an optional feature.

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

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

**Routing Priority** — The order in which eligible work is offered or assigned among qualified people or devices.

**Sealed Task** — An approved task packaged so the receiving Mac receives only the information required for that task.

**spare capacity** — Mac power that is free when you are not using it.

**swarm coordination** — The way approved Macs and services divide, check and combine eligible network work.

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

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

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

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

## Analytics Experiments And Measurement

**account start** — A person began the approved account or setup journey.

**action ID** — Identifies the visitor action that measurement records track.

**analytics event** — A small, structured record that a defined interaction or outcome occurred.

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

**confidence interval** — A range showing the uncertainty around an estimated effect.

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

**consented visitor ID** — Identifies a visitor only after the required consent or lawful basis applies.

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

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

**CTA click** — A person activated a tracked action.

**CTA impression** — A tracked action became viewable under the defined threshold.

**current-touch attribution** — The most recent eligible source associated with the current journey or conversion.

**destination ID** — The stable identifier for where an action leads.

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

**download start** — A person initiated an approved download.

**event deduplication** — Preventing the same logical interaction or outcome from being counted twice.

**event envelope** — The common set of fields carried by every analytics event.

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

**first-touch attribution** — Credit assigned to the first recorded eligible source in a journey.

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

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

**form submit success** — The receiving system confirmed that the form submission succeeded.

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

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

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

**outcome metric** — Names the main result an experiment aims to improve.

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

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

**placement ID** — The stable identifier for where an action appeared on the page.

**protected-trait proxy** — A seemingly ordinary data point that closely reveals or stands in for a protected personal characteristic.

**referrer class** — A controlled category describing the broad source of a visit.

**retention period** — Defines how long Lithi keeps a data class before deletion or another approved action.

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

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

**section view** — A meaningful section became viewable under the defined threshold.

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

**treatment** — The alternative experience or rule being tested.

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

**utm_campaign** — The stable campaign name or identifier.

**utm_content** — A controlled label distinguishing creative, placement or link variants.

**utm_id** — A stable campaign identifier used where a name may change.

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

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

## Billing Revenue Commission And Payouts

**ACH bank debit** — A bank payment method that requires explicit customer approval for its stated scope.

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

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

**billing rail** — The approved system or process used to issue and collect a type of payment.

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

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

**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.

**effective spend limit** — The approved maximum spend for a named account, task or period.

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

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

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

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

**Lithi Invoice Ledger** — The governed record of what was invoiced, what cleared and which evidence supports it.

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

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

**per-Mac license** — A license charged for each approved Mac covered by the plan.

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

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

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

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

**Solo plan** — A plan intended for one person using the customer product.

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

**suspended for non-payment** — Access is paused because an applicable charge did not clear under the current terms.

**Team and Enterprise** — The collective label for Lithi’s organization plans when discussing their shared licensing model.

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

## Brand And Ecosystem

**Apple silicon** — Apple-designed processor architecture used in current Mac computers.

**Apple silicon Mac** — A Mac built with an Apple-designed processor.

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

**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.

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

**Demo Workspace** — Try the real Lithi with sample data. You never connect your own inbox.

**distribution loop** — The Lithi Connect side: Connectors and their Macs helping local businesses find and adopt Lithi.

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

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

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

**Help Center** — Search setup guides, troubleshooting steps and practical answers.

**Intel Mac** — A Mac built with an Intel processor.

**iOS** — Apple’s operating system for iPhone.

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

**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.

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

**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.

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

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

**Lithi Technologies** — The full company name, used in formal contexts.

**Local-first routing** — When it can, Lithi tries to use trusted Macs closer to your business.

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

**Mac** — An Apple personal computer that runs macOS.

**macOS** — Apple’s desktop operating system for Mac computers.

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

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

## Connect Growth And Attribution

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

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

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

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

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

**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.

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

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

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

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

**Contacted** — Records an approved first contact action.

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

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

**demo request** — A person asking to see Lithi or receive setup help.

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

**Engaged** — The person has meaningfully responded or interacted.

**enquiry** — A message or request from someone seeking information or help.

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

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

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

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

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

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

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

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

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

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

**Local Business Outreach Plan** — Lithi builds one plan for a matched business. You check the people, messages, timing, sources and stop rules.

**local event** — An approved nearby session, workshop or demonstration connected to Lithi.

**local group matching** — Finding relevant local groups where an approved post may be useful and permitted.

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

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

**Lost** — The opportunity will not move forward in its current form.

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

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

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

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

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

**opportunity** — A qualified potential customer with a real next commercial step.

**opt-out** — A person’s request not to receive a defined category of future communication.

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

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

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

**person–organization membership** — The dated relationship showing that a person holds or held a role at an organization.

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

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

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

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

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

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

**public-web enrichment** — Researching approved public sources to add relevant, source-linked context.

**QR code** — A scannable square code that opens an approved link.

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

**quiet hours** — Times when Lithi pauses or defers a communication.

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

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

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

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

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

**SMS** — A mobile text-message channel.

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

**syndication queue** — Holds approved or proposed posts until a person shares them through a permitted channel.

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

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

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

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

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

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

**warm path** — A genuine relationship or credible shared context that makes an introduction relevant.

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

## Data Workflow And System Architecture

**actor** — The person, service or device requesting or performing an action.

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

**append-only** — The system adds new records without silently changing or deleting existing history.

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

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

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

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

**canonical human ID** — The one approved identifier used to refer to the same human account across the system.

**causation ID** — The identifier of the command or event that directly caused another event.

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

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

**command** — A request to perform a specific action.

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

**content-free metadata** — Small details can describe an event or item. They do not include the private message or file.

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

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

**cryptographic hash** — A one-way fingerprint of data used to detect changes.

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

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

**dead-letter queue** — Holds work that exhausted its allowed processing attempts.

**device ID** — The stable identifier for an approved device record.

**digital signature** — Proves that the private-key holder signed the data and that nobody changed it afterward.

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

**event log** — An ordered record of events that occurred in a system.

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

**forward repair** — Fixing a problem by adding a corrected version or transition rather than rewriting history.

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

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

**idempotency key** — The identifier used to recognize a repeated request as the same logical action.

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

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

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

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

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

**organization ID** — The stable identifier for an organization.

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

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

**queue** — Holds work in order until a worker can process it.

**rate limit** — A cap on how many requests or actions may occur in a period.

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

**read model** — A view of data prepared for a particular screen, report or question.

**redaction** — Removes or masks information that people should not see or share.

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

**retry** — Trying a failed or incomplete operation again under a defined rule.

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

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

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

**schema** — The defined structure and validation rules for data.

**schema version** — The identifier showing which form of a data contract is in use.

**source of truth** — The current authority people should consult for a specific fact or rule.

**state** — The current recognized condition of an item or workflow.

**system of record** — The approved system whose stored value is authoritative for a particular fact or state.

**tamper-evident** — Designed so unauthorized changes can be detected.

**task** — One defined unit of work inside a workflow.

**task ID** — The stable identifier for one task.

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

**tenant ID** — The identifier for a governed customer or operating data scope.

**terminal state** — A state in which the current workflow run is finished.

**trace ID** — An identifier linking technical operations within one distributed trace.

**transition** — An approved change from one state to another.

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

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

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

**workflow run** — One execution of a workflow for a particular item or request.

**workflow run ID** — The stable identifier for one workflow execution.

## EmailOS And SwarmOS Workflows

**Approve** — Accept the current proposed item for its stated next step.

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

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

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

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

**connection host** — The approved customer device that keeps a provider credential and performs permitted provider requests.

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

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

**device activation** — The steps that register a Mac for an approved Lithi account and role.

**draft** — A proposed message you have not sent.

**Edit** — Open the proposed item so you can change it.

**eligible inbound email** — An incoming message that matches the approved rules for Lithi to prepare work from.

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

**human-in-the-loop** — A workflow in which a person reviews or decides at a defined point before the action can continue.

**inbox work** — The reading, organizing and reply-preparation tasks people perform around email.

**knowledge-gap view** — A team view showing which topics lack enough approved information to answer well.

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

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

**local processing boundary** — The clearly named content and operations that stay on approved customer Macs.

**local-first** — Designed to do eligible work on your Mac first, before any external path.

**minimum-cell privacy** — Hiding very small groups in reports so a person cannot be singled out from an aggregate.

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

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

**no-surveillance principle** — Team features should help people find approved knowledge without turning ordinary work into employee surveillance.

**personal connection** — A connected account used only by you, on your own Mac.

**provider connection** — An approved link between Lithi on the Mac and a mail or business service.

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

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

**reply-only draft** — A draft reply prepared inside an existing conversation rather than a new outbound message.

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

**review queue** — The ordered list of drafts and actions waiting for you to check.

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

**Send** — Deliver the reviewed message through the connected email provider.

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

**shared team intelligence** — Approved knowledge and context that helps teammates answer without repeatedly asking one another.

**Skip** — Leave this proposed item undone and move on.

**Smart Controls** — The customer settings that control sources, tone, recipients, copied people and approvals.

**smart folder** — A saved view that groups messages or work matching defined rules.

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

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

## Knowledge Context And Learning

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

**Approved Team Knowledge** — Company knowledge that an authorized person has allowed the team to use for a defined purpose.

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

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

**citation** — A reference showing which source supports a statement.

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

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

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

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

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

**context** — The information supplied to an agent for the current task.

**context assembly** — The step that selects and orders the approved information for a task.

**context pack** — The approved bundle of information assembled for one agent task.

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

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

**embedding** — A numerical representation used to find content with similar meaning.

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

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

**HRIS** — A system for managing employee and workforce information.

**hybrid search** — Search that combines exact-word and meaning-based results.

**keyword index** — A search index that finds exact words and phrases.

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

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

**knowledge conflict** — Two approved sources giving different answers to the same question.

**knowledge gap** — A question the approved knowledge cannot answer well enough yet.

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

**knowledge source** — An approved place or document from which a fact or answer may be drawn.

**learning loop** — The process of using verified outcomes and approved corrections to improve future work.

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

**local index** — A search index stored and used on your Mac.

**memory** — Information a system retains for future use.

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

**per-person scope** — A sharing rule that grants access to a named person rather than a whole team.

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

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

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

**private knowledge** — Knowledge only you, or the approved scope that owns it, can see.

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

**Public source receipt** — A record of the public information used to personalize or enrich a message.

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

**retrieval** — Finding the most relevant approved information for a task.

**retrieval policy** — The rules that decide which sources may be searched and used for a task.

**retrieval-augmented generation** — Generating an answer using relevant source material found at request time.

**semantic search** — Search that looks for similar meaning, not only matching words.

**shared timeline** — A short, team-visible history of approved customer facts and actions.

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

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

**source document** — The original file or page from which knowledge was extracted.

**source fact** — A specific statement taken from an approved source.

**source priority** — The order in which eligible sources should be checked for a particular answer.

**source receipt** — A record of the facts and sources used for a prepared reply.

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

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

**standard operating procedure** — An approved step-by-step way of completing a recurring task.

**team knowledge** — Approved company knowledge that can help authorized teammates answer consistently.

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

**un-share** — You revoke a sharing grant so Lithi stops using it and handles cached answers under the approved policy.

**vector index** — A search index that finds items with similar numerical representations.

**verified outcome** — A result that has enough evidence to show what happened.

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

**voice profile** — Approved writing preferences that keep drafts sounding like you or your organization.

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

## Local AI Agents And Models

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

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

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

**AI agent** — Software that can work through a defined task using approved tools and rules.

**AI assistant** — Software that helps a person understand information or prepare work.

**AI model** — Software trained to recognize patterns and generate or classify information.

**benchmark** — A standardized task set used to compare model performance.

**checkpoint** — A specific saved version of a model’s weights.

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

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

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

**execution boundary** — The place and rules that define where an action can run and what it can reach.

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

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

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

**hardware tier** — A group of devices with enough memory and performance for a defined model workload.

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

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

**latency** — How long a system takes to start or finish a result.

**Lithi CLI tools** — Command-line tools for approved technical inspection and management tasks.

**Lithi Drafter** — The fast local agent role that prepares a first draft or classification.

**Lithi Edge Agents** — The named Lithi agents that run eligible work on approved Macs.

**Lithi Edge Pack** — The signed package that installs the approved local agent runtime and its supporting files.

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

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

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

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

**local AI agent** — A software helper that does one kind of AI work on your Mac.

**local inference** — Your device runs the model work instead of sending it to a hosted service.

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

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

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

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

**MCP tool** — A function an MCP server allows an AI application to request.

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

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

**Model Context Protocol** — A standard way for AI applications to discover approved tools, prompts and context from a server.

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

**model version** — The specific release of a model used for a result.

**model weights** — The learned numerical values that make up a trained model.

**on-device** — Your current device runs the named operation.

**open-weight model** — A model whose trained parameter files are available under stated license terms.

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

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

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

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

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

**prompt template** — A reusable structure that turns task data into consistent model instructions.

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

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

**sensitive information disclosure** — Private or restricted information being exposed to someone or something that should not receive it.

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

**throughput** — How much work a system completes in a period of time.

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

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

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

## People Roles And Lifecycle

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

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

**customer** — A person or organization using a Lithi customer product.

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

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

**human reviewer** — A person who checks what the AI prepared before it goes ahead.

**IT Admin** — A person responsible for deploying, configuring and supporting Lithi devices for an organization.

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

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

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

**Security Admin** — A person responsible for security settings, evidence and access rules.

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

## Public Web Content Design And SEO

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

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

**alternative label** — An accepted synonym, abbreviation or spelling variant that points to the preferred term.

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

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

**breakpoint** — Lets a layout change when the screen reaches a defined width.

**browser zoom** — A browser control that enlarges or reduces page content.

**call to action** — A clear invitation to take a useful next step.

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

**clay canvas** — The quiet warm-neutral page background used across the Lithi public website.

**color contrast** — The visual difference between foreground content and its background.

**copy key** — A stable identifier used by software to retrieve approved wording.

**DefinedTerm** — A Schema.org object representing one glossary concept.

**DefinedTermSet** — A Schema.org object representing a glossary or controlled vocabulary.

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

**embedded tab** — A distinct content view shown inside a shared page rather than at a separate rendered page.

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

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

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

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

**JSON-LD** — A common format for adding linked structured data to a web page.

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

**llms.txt** — A proposed website file that gives AI systems a concise map of useful public content.

**locked copy** — Wording that must remain exactly the same until its owner approves a new version.

**Markdown-first page** — A public page authored in plain Markdown first so its readable source can project consistently to the page and related outputs.

**metadata** — Information about a page, such as its title, description, language and sharing image.

**minimum target size** — The minimum clickable or tappable area needed for a control to be comfortable and reliable to use.

**mobile-first** — Designing the smallest-screen reading order and controls first, then expanding the same meaning for larger screens.

**Open Graph metadata** — Page information used to create a social or messaging link preview.

**page deck** — The short introduction below a page title that answers what the reader can do or understand here.

**PDF** — A fixed-layout document format designed to preserve a document’s appearance across systems.

**plain language** — Writing that helps the intended reader find, understand and use the information the first time.

**PNG** — A lossless raster image format commonly used for screenshots and graphics.

**preferred label** — The one approved name used for a concept in a language and context.

**primary action** — The most useful next step on the current page.

**quiet eyebrow** — A small orientation label above a title that tells the reader where they are or what type of page this is.

**Read next** — A contextual link to the most useful next page after the current one.

**reading measure** — The width of a line of body text, kept comfortable for reading.

**redirect** — A rule that sends an old or alternate URL to the current destination.

**reduced motion** — A user preference to limit or remove non-essential animation.

**reflow** — Content adapting to a narrow or enlarged view without forcing two-dimensional scrolling for ordinary reading.

**render route** — The page entry that actually renders a public route or embedded view.

**responsive design** — A layout that adapts clearly to mobile, tablet, desktop, zoom and print without losing meaning.

**robots.txt** — A website file giving compliant crawlers instructions about which paths they may crawl.

**route** — The public URL path or logical destination for a page or action.

**scope note** — A short rule explaining where a term applies and how it differs from similar terms.

**screen reader** — Software that presents digital content through speech, braille or another non-visual output.

**search engine optimization** — Helping search systems and people understand, find and navigate content.

**secondary action** — A quieter alternative next step for someone not ready for the primary action.

**selective glass** — A restrained translucent surface used only where it improves hierarchy.

**semantic token** — A design token named for its purpose, such as text-primary or surface-soft.

**sitemap** — A machine-readable list of public URLs a site wants crawlers to discover.

**slug** — The readable part of a URL that identifies a page or item.

**source-attributed copy** — Wording linked to the source that supports it.

**structured data** — Machine-readable information describing what a page is about.

**SVG** — A scalable vector format for graphics that remain sharp at different sizes.

**terminal CTA** — The one final action that gives an action-bearing page its clear next step.

**text alternative** — Text that communicates the purpose or information of non-text content.

**URL** — The web address of a page, file or other resource.

## Receipts Evidence And Observability

**audit trail** — A history showing who or what changed something and when.

**evidence** — Information that supports or challenges a statement, decision or outcome.

**evidence pack** — A grouped set of records used to review one change, workflow or claim.

**Lithi Receipt** — Every accepted Agent Network task leaves a timestamped receipt showing what Lithi did and where relevant data stayed.

**Lithi Receipt ID** — The non-content identifier used to find one Lithi Receipt.

**log** — A timestamped technical record produced while software runs.

**LTH identifier prefix** — The shared `LTH` prefix used by several Lithi public identifier families.

**metric** — A measured number used to understand performance, quality or outcomes.

**observability** — The ability to understand what a system is doing from its recorded signals.

**proof** — Evidence that supports a specific statement about what happened.

**read-back** — Checking the stored result after a write or change rather than assuming it succeeded.

**receipt digest** — A cryptographic fingerprint used to bind receipt evidence to a result or state without publishing the private content itself.

**receipt type** — The category showing what kind of action a receipt records.

**replay** — Running a recorded event or request through a controlled test again.

**span** — One timed operation inside a trace.

**trace** — A linked view of technical operations that handled one request or workflow path.

**verified work** — A timestamped action tied to a customer outcome with enough evidence to count.

## Security Privacy Legal And Compliance

**accessibility** — Designing information and interactions so people with a wide range of disabilities can perceive, understand and use them.

**active consent** — Consent given through a clear affirmative action rather than silence or a preselected choice.

**AES-256** — The Advanced Encryption Standard using a 256-bit key.

**AES-256-GCM** — An authenticated encryption method using the Advanced Encryption Standard with a 256-bit key.

**App Sandbox** — An Apple security control that limits which resources a Mac app can access.

**attribute-based access control** — Granting or denying access using attributes such as organization, device, purpose, capability or resource state.

**CAA record** — A DNS record stating which certificate authorities may issue certificates for a domain.

**CIDR** — A notation for an IP network range, such as 10.0.0.0/24.

**code signing** — Cryptographic signing that lets a system verify who signed an app and whether its code changed.

**consent** — A person’s freely given, specific, informed and unambiguous agreement to a defined use.

**Customer Content** — Content a customer supplies, connects or generates through an approved Lithi product workflow.

**Customer Personal Data** — Personal data processed for a customer under the customer relationship and applicable agreement.

**data minimization** — Collecting and using only the data needed for the stated purpose.

**data protection law** — A law controls how organizations collect, use, share, secure and retain personal data.

**data region** — A named geographic area used for a specifically scoped data or service operation.

**data residency** — Names the countries or regions where an organization stores or processes a defined data class.

**data subject** — A person whose personal data an organization processes.

**Data Subject Access Request** — A request from a person to exercise applicable rights over their personal data, such as access.

**data subject request** — A person’s request to exercise an applicable privacy right over their personal data.

**default deny** — Blocks access until an approved rule explicitly allows it.

**encrypted in transit** — Encryption protecting data while it travels on a named protected network path.

**encryption at rest** — Encryption protecting stored data on disk or in a database.

**encryption in transit** — Encryption protecting data while it travels between systems.

**envelope encryption** — Encrypting data with one key and protecting that key with another managed key.

**fingerprinting** — Combining device or browser characteristics to recognize or single out a person or device.

**Gatekeeper** — A macOS security feature that checks downloaded software before it runs.

**HMAC** — A keyed cryptographic code used to verify that data came from someone holding the shared secret and was not changed.

**HSTS** — A browser security policy that tells supported browsers to use HTTPS for a site.

**international data transfer** — Makes personal data available in another country or legal jurisdiction.

**ISO certification** — Independent confirmation by a certification body that an organization meets a named ISO standard within a stated scope.

**ISO standard** — An International Standard published by ISO after expert agreement.

**key rotation** — Replacing a cryptographic key according to a defined schedule or security event.

**Keychain** — The Apple system for storing passwords, keys and other credentials securely on a device.

**least privilege** — Giving a person, service or agent only the access needed for the current job.

**MDM deployment** — Deploying and configuring Lithi through an organization’s mobile device management system.

**mobile device management** — Software used by an organization to configure and manage approved devices.

**multi-factor authentication** — Signing in with evidence from more than one factor, such as a password plus a security key or authenticator.

**Mutual Non-Disclosure Agreement** — A contract in which both parties agree to protect defined confidential information.

**non-essential cookie** — A cookie not strictly necessary to provide the service the person requested.

**notarization** — Apple’s automated service for checking and recording software distributed outside the Mac App Store.

**OAuth** — A standard way for an application to receive limited access to a service without receiving the person’s password.

**OpenPGP** — An open standard for encrypting or digitally signing messages and files using public-key or symmetric cryptography.

**personal data breach** — A security breach causing accidental or unlawful loss, change, destruction, disclosure of or access to personal data.

**processing of personal data** — Any operation performed on personal data, from collection and use to storage, sharing or deletion.

**purpose limitation** — Using personal data only for clear, specified and compatible purposes.

**redacted support bundle** — Removes or masks private content before someone shares diagnostic information with support.

**RFC** — A numbered publication in the Internet technical-document series maintained through the RFC Editor.

**role-based access control** — Granting permissions according to a person’s approved role.

**row-level security** — Database rules that decide which rows a request may read or change.

**secret** — Sensitive value used to authenticate or protect access, such as a private key, password or API credential.

**Secure Enclave** — A hardware-based security component on supported Apple devices that can protect certain cryptographic operations and keys.

**security key** — A physical authentication device used as a strong sign-in factor.

**security.txt** — A standard text file that tells security researchers how to report a vulnerability.

**sensitive data** — Information that could cause greater harm or requires stronger protection if misused or exposed.

**Service Level Agreement** — A contract that states measurable service commitments and the remedies or process when they are not met.

**SHA-256** — A cryptographic hash that turns data into a 256-bit fingerprint.

**signed for integrity** — A cryptographic signature showing that an approved message or result envelope has not been silently changed after signing.

**single sign-on** — Using one organization identity service to sign in to multiple approved applications.

**Standard Contractual Clauses** — European Commission-approved contract clauses used as one safeguard for certain international personal-data transfers.

**storage and access technology** — Technology that stores information on, or reads information from, a person’s device, including many cookies and similar identifiers.

**subprocessor** — Another organization a processor uses to help process personal data.

**TLS** — Transport Layer Security, the protocol used to protect many network connections such as HTTPS.

**UK International Data Transfer Addendum** — A UK transfer safeguard that can supplement certain contract clauses for restricted UK personal-data transfers.

**VPAT** — A standard template used to document how a product supports accessibility criteria.

**WCAG 2.2** — The current W3C Web Content Accessibility Guidelines version used as the public-web accessibility target.

**Web Content Accessibility Guidelines** — The W3C guidelines for making web content more accessible to people with disabilities.

**XPC** — Apple’s mechanism for communication between separate local processes or services.

**zero trust** — A security approach that does not grant trust merely because something is inside a network or previously connected.

## Support Quality Testing And Operations

**accessibility test** — A test checking whether people using different input methods or assistive technologies can use the experience.

**blocked** — Policy, permission, safety or an owner gate prevents the action.

**BLOCKED verification state** — The named verification or action could not proceed because of a stated dependency or gate.

**canceled** — The work was deliberately stopped before completion.

**completed** — The defined work finished successfully and passed its terminal checks.

**contract test** — A test that confirms data or interface behavior matches its declared contract.

**deferred** — The work is intentionally waiting for a required condition or safe capacity.

**deployment** — Putting an approved software version into an environment where it can run.

**deterministic safety validator** — A rule-based check that gives the same result for the same validated input and rule version.

**diagnostic** — A safe check used to understand why something is not working as expected.

**downloadable document pack** — A versioned set of approved guides sent or made available together for a specific stage, such as before orientation.

**empty** — The request succeeded, but there are currently no items in this defined scope.

**end-to-end test** — A test of a complete user or system journey from start to final outcome.

**error** — A problem prevented or degraded the requested result.

**fail closed** — When a required check cannot complete safely, the action stops instead of continuing by default.

**failed** — The work ended without the intended result.

**hostile-path test** — A test deliberately using invalid, malicious, repeated or out-of-order input to confirm the system fails safely.

**Ideal Customer Profile** — A defined description of the organizations most likely to benefit from a product or campaign.

**incident** — An event that harms or threatens service, security, privacy or customer outcomes and needs coordinated response.

**incident severity** — A measure of an incident’s current impact, scope and risk.

**integration test** — A test of two or more real components working together.

**Lithi Doctor** — The diagnostic system that checks whether Lithi is installed, healthy, secure and connected as expected.

**Lithi Support** — The official help function for product issues, account questions and approved support requests.

**Lithi Support Agent** — Walks you through diagnostics with your permission. It does not read your private email or team knowledge by default.

**Lithi Test Lab** — The testing system used to prove changes before release and detect regressions.

**loading** — The system is actively trying to retrieve or prepare the information.

**materialized view** — A stored result of a database query that can be refreshed for faster reads.

**not checked** — The system has not yet verified this value or capability.

**NOT_AUTHORISED verification state** — The current task or actor did not have authority to perform the named action.

**NOT_RUN verification state** — The named verification or action was not performed.

**P0 priority** — The highest-priority defect class in a defined Lithi work or bug-tracking rubric.

**P1 priority** — A high-priority defect class below P0 in a defined Lithi work or bug-tracking rubric.

**partial** — Some expected information is available, but the result is incomplete.

**paused** — The work is temporarily stopped and can resume under the defined rule.

**priority** — The order in which work should be addressed based on impact, urgency and dependency.

**production proof** — Evidence from the real released environment showing a defined capability or outcome works as claimed.

**publication** — Making approved content publicly available.

**queued** — Lithi accepted the work and is waiting to start it.

**rollup** — A summary created from more detailed records, such as counts or totals.

**running** — The work has started and has not reached a terminal state.

**safe review path** — The ordered checks and fallback decisions an eligible action must pass before it can continue.

**self-heal** — A safe, pre-approved fix the system may apply automatically for a known problem.

**semantic safety review** — A meaning-based review for risks that simple rules may not catch.

**stale** — The information may be out of date under the current freshness rule.

**success** — The stated action completed and its result was confirmed.

**support bundle** — A diagnostic package prepared to help investigate a product issue.

**support request** — A recorded request for help with a specific issue or question.

**test fixture** — A controlled sample input or system state used to run a repeatable test.

**unavailable** — Lithi cannot currently provide the information or action.

**unit test** — A test of one small piece of logic in isolation.

**Vault** — A general label for an approved secure secret store.

**verification** — Checking evidence against a defined requirement or expected result.

**visual regression test** — A test comparing rendered interfaces to detect unintended visual changes.

**warning** — Attention is needed, but the current task may still continue safely.