Concept Fables

Turning AI / Agent concepts into stories you can remember

This collection contains 684 concepts. Each entry first builds understanding through a fable, then reveals the definition and metaphorical mapping after the story ends.

Enter the concept library from a question

Do you want to understand a word, or do you want to make a judgment?

If you are comparing options, start with the problem navigator; if you have already encountered a specific term, use the concept library below to look up definitions, stories, applicable conditions and adjacent concepts.

Featured concepts

Read concepts and stories by topic

Browse by topic

Agent runtimeTool callingTool registryWeights & Biases WeaveSynthetic dataLow-Rank AdaptationQuantized low-rank adaptationInference engineDistillationBatch inferenceOnline inferenceModel routingSemantic cacheInference endpointModel gatewayModel Context ProtocolAI job replacement rateAutomated deflection rateAutonomous drivingCopilotWatermarkService as softwareAgent operating modelAgent OwnerAuthority boundariesAutonomy levelOperational metricsAgent loopExecutorPlannerActionComputer useGUI agentsWeb agentsTool selectionRunRun stepsReal-time agentVoice agentEpisodic memoryMemory compressionSemantic MemoryApproval flowState diagramAgent-to-Agent protocolLong-term memoryWorking memoryDraft areaLangGraphAlignmentConstitutional AIDirect Preference OptimizationPreference dataPreference optimizationProximal Policy OptimizationAI feedback reinforcement learningReinforcement learning from human feedbackReward modelLarge model applicationsHierarchical Navigable Small World GraphAttention maskALiBiBERTCausal attention / autoregressiveContext length/windowCross-attentionDecoder-onlyDiffusion language modelsEncoder-decoderFeedforward networkGPTGrouped Query AttentionJambaLayer normalizationLinear attentionMambaMoDMixture of ExpertsMulti-query attentionResidual connectionsRMSNormRotary position encodingSliding window attentionState space modelSwiGLUT5Vision TransformerWeight tyingAudit evidenceAudit trailAuditabilityInternal AuditSource citationtamper-evident logAgent workflowWorkflowIdempotencyTask queueMeasurementAnnual recurring revenueChurn rateNet revenue retentionCustomer health scoreGross profitUnit economics modelEnterprise salesIdeal Customer ProfileProduct-led growthSales-led growthCustomer acquisition costCustomer lifetime valueService Level AgreementToken costCustomer SuccessProfessional servicesManaged serviceHybrid pricingOutcome-based pricingSeat-based pricingUsage-based pricingSoftware as a ServiceProductized servicesDigital employeeSkillsCompliance mappingControl testingTechnical documentationControl FrameworkControlsISO 27001SOC 2 Type ISOC 2 Type IISOC 2AWQbitsandbytesDeep pruningDistilled reasoning modelGGMLGPTQGGUFModel PruningPost-training quantizationQuantization-aware trainingSparsityStructured pruningUnstructured PruningWidth pruningChain of thought and scratchpadC2PAHuman in the loopConversation threadHandoffToken budgetBudget-aware routingIntelligent customer serviceLlamaIndexDocument parsingOCRData connectorData flywheelBeam searchDecodeGreedy decodingLogitsSamplingTemperatureTop-k samplingTop-p samplingBackpropagationDeep learningNeural networksRepresentation learningCanary releaseCanary releasePrivate deploymentLocalized deploymentContainerKubernetesBlue-green deploymentCanary releaseInfrastructure as CodeGitOpsContinuous integration and continuous deliverySlot fillingNoise predictor/UNetPipeline parallelismTensor parallelismData parallelismFSDPZeROLayout analysisTable extractionDataset datasheetModel CardSystem cardChromaEmbedSemantic similarityVector databaseWord embeddingsPlatform EngineeringDeveloper experienceKnowledge base Q&ASemantic KernelCo-creationPilotEvaluation benchmarkBenchmark contaminationData leakageDistribution shiftPerplexityStep success rateTool call accuracyTrajectory evaluationLLM evaluation platformCost AttributionFine-tuningInstruction fine-tuningParameter-efficient fine-tuningSupervised Fine-TuningFull fine-tuningInstruction dataLayer-wise learning ratesrejection samplingArtificial IntelligenceModelDiffusion modelsDiffusion TransformerLatent Diffusion ModelScenario-based implementationAI impact assessmentAI use case checklistData lineageGovernance, Risk & CompliancePolicy engineProof of originShadow AITraceabilityTransparencyTrustworthy AIAgent policyAI disclosureControl everyoneHuman oversightBiasExplainabilityFairnessThree lines of defenseContent filteringPolicy as codeAI OperationsDelivery acceptanceAutoregressive decodingBest-of-N samplingContext pruningDynamic batchingEarly departureFlash AttentionInferenceCache offloadingQuantized KV cacheOperator fusionLatencyRetrospective decodingMedusaModel servingPaged attentionPrefillPrefix cachingQuantizationSpeculative decodingSpeculative editingSpeculative prefix treeSpeculative samplingTest-time computeThroughputTree searchContinuous batchingPrompt cachingRuntimeRetrieval-Augmented GenerationKnowledge graphOntologyTripleGraph-enhanced retrieval generationContext windowLanguage modelLarge Language ModelLiteLLMAgentMemoryPlanningHallucinationFew-shot promptingIn-context learningPromptPrompt engineeringSystem promptZero-shot promptingChain of ThoughtLangChainTruLensDecoding stagePrefillPaged attentionText generation inferenceCacheLangSmithHeliconeCost trackingLangChain Expression LanguageSignatureDSPyKV cacheTime to First TokenPrompt managementEvaluationGolden datasetModel file configurationOllamaFeature StoreModel version managementModel driftModel registryGeneralizationGradient descentHyperparametersLoss functionMachine learningOverfittingParametersReinforcement LearningSupervised LearningTest setTraining setUnsupervised LearningValidation setOpenAI Assistants APIAssistantOpenAI Responses APIFile searchCode InterpreterPineconeBenchmark caseAuxiliary lossExpert routingTop-k routingModel inventoryModel monitoringModel risk managementModel validationFunction callingJSON modeStructured outputStructured outputSupervisor agentGroup chat orchestrationAutoGenAgent teamUser Proxy AgentCrewAICLIPCross-Modal AlignmentMultimodal modelsVideo understandingContrastive learningCross-modal embeddingMultimodalVision-language modelEntity extractionRelation extractionHaystackTool call latencySpanTracking recordsOpenTelemetryArize PhoenixLangfuseMilvusQdrantWeaviateChange managementUpgrade pathException handlingHot reloadHuman-in-the-loop oversightPost-mortem reviewQuality assuranceRollbackRollback planRoot cause analysisCloud cost operationsAutoscalingLarge language model operationsMachine Learning OperationsDead letter queueDisaster recoveryObservabilityRecovery point objectiveRecovery time objectiveIncident responseSampling reviewVersion controlApproval thresholdChange Advisory BoardAI incidentsBusiness continuityConfidence thresholdFact-checkingIncident ManagementDirected acyclic graphIntent recognitionSemantic routingRouterAdapterIA3Merge weightsPrefix Fine-TuningPrompt fine-tuningTarget module selectionWorkflow engineQuotaConnectorDurable executionCloud nativeInternal developer platformGolden pathAI policyAcceptable Use PolicypgvectorBPESentencePieceCorpusFoundation modelPretrainingSelf-supervised learningAnonymizationData MinimizationData protection impact assessmentData retention policyDifferential privacyMembership inference attackModel inversion attackPersonal dataPersonally identifiable informationPseudonymizationPurpose limitationSecure aggregationSensitive personal dataCross-border data transferData localizationData residencySupplier evaluationVendor Lock-InData processing agreementData usage rightsSub-processorTraining data exclusionExit planThird-party risk managementSupplier due diligenceSecurity questionnaireProduct-market fitTime to valueSelf-serviceUser profileProof of conceptFeature flagOnboardingActivateMinimum viable productTasks to be completedAI-native workflowPrompt optimizerSemantic functionEvaluation frameworkDouble quantizationNF4Multimodal RAGRerankerAnswer RelevanceContext precisionContext recallFaithfulnessRetrieval precisionRetrieval recallGraph of ThoughtsSelf-consistencyTree of ThoughtsProgram-aided language modelReasoning-Action ParadigmEU AI ActGeneral-purpose AIHigh-risk AI systemsConformity assessmentRollbackCircuit breakerError budgetService Level ObjectiveDegradationModel fallbackFact AnchoringEmbedCross-encoderBM25Dual encoderHypothetical document embeddingsMaximum Marginal RelevanceMulti-hop retrievalQuery rewritingRecursive retrievalApproximate nearest neighbor searchDocument storageVector database ecosystemDense retrievalHybrid searchSemantic searchSparse retrievalChunkingParent-child chunkingSemantic chunkingSliding Window ChunkingRerankingQuery engineAI risk managementAI risk management frameworkHallucination riskResidual riskRisk acceptanceRisk appetiteRisk assessmentRisk ownerRisk RegisterMulti-tenantTenant isolationSafety guardrailsSales AgentAI safetyAttribute-based access controlBackdoor attackContext contaminationData exfiltrationData poisoningUnauthorized agencyModel poisoningOWASP LLM Top 10Permission boundariesRole-based access controlSupply chain riskTool output contaminationSandboxAudit logsPermission modelPrinciple of least privilegeSecrets managementInformation Security Management SystemSeparation of dutiesData loss preventionvLLMStreaming responsesTokens per secondChunked PrefillDraft modelState machineSpeech recognitionSpeech synthesisMulti-agent orchestrationOrchestrationContext EngineeringByte Pair EncodingTokenTokenizationTokenizerVocabularyBrowser toolsPluginActivation Checkpointbf16Catastrophic forgettingChain-of-thought trainingChinchilla approachContinued pretrainingCurriculum learningData mixingDenoising objectiveGRPOMasked language modelingMixed precision trainingMulti-task learningNext-word predictionPretrainingReinforcement fine-tuningVerifiable reward reinforcement learningScaling lawsFederated learningKnowledge distillationData augmentationAttention mechanismDecoderEncoderMulti-head attentionPositional encodingSelf-attentionTransformerCitationAI assistantFAISSAgent negotiationMulti-agent reflectionTask decompositionAgent debateAgent swarmMulti-agent consensusRole-playing multi-agentEmergent behaviorAgent decision tracingCompliance logUser feedback loopHallucination detectionLLM observabilityLatency monitoringProduction drift detectionPrompt version managementToken usage monitoringCall chain tracingBIG-bench (Beyond the Imitation Game Benchmark)HumanEval (code generation evaluation)MMLU (Massive Multitask Language Understanding)SWE-benchHELM (Holistic Evaluation of Language Models)Model safety evaluationRed team testingHarmful content filteringSafety fine-tuningEvaluation suiteTask success rateAdversarial examplesDenial-of-service attackIndirect prompt injectionJailbreakMultimodal jailbreakPrompt injectionJailbreakAgent orchestrationBlackboard architectureDecentralized multi-agentHierarchical multi-agentHybrid multi-agentMulti-agent systemAI GovernanceAccess controlAgent Identity and AuthenticationData privacy and PII maskingModel approval processModel risk assessmentRate limitingResponsible AIRight of regret and revocation mechanismsSecurity incident responseUsage policyLLM evaluationAdversarial evaluationAlignment EvaluationCapability assessmentHuman evaluationRound-by-round evaluationCapability contamination and data leakagePrompt sensitivityAgent routingAgent communication protocol

Domain classification

All concepts

684

Coding agent / developer tool

New

opencode

AI Coding Agent

opencode is an open-source AI coding agent for programming tasks, suited to understanding engineering in a codebase, editing files, running commands, debugging errors, generating tests, and refactoring code. It is a development tool for production business Agents, not a business Agent itself.

Read the fable →

Agent runtime / harness

New

OpenClaw

Agent Runtime / Harness

OpenClaw is a more general-purpose Agent runtime / harness that organizes channels, sessions, tools, skills, memory, tasks, automation and node capabilities into agent infrastructure that can run continuously.

Read the fable →

AI agent platform

Agent runtime

Agent Runtime

An agent runtime is the execution environment that lets an agent actually do work. It is not just a single large-model call; it manages task state, context, tool calls, permission boundaries, human approval, error recovery, log tracing, and multi-step execution.

Read the fable →

AI agent platform

Tool calling

Tool Calling, Function Calling

Tool calling, also called Function Calling, is a mechanism by which a model requests external functions, APIs, databases, file systems, or business systems in a structured way to complete tasks.

Read the fable →

AI agent platform

Tool registry

Tool Registry

A tool registry is the centralized catalog and control layer for the tools available to an Agent. It records tool names, purposes, parameter schemas, invocation methods, permission requirements, risk levels, approval rules, rate limits, return formats, and owners.

Read the fable →

AI application observability and evaluation tool

Weights & Biases Weave

Weights & Biases Weave

Weights & Biases Weave is a tracking, evaluation, and debugging tool for AI applications that records model calls, prompts, outputs, and iteration processes.

Read the fable →

AI engineering / data pipeline

Synthetic data

Synthetic Data

Synthetic data is generated by models, rules or simulation systems for training, fine-tuning, evaluation and test coverage; the key lies in quality filtering and distribution boundaries.

Read the fable →

AI engineering / fine-tuning

Low-Rank Adaptation

LoRA, Low-Rank Adaptation

LoRA (Low-Rank Adaptation) is a parameter-efficient fine-tuning method. It freezes most of the base model's weights and trains only small low-rank matrices to adapt to a specific task, significantly reducing training cost, VRAM requirements, and the complexity of multi-task adaptation.

Read the fable →

AI engineering / fine-tuning

Quantized low-rank adaptation

QLoRA, Quantized LoRA

QLoRA (Quantized LoRA) is a method for training LoRA adapters on a quantized base model. A common approach is to use 4-bit quantization to reduce memory usage while training a small number of adapter parameters.

Read the fable →

AI engineering / infrastructure

Inference engine

Inference Engine

The inference engine is responsible for efficiently executing the model's forward computation and managing GPU memory, KV cache, batching, concurrent scheduling, streaming output, and hardware acceleration.

Read the fable →

AI engineering / model optimization

Distillation

Distillation

Distillation is training a smaller model on the outputs, explanations, or preference signals of a large or strong model, so the smaller model reproduces part of the capability at lower cost. Enterprises commonly use distillation to reduce inference costs, improve latency, or transfer general model capabilities to specialized tasks; but the applicable scope, evaluation criteria, and fallback mechanisms must be clearly defined.

Read the fable →

AI engineering / operations

Batch inference

Batch Inference

Batch inference submits large volumes of input to a model for offline processing, suitable for labeling, report generation, document processing, recommendation recall, quality scanning, and non-real-time tasks. It typically optimizes throughput, unit cost, retries, and job management rather than the immediate latency of a single request.

Read the fable →

AI engineering / operations

Online inference

Online Inference

Online inference is calling the model in real time to generate results when a user request occurs, with typical constraints of low latency, high availability, concurrency capacity, streaming responses, and error handling. Online inference for enterprise Agents must also consider authentication, context assembly, tool calls, upgrade paths, SLAs, and observability.

Read the fable →

AI platform / cost optimization

Model routing

Model Routing

Model Routing is a mechanism that selects different models to call based on task type, quality requirements, cost, latency, context length, risk, permissions, or vendor status. It avoids using the most expensive or strongest model for every task, and also avoids critical tasks being handled by low-capability models.

Read the fable →

AI platform / cost optimization

Semantic cache

Semantic Cache

Semantic Cache is a mechanism that reuses existing answers, intermediate results, retrieval results, or tool results based on the semantic similarity of requests. It differs from ordinary caching that only hits on exactly identical strings; instead, it judges whether two requests are sufficiently close in meaning.

Read the fable →

AI platform / deployment

Inference endpoint

Inference Endpoint

An inference endpoint is the network entry point that model serving exposes for applications to call, usually including authentication, request format, routing, version management, rate limiting, load balancing, logging, and monitoring. It turns model capabilities into a service contract that applications can call reliably, and it is an important boundary for deployment and operational governance.

Read the fable →

AI platform / infrastructure

Model gateway

Model Gateway, AI Gateway

Model Gateway / AI Gateway unifies access to multiple model providers or self-hosted models and provides authentication, routing, rate limiting, logging, caching, fallback, cost control, and policy enforcement. It lets enterprises avoid hardcoding provider calls throughout applications in a multi-model environment, while centralizing governance of security, quality, cost, and availability.

Read the fable →

AI platform / integration

Model Context Protocol

Model Context Protocol, MCP

Model Context Protocol MCP (Model Context Protocol) is a protocol that lets AI applications connect to external tools, data sources, and context services in a standard way.

Read the fable →

AI product metrics / operations

AI job replacement rate

AI Task Automation Rate

AI work replacement rate measures what proportion of tasks originally done by humans are completed automatically by AI or with significantly reduced human involvement. It is closer to business value than call volume, session count or generated word count, because it directly connects to labor cost, delivery capacity and gross margin improvement.

Read the fable →

AI product metrics / support operations

Automated deflection rate

Deflection Rate

Automation deflection rate measures the proportion of requests that an AI or self-service system successfully handles and avoids escalating to a human, commonly seen in customer service, IT support, and operations tickets. It must be viewed together with resolution quality, error interception, and escalation accuracy; simply reducing human transfers can harm customer experience.

Read the fable →

AI product pattern

Autonomous driving

Autopilot

Autopilot is a product model that lets AI complete tasks autonomously under clear goals, permission boundaries, and monitoring mechanisms. Humans are mainly responsible for setting goals, supervising boundaries, handling exceptions, and accepting results.

Read the fable →

AI product pattern

Copilot

Copilot

Copilot is an AI product model that assists people in completing work. AI provides drafts, suggestions, retrieval, comparisons, checks, and next-step recommendations, while people retain the final right to judge, edit, approve, or submit. In enterprise scenarios, the value of Copilot lies in boosting the productivity and quality of professionals while keeping responsibility boundaries clear.

Read the fable →

AI safety

Watermark

Watermarking

Watermarking embeds detectable signals in AI-generated content to indicate or verify the content's source.

Read the fable →

AI-native business model

Service as software

Services-as-Software

Service-as-software is the productization of service processes that were once delivered by people, using AI and automation, so customers buy business outcomes rather than just access to tools. Its key difference from traditional SaaS is that the provider takes on more workflow execution and outcome responsibility, and pricing moves closer to tasks, tickets, delivery volume or outcomes.

Read the fable →

Agent Operating Model

Agent operating model

Agent Operating Model

An Agent operating model is the complete set of organizational operating methods an enterprise designs for Agents in production: who owns the Agent, how tasks are assigned, how they are supervised, how they are measured, how they escalate to humans, how they improve, and how incidents and compliance risks are handled. It turns individual Agent capabilities into a sustainable delivery system.

Read the fable →

Agent Operating Model

Agent Owner

Agent Owner

An Agent owner is the business or technical owner responsible for a certain Agent's goals, permissions, performance, risks, and lifecycle. In an enterprise, Agent responsibility cannot be left hanging between "the model," "the platform," "IT," or "the business team"; it must be clear who can change it, who watches the metrics, who handles incidents, and who decides on upgrades or decommissioning.

Read the fable →

Agent Operating Model

Authority boundaries

Authority Boundary

Authority boundaries are the explicit limits on the decisions, actions, spending, data access and external commitments an Agent is permitted to make. They further constrain "can call tools" into "under what conditions it can call them, how much scope it can affect, whether approval is required, and whether it can make external commitments."

Read the fable →

Agent Operating Model

Autonomy level

Autonomy Level

Autonomy level is the grading of how independently an Agent works: it can only recommend, draft first, execute after approval, execute autonomously within limits, or run fully automatically in specific scenarios. In enterprise governance, autonomy level determines the mode of human intervention, approval thresholds, audit requirements, and risk boundaries.

Read the fable →

Agent Operating Model

Operational metrics

Operating Metrics

Operational metrics are quantitative metrics used to manage Agents in production, such as completion rate, escalation rate, error rate, latency, cost, rework rate, first-pass acceptance rate, and incident rate.

Read the fable →

Agent architecture

Agent loop

Agent Loop

The agent loop is the basic closed loop of Agent operation: observe the state, reason and plan, choose an action, call tools to execute, then write the result back into context for the next round.

Read the fable →

Agent architecture

Executor

Executor

The executor is responsible for turning planned steps into actual actions, such as calling tools, running code, accessing external systems, and returning results for evaluation or re-planning.

Read the fable →

Agent architecture

Planner

Planner

The planner is responsible for breaking user goals into executable steps, subgoals, constraints, and dependencies, and adjusting the plan when new information appears.

Read the fable →

Agent capability

Action

Action

An action is a discrete operation that an Agent performs in an environment, usually completed through tools, functions, APIs, browsers, or GUI automation. It differs from an ordinary text answer: an action changes the state of an external system, such as sending an email, modifying a record, creating an order, submitting a form, or calling a payment interface.

Read the fable →

Agent capability

Computer use

Computer Use

Computer Use refers to a model's ability to directly operate a computer environment through the screen, mouse, keyboard, or UI automation. It enables Agents to handle tasks that have no API, incomplete interfaces, or can only be completed through desktop software.

Read the fable →

Agent capability

GUI agents

GUI Agent

A GUI Agent is an Agent that completes software tasks through visual recognition and interface operations. It understands controls, text, tables, pop-ups, and state changes on the screen, and advances tasks through actions such as clicking, typing, and selecting.

Read the fable →

Agent capability

Web agents

Web Agent

A Web Agent is an agent that searches, navigates, fills out forms, downloads materials, and performs operations in a web environment. It needs to understand page content, maintain task state, handle logins and dynamic pages, judge evidence quality, and request human approval before high-risk web actions.

Read the fable →

Agent decision-making

Tool selection

Tool Selection

Tool Selection is the process by which an Agent, based on the current subtask, chooses which available tool, function, or API to call and with what parameters. It is not just capability matching; it also involves intent recognition, permission boundaries, risk level, cost, rollbackability, and whether human approval is required.

Read the fable →

Agent execution object

Run

Run

A Run represents one complete execution by an Assistant or Agent for a thread/request. It includes model inference, message generation, tool calls, waiting for human actions, error handling, and final output.

Read the fable →

Agent execution trace

Run steps

Run Step

A Run Step is an intermediate execution record within a Run, such as a model message generation, a tool call, a wait for human action, or a failed retry. It lets teams inspect the Agent's execution process rather than only looking at the final answer.

Read the fable →

Agent interface

Real-time agent

Real-Time Agent

A Real-Time Agent is an Agent that understands input, plans actions, calls tools and keeps responding within low-latency, streaming interactions. It is commonly used in voice, customer service, dispatch, monitoring and collaboration scenarios, and its key requirements are low latency, incremental understanding, continuously updated state, timely interruption and safe escalation.

Read the fable →

Agent interface

Voice agent

Voice Agent

A Voice Agent is an Agent that interacts with users in real time through voice input and output to complete tasks. It combines speech recognition, real-time understanding, dialogue management, tool calling, speech synthesis, and human escalation.

Read the fable →

Agent memory

Episodic memory

Episodic Memory

Episodic memory records specific events, interactions, observations, and outcomes, usually including metadata such as time, source, participants, actions, and consequences.

Read the fable →

Agent memory

Memory compression

Memory Compression

Memory Compression compresses long conversations, historical observations, retrieved materials, or execution traces into shorter summaries, structured facts, or retrievable memories, so they can fit into the subsequent context budget while preserving as much task-useful signal as possible.

Read the fable →

Agent memory

Semantic Memory

Semantic Memory

Semantic Memory is facts, concepts, user preferences, business rules, and domain knowledge abstracted from specific events. It differs from Episodic Memory: the latter preserves experiences that happened one by one, while the former stores reusable stable knowledge.

Read the fable →

Agent operations / governance

Approval flow

Approval Flow, Human Approval

An approval flow is a control mechanism that adds human confirmation before high-risk actions, commonly used for payments, external writes, permission changes, and deletion operations.

Read the fable →

Agent orchestration pattern

State diagram

State Graph

A state graph models an Agent workflow as a set of nodes and edges: nodes read and update shared state, and edges decide the next execution step based on state. It is suitable for expressing Agent flows that branch, loop, wait, retry, and recover.

Read the fable →

Agent protocol

Agent-to-Agent protocol

Agent2Agent, A2A

Agent2Agent, A2A refers to the protocol direction for interoperability and communication between different Agents, enabling one Agent to discover another Agent's capabilities, initiate tasks, pass context, receive status, and handle results. It focuses on collaboration boundaries across systems, vendors, and organizations.

Read the fable →

Agent state

Long-term memory

Long-Term Memory

Long-Term Memory is information stored outside the current context window that can be retrieved across sessions and tasks. It lets enterprise Agents remember customer preferences, historical commitments, domain facts, unfinished tasks, and long-term state.

Read the fable →

Agent state

Working memory

Working Memory

Working Memory is the state an Agent temporarily holds and operates on during the current task, including goals, constraints, recent observations, tool results, intermediate artifacts, hypotheses, and next-step plans. It usually lives in the context window, scratchpad, state object, or workflow state.

Read the fable →

Agent state / reasoning workspace

Draft area

Scratchpad

A scratchpad is a temporary workspace an Agent uses within the current task to record intermediate observations, calculations, plans, tool results and execution notes. It helps the Agent maintain task state, but it usually should not enter long-term memory or user output without filtering.

Read the fable →

Agent workflow framework

LangGraph

LangGraph

LangGraph is a graph-based framework for building stateful, multi-step, controllable Agent workflows.

Read the fable →

Alignment

Alignment

Alignment

Alignment makes an AI model's or Agent's behavior conform to human intent, organizational policy, safety boundaries and real task objectives.

Read the fable →

Alignment

Constitutional AI

Constitutional AI

Constitutional AI uses a set of explicit principles to guide the model in generating, critiquing, and revising outputs, reducing reliance on item-by-item human preference labeling.

Read the fable →

Alignment

Direct Preference Optimization

Direct Preference Optimization, DPO

DPO is a method for directly optimizing a language model based on preference data, using comparisons of good and bad responses to the same input to adjust model behavior.

Read the fable →

Alignment

Preference data

Preference Data

Preference Data is data used to train reward models, DPO, RLHF, RLAIF or other preference optimization methods, usually containing multiple responses to the same input along with their rankings, choices or scores. It expresses "which behavior is more acceptable," not just the standard answer.

Read the fable →

Alignment

Preference optimization

Preference Optimization

Preference optimization uses human or model preference signals to improve model behavior. Common methods include RLHF, RLAIF, DPO, IPO and KTO.

Read the fable →

Alignment

Proximal Policy Optimization

Proximal Policy Optimization, PPO

Proximal Policy Optimization, PPO is a reinforcement learning algorithm commonly used in RLHF to optimize a language model's policy based on a reward model. It limits how much the new policy can update relative to the old policy, preventing the model from drifting too far in behavior while chasing rewards.

Read the fable →

Alignment

AI feedback reinforcement learning

Reinforcement Learning from AI Feedback, RLAIF

Reinforcement Learning from AI Feedback, RLAIF is a method of training and aligning models using feedback or preference signals generated by AI systems. It can reduce manual annotation costs, expand feedback coverage, and is used for constitutional AI, automated preference review and safety evaluation.

Read the fable →

Alignment

Reinforcement learning from human feedback

Reinforcement Learning from Human Feedback, RLHF

RLHF trains models using human preferences, typically including collecting preferences, training a reward model, and using reinforcement learning to optimize model outputs.

Read the fable →

Alignment

Reward model

Reward Model

A Reward Model is a model trained on human or AI preference data to score or rank candidate outputs and predict which responses better match the target preferences. In RLHF, the reward model usually guides subsequent reinforcement learning optimization.

Read the fable →

Application layer / Product

Large model applications

LLM Application, Large Model Application

LLM Application / Large Model Application embeds large model capabilities into specific business processes, connecting data, tools, permissions, user interfaces, evaluation, and operational mechanisms to form deliverable software or services.

Read the fable →

Approximate nearest neighbor index

Hierarchical Navigable Small World Graph

Hierarchical Navigable Small World, HNSW

HNSW is a graph-based approximate nearest neighbor index that accelerates vector retrieval through a hierarchical small-world network, and it is commonly used in vector databases.

Read the fable →

Architecture

Attention mask

Attention Mask

Attention Mask is used to control which tokens can be attended to by other tokens in the attention mechanism. Common uses include causal masking, preventing the model from seeing future tokens, ignoring padding tokens, and isolating information in different regions in certain architectures.

Read the fable →

Architecture

ALiBi

Attention with Linear Biases

ALiBi (Attention with Linear Biases) adds a distance-related linear bias to attention scores, usually making the model favor nearby tokens while preserving the possibility of attending to distant tokens.

Read the fable →

Architecture

BERT

Bidirectional Encoder Representations from Transformers

BERT is an encoder-only Transformer model, pretrained through masked language modeling, and is suitable for classification, matching and understanding tasks.

Read the fable →

Architecture

Causal attention / autoregressive

Causal Attention / Autoregressive

Causal Attention / Autoregressive means that when generating the current position, it can only attend to tokens before the current position and cannot see future tokens. It is the foundation of autoregressive language models, enabling the model to predict the next token in sequence and generate text.

Read the fable →

Architecture

Context length/window

Context Window / Context Length

Context Window / Context Length refers to the maximum number of tokens a model can process in one forward computation, and is an important capability metric of model architecture and deployment configuration. It differs from context strategy at the application layer: the fact that a model supports long context does not mean every request should fill it up.

Read the fable →

Architecture

Cross-attention

Cross-Attention

Cross-attention lets one sequence dynamically attend to relevant information in another sequence while generating or updating representations.

Read the fable →

Architecture

Decoder-only

Decoder-Only

Decoder-Only is an architecture that uses only a stack of Transformer decoders, and most modern GPT-style large language models adopt this approach. It places the input prompt, context, examples, and already-generated content into the same sequence, predicting the next token autoregressively.

Read the fable →

Architecture

Diffusion language models

Diffusion Language Model

Diffusion Language Model is a model approach that applies the ideas of diffusion models to language generation, usually generating or editing text by gradually denoising from noisy or corrupted text states, rather than strictly predicting the next token from left to right like traditional autoregressive models.

Read the fable →

Architecture

Encoder-decoder

Encoder-Decoder

Encoder-Decoder is a Transformer architecture composed of an encoder and a decoder. The Encoder first encodes the input into a contextualized representation, and the Decoder looks at these representations through Cross-Attention when generating output.

Read the fable →

Architecture

Feedforward network

Feed-Forward Network, FFN

The feed-forward network is the position-wise nonlinear module in a Transformer layer that follows attention, responsible for expanding and transforming each token representation.

Read the fable →

Architecture

GPT

Generative Pre-trained Transformer

GPT is a decoder-based autoregressive Transformer model, trained by predicting the next token, and is suited to generation, reasoning, and dialogue tasks.

Read the fable →

Architecture

Grouped Query Attention

Grouped Query Attention, GQA

Grouped-query attention lets multiple query heads share key-value heads, striking a compromise between multi-head attention quality and multi-query attention efficiency.

Read the fable →

Architecture

Jamba

Jamba

Jamba is a hybrid architecture route combining Transformer attention with Mamba/SSM ideas, used to improve long-context processing efficiency.

Read the fable →

Architecture

Layer normalization

Layer Normalization

Layer Normalization is a technique for normalizing activation values inside a neural network layer, making the feature distribution of each sample more stable. In Transformers, LayerNorm is often used before and after attention and the FFN to improve training stability and gradient propagation.

Read the fable →

Architecture

Linear attention

Linear Attention

Linear Attention is a class of methods that reduce the computational complexity of attention from the quadratic growth of traditional self-attention to approximately linear growth.

Read the fable →

Architecture

Mamba

Mamba

Mamba is a sequence modeling architecture based on selective state space models. Its core feature is giving state updates an input-dependent selection mechanism, thereby balancing efficiency and content-sensitive information retention on long sequences.

Read the fable →

Architecture

MoD

Mixture of Depths

MoD dynamically decides whether different tokens pass through all model layers, letting simple tokens skip part of the computation to reduce inference cost.

Read the fable →

Architecture

Mixture of Experts

Mixture of Experts, MoE

Mixture-of-experts models route different tokens to different expert subnetworks, expanding total parameter count while controlling the cost of a single inference.

Read the fable →

Architecture

Multi-query attention

Multi-Query Attention, MQA

Multi-query attention lets all query heads share the same set of key-value heads, significantly reducing KV cache usage and often used to improve long-context inference efficiency.

Read the fable →

Architecture

Residual connections

Residual Connection

A residual connection adds a layer's input directly to its output, letting the network learn incremental changes instead of completely rewriting the representation at every layer. It improves gradient propagation and training stability in deep networks, and is a key reason Transformers can stack many layers.

Read the fable →

Architecture

RMSNorm

Root Mean Square Layer Normalization

RMSNorm is a variant of LayerNorm that normalizes using the root mean square of activations, usually without subtracting the mean, which can reduce computational overhead and stabilize training.

Read the fable →

Architecture

Rotary position encoding

Rotary Position Embedding, RoPE

RoPE (Rotary Position Embedding) encodes positional information by applying position-dependent rotations to query/key vectors, so that attention scores incorporate relative position information. It is widely used in modern LLMs, helps handle order and relative distance, and is closely tied to long-context extension techniques.

Read the fable →

Architecture

Sliding window attention

Sliding Window Attention

Sliding Window Attention limits each token to attending only to tokens within a fixed nearby window, thereby reducing the cost of long-sequence attention from global quadratic growth. It suits scenarios with strong local dependencies such as long texts, speech and logs, and is often combined with global attention or sparse attention.

Read the fable →

Architecture

State space model

State Space Model, SSM

State space models use a state updated along the sequence to model long-range dependencies, an important sequence modeling path beyond Transformer attention.

Read the fable →

Architecture

SwiGLU

Swish-Gated Linear Unit

SwiGLU is a gated activation structure used in Transformer feed-forward networks, improving nonlinear expressiveness and model performance through a gating branch.

Read the fable →

Architecture

T5

Text-to-Text Transfer Transformer

T5 unifies NLP tasks such as translation, summarization, and question answering into a text-to-text format, using the same model paradigm to handle multiple language tasks.

Read the fable →

Architecture

Vision Transformer

Vision Transformer, ViT

Vision Transformer (ViT) cuts images into patches and uses a Transformer to model the relationships between image blocks as if processing a token sequence. It brings self-attention into vision tasks and is suitable as a foundation for visual understanding such as classification, retrieval, and detection.

Read the fable →

Architecture

Weight tying

Weight Tying

Weight Tying is a technique in language models that shares the weights of the input embedding layer and the final output projection (LM head). It can reduce the number of parameters and let input word representations and output word predictions share the same symbol space, usually without significantly hurting quality.

Read the fable →

Auditability

Audit evidence

Audit Evidence

Audit evidence is verifiable material supporting audit conclusions, such as approval records, logs, test results, tickets, and third-party attestations.

Read the fable →

Auditability

Audit trail

Audit Trail

An Audit Trail is a traceable chain recording the entire process of an object, request, data item, or operation from start to finish. It typically includes timestamps, operators, inputs, outputs, system state, approvals, reasons for changes, and results.

Read the fable →

Auditability

Auditability

Auditability

Auditability refers to the ability of a system, process or organization to be audited, reviewed and explained. It is not a single logging feature, but an attribute formed jointly by records, permissions, evidence, controls, responsibilities, documentation and reproducible processes.

Read the fable →

Auditability

Internal Audit

Internal Audit

Internal Audit is the function within an organization that independently assesses whether risk management, controls and governance are effective. It typically does not directly own business controls, but checks whether control design is reasonable, execution is consistent, evidence is sufficient, and deficiencies are remediated.

Read the fable →

Auditability/Documentation

Source citation

Citation

Citation is the reference to source material in AI output, decisions, or generative statements. In enterprise RAG, knowledge base Q&A, compliance analysis, and report generation, citations are used to connect answers to documents, paragraphs, records, or evidence, supporting verification, auditing, and correction.

Read the fable →

Auditability/Security

tamper-evident log

Tamper-Evident Log

A Tamper-Evident Log is a logging mechanism that makes modifications, deletions, insertions or reordering leave detectable traces. It does not mean it is absolutely immune to attack, but it makes tampering hard to go unnoticed, often achieved through append-only writes, hash chains, signatures, timestamps, WORM storage or external anchoring.

Read the fable →

Automation architecture

Agent workflow

Agentic Workflow

Agentic workflows combine repeatable processes with the Agent's limited autonomy, advancing tasks within goals, state, tools, permissions, approvals, and recovery rules.

Read the fable →

Automation architecture

Workflow

Workflow

A workflow is a predefined or semi-structured process made up of steps, decisions, roles, and system integrations, used to reliably produce a business outcome. In AI / Agent systems, workflows coordinate model calls, tools, human approvals, state, and external systems.

Read the fable →

Backend engineering / operations

Idempotency

Idempotency

Idempotency means that the same operation produces the same expected result whether executed once or multiple times, and it is commonly used in retries, payments, task scheduling, and external writes.

Read the fable →

Backend engineering / operations

Task queue

Job Queue, Task Queue

A task queue stores units of work waiting for asynchronous execution, decoupling front-end requests from time-consuming, failure-prone background actions. Users do not have to wait in place the whole time, and workers can process gradually according to the rules.

Read the fable →

Billing / platform

Measurement

Metering

Metering is the ability to record, aggregate, and use actual customer usage for billing, quotas, cost attribution, and business analysis. In enterprise AI / Agent services, the metered objects may be tokens, tasks, tickets, automated completions, manual escalations, data processing volume, or delivery results.

Read the fable →

Business / SaaS metrics

Annual recurring revenue

Annual Recurring Revenue, ARR

ARR is a revenue metric that standardizes subscription or recurring contract revenue to an annual basis, used to measure the scale of a SaaS or ongoing service business.

Read the fable →

Business / SaaS metrics

Churn rate

Churn Rate

Churn rate measures the proportion of customers, accounts, or revenue that stops renewing, reduces usage, or leaves within a certain period.

Read the fable →

Business / SaaS metrics

Net revenue retention

Net Revenue Retention, NRR

Net Revenue Retention, NRR measures how revenue from the same group of existing customers changes after renewals, expansion, downgrades and churn. The formula is usually starting customer revenue plus expansion revenue, minus contraction and churn revenue, divided by starting revenue.

Read the fable →

Business / customer success

Customer health score

Customer Health Score

Customer Health Score uses multiple signals to assess whether a customer will renew, expand or churn.

Read the fable →

Business / finance

Gross profit

Gross Margin

Gross Margin is the remaining percentage of revenue after deducting direct delivery costs. For AI / Agent services, direct costs may include model calls, cloud resources, tool/API calls, human review, customer support, implementation, and SLA response.

Read the fable →

Business / finance

Unit economics model

Unit Economics

Unit Economics analyzes the revenue, direct costs, and profit of each customer, task, request, ticket, or transaction to determine whether a business can scale profitably.

Read the fable →

Business / go-to-market

Enterprise sales

Enterprise Sales

Enterprise Sales targets organizational and large-account purchasing, usually involving multi-stakeholder decisions, budget ownership, security and compliance review, POC, procurement processes, legal contracts, and longer sales cycles.

Read the fable →

Business / go-to-market

Ideal Customer Profile

Ideal Customer Profile, ICP

An ideal customer profile describes the types of customers best suited to buy and successfully use the product, including industry, size, pain points, budget and purchasing capability.

Read the fable →

Business / go-to-market

Product-led growth

Product-Led Growth, PLG

Product-led growth uses the product itself to drive acquisition, activation, conversion and expansion, with common tactics including trials, self-serve onboarding and in-product guidance.

Read the fable →

Business / go-to-market

Sales-led growth

Sales-Led Growth

Sales-Led Growth relies on a sales team to identify target customers, discover needs, coordinate multiple stakeholders, advance procurement, and close high-ticket deals. It suits complex enterprise products, heavily customized delivery, high compliance risk, or AI / Agent services that require budget restructuring.

Read the fable →

Business / growth

Customer acquisition cost

Customer Acquisition Cost, CAC

Customer acquisition cost is the cost of sales, marketing, and related inputs required to acquire one new customer.

Read the fable →

Business / growth

Customer lifetime value

Customer Lifetime Value, LTV

Customer Lifetime Value, LTV is the revenue or gross margin value a customer is expected to contribute over the entire cooperation cycle. For Andy Ren Xu, LTV depends on contract amount, renewal years, expansion revenue, gross margin, support cost and churn probability.

Read the fable →

Business / operations

Service Level Agreement

Service Level Agreement, SLA

An SLA is a formal commitment between a service provider and a customer regarding availability, response time, support scope, repair time, breach compensation, and communication mechanisms. For enterprise AI / Agent services to replace manual processes or outsourced teams, availability, quality, escalation, incident handling, and outcome acceptance must be written clearly.

Read the fable →

Business / operations

Token cost

Token Cost

Token Cost is the model usage cost of an LLM application, calculated from input, output and intermediate reasoning tokens. For Agent services like Andy Ren Xu's, it isn't just a technical bill—it's a foundational variable for gross margin, plans, usage limits and automation strategy.

Read the fable →

Business / post-sales

Customer Success

Customer Success

Customer Success helps customers continuously achieve promised outcomes through onboarding, training, value tracking, risk alerts, renewal management and expansion recommendations. Adoption risk for enterprise AI / Agent services is high: customer processes must change, employees must trust the system, results must be accepted, and costs must be controllable.

Read the fable →

Business model / delivery

Professional services

Professional Services

Professional services are labor-intensive delivery around consulting, implementation, customization, training and integration. For enterprise AI / Agent companies, they are often used for early pre-sales validation, complex integration, process mapping and go-live support, and can drive deals and customer success.

Read the fable →

Business model / operations

Managed service

Managed Service

A managed service is a vendor continuously operating a system, process or business capability on behalf of a client, typically including software, monitoring, support, staffing fallback, SLAs and outcome responsibility. It is more continuous than one-off professional services and takes on more operational responsibility than pure SaaS.

Read the fable →

Business model / pricing

Hybrid pricing

Hybrid Pricing

Hybrid pricing combines subscription fees, seat fees, usage fees, service fees, overage fees or outcome-based revenue sharing to match different cost structures and customer perceptions of value.

Read the fable →

Business model / pricing

Outcome-based pricing

Outcome-Based Pricing

Outcome-based pricing charges for the business outcomes the customer achieves, cost savings, new revenue, or completed delivery, rather than per seat, per hour, or per API call. For enterprise AI / Agent services, it suits scenarios where outcomes are clear, verifiable, attributable, and the vendor can control the critical processes.

Read the fable →

Business model / pricing

Seat-based pricing

Seat-Based Pricing, Per-Seat Pricing

Seat-based pricing charges by the number of users, accounts, or personnel, and is the most common and easily understood procurement model in SaaS. It suits products where value mainly comes from people using the software, and where user count is roughly correlated with value and cost.

Read the fable →

Business model / pricing

Usage-based pricing

Usage-Based Pricing

Usage-based pricing charges customers according to actual usage, and common billing units include number of requests, tokens, tasks, amount of data processed, storage, autocomplete counts, or ticket volume. The marginal cost of AI / Agent products usually varies with model calls, tool calls, and human escalation, so usage-based pricing can bring revenue closer to cost and value.

Read the fable →

Business model / product

Software as a Service

SaaS, Software as a Service

SaaS (Software as a Service) continuously delivers software capabilities online, usually charged by subscription, seat, or usage, with the vendor responsible for operation, maintenance, upgrades, and availability.

Read the fable →

Business model / product strategy

Productized services

Productized Service

Productized services compress services that were originally customized and dependent on experts' on-the-spot judgment into delivery solutions with clear scope, fixed processes, explicit pricing and stable acceptance criteria. In enterprise AI / Agent scenarios, much early revenue comes from manual implementation, consulting and customized processes; without productization, it is hard to scale and hard to improve gross margin.

Read the fable →

Business positioning / Automation

Digital employee

Digital Employee, Digital Worker, AI Worker

A digital employee, Digital Worker or AI Worker packages AI capabilities as a virtual workforce that can take on job tasks or process outcomes. Its market expression is closer to "replacing or augmenting a certain type of work" rather than "providing a software feature."

Read the fable →

Capability packaging

Skills

Skill

A skill is a task capability module packaged for an Agent, usually containing task-specific instructions, tools, examples, workflows, boundaries, and acceptance methods. It lets the Agent complete a certain type of work more reliably, rather than improvising each time with generic prompts.

Read the fable →

Compliance

Compliance mapping

Compliance Mapping

Compliance Mapping is the process of mapping regulations, standards, customer requirements, or audit criteria to a company's internal controls, processes, evidence, and responsible parties. It avoids duplicate efforts and can also reveal control gaps.

Read the fable →

Compliance/Audit

Control testing

Control Testing

Control Testing is the activity of verifying whether controls operate as designed and effectively reduce risk. It can be done through sample checks, reperformance, observation, inquiry, configuration review, log analysis or simulation drills.

Read the fable →

Compliance/Documentation

Technical documentation

Technical Documentation

Technical documentation describes system architecture, components, interfaces, data flows, permissions, deployment, operations, troubleshooting and change history.

Read the fable →

Compliance/Governance

Control Framework

Control Framework

A Control Framework is a structured framework organizations use to design, organize, execute, and evaluate control measures. It typically defines control objectives, control domains, ownership, execution requirements, evidence types, testing frequency, and defect handling methods.

Read the fable →

Compliance/Security

Controls

Controls

Controls are specific measures designed to reduce risk, meet policy, or achieve control objectives. They can be preventive, detective, or corrective, such as access approval, least privilege, log monitoring, manual review, configuration baselines, change approval, backup, alerting, and incident response.

Read the fable →

Compliance/Security

ISO 27001

ISO/IEC 27001

ISO 27001 is the international standard for information security management systems, requiring organizations to continuously improve information security controls through risk management.

Read the fable →

Compliance/Security

SOC 2 Type I

SOC 2 Type I

SOC 2 Type I is an independent auditor's assessment, at a single point in time, of whether a service organization's system description and control design are suitable for meeting the relevant Trust Services Criteria, such as security, availability, confidentiality, processing integrity, and privacy.

Read the fable →

Compliance/Security

SOC 2 Type II

SOC 2 Type II

SOC 2 Type II is a report in which an independent auditor evaluates the design and operating effectiveness of a service organization's controls over a period. It demonstrates more than Type I whether the organization continuously executes controls, often covering 3 to 12 months of evidence.

Read the fable →

Compliance/Security

SOC 2

Service Organization Control 2, SOC 2

SOC 2 is an audit reporting framework for service organizations, used to assess whether controls for security, availability, confidentiality, privacy and other areas are effective.

Read the fable →

Compression

AWQ

Activation-Aware Weight Quantization

AWQ is a weight quantization method that protects key channels based on activation magnitude while compressing unimportant weights more aggressively.

Read the fable →

Compression

bitsandbytes

BitsAndBytes

bitsandbytes is a low-precision loading and quantization library commonly used in the Hugging Face ecosystem, especially for 8-bit and 4-bit weight loading. It lets larger models be loaded, fine-tuned or deployed within more limited VRAM.

Read the fable →

Compression

Deep pruning

Depth Pruning

Depth Pruning is one of the model compression methods, producing a shallower model by removing entire Transformer layers. It focuses on which layers contribute less to the output and tries to preserve quality through evaluation, calibration, or retraining.

Read the fable →

Compression

Distilled reasoning model

Distilled Reasoning Models

Distilled Reasoning Models are an approach that uses answers, steps, or reasoning traces produced by large reasoning models to train smaller models, giving the smaller models part of the reasoning capability. It is often combined with SFT, knowledge distillation, and model compression to reduce inference cost, latency, and deployment barriers.

Read the fable →

Compression

GGML

GGML Tensor Library

GGML is the C language tensor library that llama.cpp depended on in its early days. It supports LLM inference and quantization on CPU and is the predecessor of the GGUF ecosystem.

Read the fable →

Compression

GPTQ

GPT Post-Training Quantization

GPTQ is a one-shot post-training weight quantization method that uses approximate second-order information to reduce the error caused by 3/4-bit quantization.

Read the fable →

Compression

GGUF

GPT-Generated Unified Format

GGUF is a quantized large-model file format commonly used in local inference ecosystems such as llama.cpp, packaging model weights and metadata in a unified way. It lets runtimes load different quantized versions reliably, instead of every model relying on ad-hoc conventions.

Read the fable →

Compression

Model Pruning

Model Pruning

Model pruning is the removal of unimportant weights, neurons, attention heads, or layers from a trained model to reduce model size, memory usage, and inference latency.

Read the fable →

Compression

Post-training quantization

Post-Training Quantization, PTQ

Post-training quantization is a compression method that reduces weight or activation precision after model training is complete. It is fast but may lose some effectiveness.

Read the fable →

Compression

Quantization-aware training

Quantization-Aware Training, QAT

Quantization-Aware Training (QAT) simulates the effects of low-precision quantization during training or fine-tuning, letting the model adapt in advance to the compressed computation method. It is not compressing after training; rather, it lets the model feel the low-precision constraints during the training process.

Read the fable →

Compression

Sparsity

Sparsity

Sparsity means that many weights in a model are zero, or that many activations are inactive during computation. Methods such as pruning can create sparse structures, thereby reducing theoretical compute and memory requirements.

Read the fable →

Compression

Structured pruning

Structured Pruning

Structured pruning removes entire groups of neurons, attention heads, channels, layers or other regular structures. The pruned model has a tidier structure, making it easier for standard hardware and runtimes to actually run faster.

Read the fable →

Compression

Unstructured Pruning

Unstructured Pruning

Unstructured pruning sets individual weights to zero by importance, preserving most of the model's original structure. It can produce highly sparse models and reduce storage or memory pressure.

Read the fable →

Compression

Width pruning

Width Pruning

Width pruning reduces the hidden dimensions, attention heads, or feed-forward intermediate dimensions, making the model narrower and thereby lowering parameter count and inference cost.

Read the fable →

Concept distinction

Chain of thought and scratchpad

Chain-of-Thought vs Scratchpad

Chain-of-Thought is the intermediate reasoning process or reasoning trace; Scratchpad is a broader temporary workspace that can contain reasoning, observations, tool outputs, plans, variables, intermediate data, and execution notes.

Read the fable →

Content provenance

C2PA

Coalition for Content Provenance and Authenticity

C2PA is a standard for digital content provenance and authenticity, using cryptographic credentials to record the generation and editing history of images, videos, audio, and other content.

Read the fable →

Control pattern

Human in the loop

Human-in-the-Loop

Human-in-the-loop embeds human review, judgment, correction, approval, or takeover at key nodes of an AI or Agent process.

Read the fable →

Conversation state object

Conversation thread

Thread

A Thread is an object in the managed Agent API that stores conversation state. It places users, assistants, and messages into the same persistent context, allowing subsequent runs to continue execution based on the existing conversation.

Read the fable →

Coordination pattern

Handoff

Handoff

Handoff is the process by which task ownership, context, and next actions are transferred from one Agent, workflow, system, or person to another executor. In enterprise Agents, handoffs often occur in multi-agent collaboration, human escalation, customer service transfer to specialists, and automated processes transferring to human approval.

Read the fable →

Cost / context

Token budget

Token Budget

A token budget is the upper limit of tokens allocated to a task, request, user, or workflow. It controls prompt length, retrieved context, tool output, model reasoning space, and answer length.

Read the fable →

Cost optimization

Budget-aware routing

Budget-Aware Routing

Budget-aware routing makes choices among budget, task value, quality requirements, and latency: not every request needs to go to the most expensive model, nor should you cut costs blindly. The system selects models, tools, retrieval depth, or execution paths based on the scenario.

Read the fable →

Customer support / Contact center AI

Intelligent customer service

AI Customer Service, Intelligent Customer Service

Intelligent customer service uses natural language understanding, knowledge base retrieval, dialogue management and ticket system integration to automatically handle common inquiries and hand off complex issues.

Read the fable →

Data framework for LLM applications

LlamaIndex

LlamaIndex

LlamaIndex is a data and retrieval framework for LLM applications, used to connect private, structured, semi-structured and unstructured data sources, and provides abstractions such as loaders, nodes, indexes, retrievers and query engines.

Read the fable →

Data ingestion

Document parsing

Document Parsing

Document Parsing is the process of converting documents such as PDFs, Word files, web pages, tables and scans into indexable text, structured elements and metadata. It usually includes text extraction, layout recognition, table and image handling, page number and source preservation, and noise cleanup.

Read the fable →

Data ingestion

OCR

Optical Character Recognition

OCR recognizes text from images, scans, or photos, allowing unstructured documents such as invoices, contracts, and forms to enter automated processing workflows.

Read the fable →

Data ingestion integration

Data connector

Data Connector

A Data Connector loads external files, databases, SaaS content, web pages, or APIs into the indexing and retrieval pipeline of an AI application.

Read the fable →

Data strategy / Competitive advantage

Data flywheel

Data Flywheel

A Data Flywheel is the mechanism by which product usage, business feedback, and outcome data continuously flow back to improve models, processes, knowledge bases, evaluation, and delivery quality.

Read the fable →

Decoding

Beam search

Beam Search

Beam Search is a decoding strategy that keeps multiple high-probability candidate sequences during generation. It is less likely than greedy decoding to be led astray by the single highest-probability step, but it increases computation cost and may generate overly conservative, formulaic text.

Read the fable →

Decoding

Decode

Decoding

Decoding is the process of converting the model's score distribution for the next token into actual output text. It includes strategies such as greedy, sampling, beam search, top-k, top-p, and temperature.

Read the fable →

Decoding

Greedy decoding

Greedy Decoding

Greedy Decoding selects the highest-probability next token at each step. It is fast, deterministic and low-cost, suitable for fixed-format, low-creativity, short-output tasks. But it tends to converge too early, generating monotonous text, and local optima may lead to a poor overall answer.

Read the fable →

Decoding

Logits

Logits

Logits are the raw scores a model outputs before softmax converts them into probabilities. Decoding parameters, constraints, banned words, temperature scaling, and sampling strategies all act on the logits or the distribution after conversion.

Read the fable →

Decoding

Sampling

Sampling

Sampling is a decoding method that randomly selects tokens according to the model's probability distribution. It can increase diversity and reduce the mechanical feel of greedy output, but it also brings non-reproducibility and low-probability errors.

Read the fable →

Decoding

Temperature

Temperature

Temperature is a parameter that controls the randomness of generation. A lower temperature makes the probability distribution sharper and the output more stable and conservative; a higher temperature makes the distribution flatter, increasing diversity and also increasing the probability of errors.

Read the fable →

Decoding

Top-k sampling

Top-k Sampling

Top-k Sampling limits the next-token candidates to the k with the highest probability, then samples from them. It can cut off long-tail low-quality tokens and reduce the risk of random sampling going out of control.

Read the fable →

Decoding

Top-p sampling

Top-p Sampling, Nucleus Sampling

Top-p Sampling, also called Nucleus Sampling, selects the smallest candidate set whose cumulative probability reaches p, then samples from it. It adapts better than top-k to different distribution shapes: few candidates for deterministic tasks, many for open-ended tasks.

Read the fable →

Deep Learning

Backpropagation

Backpropagation

Backpropagation is the core algorithm for computing gradients in neural network training. It propagates the output error backward through the network layer by layer, determining how each parameter should be adjusted. Without backpropagation, deep models are hard to train efficiently.

Read the fable →

Deep Learning

Deep learning

Deep Learning

Deep Learning is a method that uses multi-layer neural networks to learn representations and function mappings from data. It enables models to extract features layer by layer from raw or semi-structured data, powering modern speech, vision, language models, recommendation, retrieval and Agent systems.

Read the fable →

Deep Learning

Neural networks

Neural Network

A Neural Network is a model composed of a large number of interconnected artificial neurons or computational units that learns the mapping from input to output through weights, activation functions, and hierarchical structure. It is the foundation of deep learning, language models, vision models, and recommendation systems.

Read the fable →

Deep Learning

Representation learning

Representation Learning

Representation Learning is the process of letting a model learn useful representations from data. These representations can be embeddings, hidden-layer features, cross-modal vectors, or business entity representations, used to support classification, retrieval, recommendation, clustering, prediction, and Agent memory.

Read the fable →

Deployment

Canary release

Canary Release

Canary release means letting a small number of users, tenants, regions or traffic use a new version before a full rollout, using real metrics to decide whether to continue expanding. Its core is to limit the scope of impact while discovering problems in the production environment as early as possible.

Read the fable →

Deployment

Canary release

Gradual Rollout

A gradual rollout expands the scope of change step by step by user, tenant, region, traffic percentage, or use case. It is more complete than a one-time canary, including stage plans, entry criteria, observation windows, pause conditions, communication, and exception handling.

Read the fable →

Deployment / Enterprise procurement

Private deployment

Private Deployment, On-premises Deployment

Private deployment runs an AI system in a customer's own or dedicated environment to meet data security, compliance, and intranet access requirements.

Read the fable →

Deployment / Infrastructure

Localized deployment

Local Deployment, On-premises Deployment

Localized deployment runs software, models or systems in the customer's data center, private cloud, intranet or controlled environment.

Read the fable →

Deployment / infrastructure

Container

Container

Containers package an application and its runtime dependencies into portable, isolated units, making deployment, scaling and environment consistency easier to manage.

Read the fable →

Deployment / infrastructure

Kubernetes

Kubernetes, K8s

Kubernetes (K8s) is a container orchestration system used to schedule container runs, scaling, service discovery, rolling updates, health checks and self-healing. Simply put, it keeps a group of containerized services running continuously as expected.

Read the fable →

Deployment / release engineering

Blue-green deployment

Blue-Green Deployment

Blue-green deployment keeps two systems close to the production environment: one is currently handling real traffic, while the other has the new version deployed in advance. After the new version passes validation, traffic is switched over; if problems arise, traffic is switched back to the old environment to complete the rollback.

Read the fable →

Deployment / release engineering

Canary release

Canary Deployment

Canary release first exposes a new version to a small amount of traffic or users for validation, then gradually expands the scope once stability is confirmed, in order to reduce release risk.

Read the fable →

DevOps / infrastructure

Infrastructure as Code

Infrastructure as Code, IaC

Infrastructure as Code (IaC) manages servers, networks, permissions, databases, and cloud resources using declarative configuration or scripts, rather than manually clicking through each item in a console.

Read the fable →

DevOps / operations

GitOps

GitOps

It treats the Git repository as the single trusted source of the system's desired state, describes infrastructure and application configuration in declarative files, and automated controllers continuously synchronize the actual environment to the state described in Git.

Read the fable →

DevOps / release engineering

Continuous integration and continuous delivery

CI/CD, Continuous Integration / Continuous Delivery

CI/CD turns code integration, testing, packaging, deployment, release and rollback into an automated pipeline, enabling software changes to be delivered more frequently and reliably. It turns release quality from ad-hoc manual checks into a repeatable process.

Read the fable →

Dialogue / workflow

Slot filling

Slot Filling

Slot filling is the identification and completion of key fields in dialogue or form tasks, such as identity, time, place, product, quantity, and contact information.

Read the fable →

Diffusion

Noise predictor/UNet

UNet / Noise Predictor

UNet / Noise Predictor is the denoising network backbone in many diffusion models, used to predict the noise or denoising direction in the current sample. UNet obtains global context through encoder downsampling, then restores details through decoder upsampling, and uses skip connections to preserve local information.

Read the fable →

Distributed inference

Pipeline parallelism

Pipeline Parallelism

Pipeline parallelism splits model layers across multiple devices, letting micro-batches advance like an assembly line to reduce device idle time.

Read the fable →

Distributed inference

Tensor parallelism

Tensor Parallelism

Tensor parallelism splits a single weight matrix or tensor operation across multiple GPUs. Each device computes part of the same layer, and the results are then combined through communication.

Read the fable →

Distributed training

Data parallelism

Data Parallelism

Data Parallelism is a common method in distributed training: replicate the same model across multiple GPUs or machines, with each replica processing a different data batch, then synchronize gradients or parameter updates. It can improve training throughput and is one of the foundational parallel strategies for large-model pretraining and fine-tuning.

Read the fable →

Distributed training

FSDP

Fully Sharded Data Parallelism

Fully Sharded Data Parallelism, FSDP is a distributed training strategy that shards model parameters, gradients, and optimizer states across multiple devices, rather than having each data-parallel replica hold all states in full.

Read the fable →

Distributed training

ZeRO

Zero Redundancy Optimizer

Zero Redundancy Optimizer, ZeRO is an optimization strategy that reduces memory redundancy in data-parallel training. By sharding optimizer states, gradients, and model parameters, it avoids every GPU storing all training states in full, thereby significantly lowering memory usage.

Read the fable →

Document AI

Layout analysis

Layout Analysis

Layout Analysis is the process of identifying the structure of a document page, including headings, paragraphs, tables, images, lists, headers and footers, and reading order. It usually follows OCR or text extraction and is an important step in document parsing, table extraction and RAG chunking.

Read the fable →

Document AI

Table extraction

Table Extraction

Table Extraction is the process of recognizing table structure and cell content from PDFs, images, scans or documents. It not only extracts text, but also restores table regions, rows and columns, headers, merged cells, cross-page relationships and coordinate sources.

Read the fable →

Documentation

Dataset datasheet

Datasheet for Datasets

A dataset card structurally records a dataset's motivation, composition, collection, preprocessing, uses, limitations, risks, and maintenance methods.

Read the fable →

Documentation

Model Card

Model Card

A Model Card is a structured document describing a model's purpose, training data, evaluation results, limitations, risks, applicable scenarios, and ethical considerations. When an enterprise procures, deploys, or fine-tunes a model, the model card helps product, engineering, legal, and risk teams understand the model's boundaries and provides evidence for audits, vendor assessments, and launch approvals.

Read the fable →

Documentation

System card

System Card

The system card describes the capabilities, components, risks, mitigations, evaluation results, applicable boundaries and oversight mechanisms of a deployed AI system.

Read the fable →

Embedding database

Chroma

Chroma

Chroma is an open-source lightweight embedding database designed for local development and rapid prototyping. With just a few lines of code, it can store embedding vectors, documents, and metadata locally, and provide similarity search.

Read the fable →

Embeddings

Embed

Embedding

Embedding is the conversion of text, images, audio, code, users, products, or other objects into a set of numerical vectors. This vector is not a label for people to read, but a semantic coordinate for machines to compute.

Read the fable →

Embeddings

Semantic similarity

Semantic Similarity

Semantic Similarity measures how close two pieces of text, questions, tasks or objects are in meaning, usually implemented through embedding vector distance or similarity calculation. It is the foundation of semantic search, deduplication, clustering, recommendation, RAG retrieval and ticket routing.

Read the fable →

Embeddings

Vector database

Vector Database

A vector database is a data system specifically for storing embedding vectors and retrieving nearest neighbors by similarity. It is often used for semantic search, recommendation, deduplication, and RAG.

Read the fable →

Embeddings

Word embeddings

Word Embedding

Word Embedding is a technique for representing words or tokens as vectors, enabling models to capture statistical and semantic relationships between words through spatial positions. Similar words are usually closer together in vector space, and relational patterns can also be used by the model.

Read the fable →

Engineering organization / infrastructure

Platform Engineering

Platform Engineering

Platform engineering improves engineering delivery efficiency and governance consistency through internal developer platforms, self-service capabilities, standard templates, and shared infrastructure.

Read the fable →

Engineering organization / platform

Developer experience

Developer Experience, DevEx

Developer Experience, DevEx measures the efficiency, smoothness, and cognitive load developers face from understanding, developing, testing, deploying, to troubleshooting.

Read the fable →

Enterprise AI application / Retrieval

Knowledge base Q&A

Knowledge Base Q&A, KBQA, RAG Q&A

Knowledge base Q&A connects enterprise documents, policies, product materials, and business knowledge to retrieval and generation systems, providing natural-language answers with supporting evidence.

Read the fable →

Enterprise AI orchestration SDK

Semantic Kernel

Semantic Kernel

Semantic Kernel is Microsoft's open-source AI orchestration SDK, positioned for integrating large language models, plugins, planners, memory, and native application code into enterprise applications.

Read the fable →

Enterprise collaboration / Solution design

Co-creation

Co-creation, Joint Solution Development

Co-creation is when a supplier and customer jointly define scenarios, data, processes, and acceptance criteria around real business problems, and then jointly refine the solution.

Read the fable →

Enterprise implementation / Adoption

Pilot

Pilot, Pilot Program

A pilot runs a solution on a small scale in a real business environment, to validate willingness to adopt, process fit, operating cost, stability and conditions for replication.

Read the fable →

Evaluation

Evaluation benchmark

Benchmark

A benchmark is a standardized set of tasks, datasets, metrics or test suites used to compare the capabilities of models, Agents or systems. A good benchmark is not just a leaderboard question; it must correspond to real business scenarios, failure boundaries and acceptance criteria.

Read the fable →

Evaluation

Benchmark contamination

Benchmark Contamination

Benchmark contamination means that evaluation questions, answers, or highly similar samples have entered the training data, prompt examples, tuning process, or model selection process, causing the model to perform artificially well on the benchmark. For enterprise Agents, contamination distorts release evaluations: the system appears to handle customer problems, but in reality it has only seen the test samples.

Read the fable →

Evaluation

Data leakage

Data Leakage

Data leakage means information that should not be present during training, tuning, model selection, or evaluation enters the system early, distorting performance estimates. It includes not only leaked test answers but also target labels, future information, human annotations, customer outcomes, similar examples, or production feedback flowing back inappropriately.

Read the fable →

Evaluation

Distribution shift

Distribution Shift

Distribution shift means the data distribution faced during model training, validation, or historical evaluation is inconsistent with the real input distribution after deployment. It can make offline scores good while online performance worsens. Common shifts for enterprise Agents include changes in customer base, industry language, task types, tool return formats, channels, and policies.

Read the fable →

Evaluation

Perplexity

Perplexity

Perplexity is a language model evaluation metric used to measure how easily a model predicts a text sequence. Lower perplexity usually means the model predicts that text distribution better. It is suitable for evaluating language modeling and how well a model fits similar corpora, but it cannot directly represent an Agent's task completion rate, factual correctness, safety or tool-calling ability.

Read the fable →

Evaluation

Step success rate

Step Success Rate

Step success rate measures the proportion of intermediate steps executed correctly in a multi-step task. For enterprise Agents, it locates quality problems better than final success rate alone: whether the plan is reasonable, whether retrieval hits, whether the right tool is chosen, whether parameters are correct, whether permissions pass, and whether exceptions are handled.

Read the fable →

Evaluation

Tool call accuracy

Tool Call Accuracy

Tool call accuracy measures whether an Agent picks the right tool, fills in the right parameters, calls it compliantly, and reasonably uses the results returned by the tool.

Read the fable →

Evaluation

Trajectory evaluation

Trajectory Evaluation

Trajectory evaluation is the holistic assessment of an Agent's execution process, including plans, reasoning steps, tool calls, observations, retries, exception handling, and final output. It suits multi-step tasks because the final answer may mask overreach, luck, incorrect tool calls, or non-reproducible paths in the process.

Read the fable →

Evaluation infrastructure

LLM evaluation platform

LLM Evaluation Platform

An LLM evaluation platform manages datasets, test cases, scoring functions, human annotation, model judges, regression checks, experiment comparisons, and release gates. It turns evaluation from scattered scripts into a continuous quality system.

Read the fable →

FinOps / operations

Cost Attribution

Cost Attribution

Cost attribution allocates model calls, cloud resources, tools, human review and operational costs to customers, features, workflows or task outcomes.

Read the fable →

Fine-Tuning

Fine-tuning

Fine-Tuning

Fine-Tuning is continuing to train a pre-trained model with domain-specific, task-specific, or behavioral data to make it more suitable for the target scenario. It can improve tone, format, domain knowledge usage, tool-calling habits, and task completion stability, but it also brings issues of data governance, overfitting, evaluation, rollback, and cost.

Read the fable →

Fine-Tuning

Instruction fine-tuning

Instruction Tuning

Instruction Tuning is training a model with a large number of instruction-response examples so that it better understands human task requirements and outputs according to instructions. It moves a base model from simply predicting text toward being more suitable for interaction scenarios such as question answering, summarization, rewriting, classification, formatted output, refusing inappropriate requests, and pre-tool judgment.

Read the fable →

Fine-Tuning

Low-Rank Adaptation

Low-Rank Adaptation, LoRA

LoRA is a parameter-efficient fine-tuning method that freezes the original model weights while injecting small low-rank matrices, adapting with fewer parameters.

Read the fable →

Fine-Tuning

Parameter-efficient fine-tuning

Parameter-Efficient Fine-Tuning, PEFT

Parameter-efficient fine-tuning trains only a small number of newly added or selected parameters to adapt a base model; common methods include LoRA, Adapter, and Prefix Tuning.

Read the fable →

Fine-Tuning

Supervised Fine-Tuning

Supervised Fine-Tuning, SFT

Supervised fine-tuning trains a model with labeled examples that have target outputs, so the model learns to generate the expected response given a given input.

Read the fable →

Fine-tuning

Full fine-tuning

Full Fine-Tuning

Full fine-tuning updates all or most of a model's parameters, offering strong adaptation capability but higher training cost, memory requirements, and risk of catastrophic forgetting.

Read the fable →

Fine-tuning

Instruction data

Instruction Data

Instruction Data is data used to train or evaluate a model's instruction-following ability, usually containing user instructions, context, expected responses, refusal examples, format requirements and sometimes tool-calling traces.

Read the fable →

Fine-tuning

Layer-wise learning rates

Layer-wise Learning Rate

Layer-wise Learning Rate means setting different learning rates for different model layers during fine-tuning, commonly with smaller rates for lower layers and larger rates for higher or task-related layers. It helps preserve general representations while letting the model adapt to new tasks, reducing catastrophic forgetting and overfitting risk.

Read the fable →

Fine-tuning

rejection sampling

Rejection Sampling

In AI training, rejection sampling often means generating multiple candidate outputs and keeping only qualified samples according to quality standards, used to construct higher-quality fine-tuning or preference data. It can improve data quality, but depends on the reliability of filters, reward models, or human annotation.

Read the fable →

Foundations

Artificial Intelligence

Artificial Intelligence, AI

Artificial Intelligence is the broad field of building systems capable of intelligent tasks such as perception, language, reasoning, planning and decision-making. In an enterprise context, AI should not be understood as a single model, but as a combination of capabilities, data, processes, controls and business delivery methods.

Read the fable →

Foundations

Model

Model

A model is a simplified system learned from data or experience, used to map inputs to outputs, such as prediction, classification, generation, or decision-making.

Read the fable →

Generative AI

Diffusion models

Diffusion Model

A Diffusion Model is a generative model that progressively adds noise to real data during training, then learns the reverse denoising process; during generation it starts from random noise and, through multiple denoising steps, produces images, audio, video or other samples. Its strength is high-quality generation and controllable editing; the cost is many inference steps and heavy computation.

Read the fable →

Generative modeling

Diffusion Transformer

Diffusion Transformer, DiT

DiT uses the Transformer as the generative backbone of a diffusion model, typically slicing an image or latent space into tokens before denoising modeling.

Read the fable →

Generative modeling

Latent Diffusion Model

Latent Diffusion Model, LDM

Latent Diffusion Model, LDM performs diffusion denoising in a compressed latent space rather than generating directly in the original pixel space. Typically, an autoencoder first encodes the image into a low-dimensional latent, then diffusion is performed on the latent, and finally it is decoded back into an image.

Read the fable →

Go-to-market / Implementation

Scenario-based implementation

Scenario-based Implementation, Use-case Implementation

Scenario-based implementation starts from specific business roles, inputs and outputs, system integration, and acceptance metrics, turning AI capabilities into deliverable processes.

Read the fable →

Governance

AI impact assessment

AI Impact Assessment, AIIA

AI impact assessment evaluates the impact on individuals, business, law, privacy, security, and fairness before system deployment and during operation.

Read the fable →

Governance

AI use case checklist

AI Use Case Inventory

An AI Use Case Inventory is a list of AI use cases maintained by an organization, recording use case name, business purpose, system/model, data inputs, vendor, owner, risk classification, operating status, review records, and retirement plan.

Read the fable →

Governance

Data lineage

Data Lineage

Data Lineage is the full-process relationship tracking data from source, processing, transformation, and merging to its final point of use.

Read the fable →

Governance

Governance, Risk & Compliance

Governance, Risk, and Compliance, GRC

GRC unifies governance, risk, control, policy, audit, and compliance obligations, and is the foundational control framework for enterprises introducing Agents.

Read the fable →

Governance

Policy engine

Policy Engine

A Policy Engine is a component that evaluates rules at runtime and decides whether to allow, deny, restrict, or escalate an action. It typically makes judgments based on subject, resource, action, context, risk level, and approval status.

Read the fable →

Governance

Proof of origin

Provenance

Provenance is the evidence about the origin, author, authorization and transformation history of data, content or output. Enterprise Agents read documents, retrieve knowledge bases, call external APIs, reference customer data and generate new content, so it must be known where the material comes from, whether it is trustworthy, whether there is a right to use it, and what processing it has undergone.

Read the fable →

Governance

Shadow AI

Shadow AI

Shadow AI is the use of AI tools, models or Agents by employees or teams without formal approval, security review, procurement visibility or governance controls. It can bring data leaks, vendor risk, compliance violations, unauditable decisions and duplicate procurement.

Read the fable →

Governance

Traceability

Traceability

Traceability is the ability to reconstruct why a system produced a certain output or took a certain action. In enterprise Agents, it requires linking the user request, context, retrieval sources, model selection, prompt version, tool calls, permission decisions, human approvals, external writes and final results.

Read the fable →

Governance

Transparency

Transparency

Transparency requires clearly disclosing the AI system's purpose, capabilities, limitations, data use, decision-making role, responsible parties, and user choices.

Read the fable →

Governance

Trustworthy AI

Trustworthy AI

Trustworthy AI means a system meets requirements for compliance, ethics, fairness, privacy, security, robustness, transparency, oversight, and accountability for a specific use.

Read the fable →

Governance and control

Agent policy

Agent Policy

Agent Policy defines the rules for what an agent is allowed, forbidden or required to do regarding data, tools, users, external actions, budgets, communication and escalation. It should be usable by the runtime, policy engine and audit mechanisms, not just be natural-language principles.

Read the fable →

Governance/Compliance

AI disclosure

AI Disclosure

AI disclosure is telling users, employees, or affected parties in appropriate contexts that AI participated in content generation, interaction, recommendations, or decisions.

Read the fable →

Governance/Compliance

Control everyone

Control Owner

A Control Owner is the person or function responsible for the design, operation, evidence, testing and improvement of a control. In enterprise Agent governance, controls may include permission approval, sensitive data filtering, human review, log retention, model change approval, vendor review and exception escalation.

Read the fable →

Governance/Operations

Human oversight

Human Oversight

Human Oversight is the use of human review, approval, monitoring, intervention, override, pause, or escalation mechanisms to prevent or mitigate improper consequences caused by AI systems. Effective oversight is not manually approving every action, but placing people at key decision points based on risk, impact, confidence, and anomaly signals, and giving them sufficient information and authority.

Read the fable →

Governance/Risk

Bias

Bias

Bias is a systematic skew in data, models, design, objective functions, or deployment processes that can lead to inaccurate, unfair, or harmful outcomes. Bias in enterprise Agents can come from historical data, labeling bias, insufficient sampling, feedback loops, proxy variables, or business rules.

Read the fable →

Governance/Risk

Explainability

Explainability

Explainability is the ability of an AI system to explain the key reasons, evidence, factors, and limitations of an output or decision in a way suited to the use case. For enterprise Agents, explainability helps business staff judge whether to adopt a recommendation, helps users appeal, and helps audit and risk teams trace problems.

Read the fable →

Governance/Risk

Fairness

Fairness

Fairness means AI systems avoid unjustified adverse treatment or outcomes for protected or business-relevant groups. It requires defining the relevant groups, measuring disparate impact, analyzing causes, and setting fairness metrics and mitigation measures.

Read the fable →

Governance/Risk

Three lines of defense

Three Lines of Defense

Three Lines of Defense is a governance model that divides responsibility into three categories: the first line owns and manages risk in business teams; the second line sets frameworks, oversees, and challenges through functions such as risk, compliance, and security; the third line provides assurance through independent functions such as internal audit.

Read the fable →

Governance/Safety

Content filtering

Content Filtering

Content Filtering is the detection, classification, and handling of user input, model output, and interaction context to intercept illegal, harmful, fraudulent, hateful, violent, self-harm, privacy-leaking, or policy-violating content.

Read the fable →

Governance/Security

Policy as code

Policy as Code

Policy as code expresses security, compliance, and business governance rules in machine-executable code, and manages those rules through version control, testing, and auditing.

Read the fable →

IT operations / automation

AI Operations

AIOps

AIOps more accurately means intelligent operations: using machine learning and automation to analyze logs, metrics, traces, alerts, and incident records, helping teams detect anomalies, reduce noise, locate root causes, and drive response. This is not a general reference to maintaining AI systems, but to using AI methods to improve operational judgment and handling efficiency.

Read the fable →

Implementation / Project governance

Delivery acceptance

Delivery Acceptance, Acceptance Testing, Project Acceptance

Delivery acceptance is the process by which a customer or project owner confirms, according to pre-agreed standards, whether deliverables meet contract, functional, performance, security, business outcome, and operational requirements.

Read the fable →

Inference

Autoregressive decoding

Autoregressive Decoding / Decode Phase

Autoregressive decoding, also known as the Decode Phase, is the stage in which a large model generates tokens one by one after processing the input. Each new token depends on what has already been generated, so it naturally has sequential dependencies and cannot be fully parallelized like batch reading of input.

Read the fable →

Inference

Best-of-N sampling

Best-of-N Sampling

Best-of-N sampling can also be understood as "selecting the best among multiple candidates": the system generates N candidate answers at once, then uses a scorer, rules, verifier, or human standard to choose the best one. It is not about having the model generate only once, but about spending more computation at request time in exchange for higher quality.

Read the fable →

Inference

Context pruning

Context Pruning / Prompt Compression

Context pruning deletes or compresses low-relevance content, shortens the prompt length, reduces KV cache usage and lowers prefill latency.

Read the fable →

Inference

Dynamic batching

Dynamic Batching / In-flight Batching

Dynamic batching adds new requests while an existing batch is still running, rather than waiting for the whole batch to finish, thereby improving inference serving throughput and GPU utilization.

Read the fable →

Inference

Early departure

Early Exiting

Early exit, also called early-exit inference, lets a model stop at an intermediate layer when confidence is high enough, instead of running the entire model every time. Simple samples use less computation, while difficult samples still take the full path.

Read the fable →

Inference

Flash Attention

FlashAttention

FlashAttention is an IO-optimized attention algorithm that reduces memory reads and writes through tiling and operator fusion, lowering the overhead of attention on long sequences.

Read the fable →

Inference

Inference

Inference

Here, inference refers to model inference or model execution: applying a trained model to new input and generating output. It is not logical reasoning in the human sense, but the model performing computation on the current request.

Read the fable →

Inference

Cache offloading

KV Cache Offloading

KV cache offloading moves less active KV cache blocks from GPU memory to CPU memory or SSD. This allows the system to support longer contexts or more concurrent requests without being entirely limited by GPU memory.

Read the fable →

Inference

Quantized KV cache

KV Cache Quantization

KV cache quantization stores the key-value cache during inference at lower precision, supporting longer context or higher concurrency under limited VRAM.

Read the fable →

Inference

Operator fusion

Kernel Fusion

Operator fusion combines multiple GPU operations into a single kernel, reducing memory round trips and launch overhead, and is a common optimization in high-performance inference runtimes.

Read the fable →

Inference

Latency

Latency

Latency is the time a model or Agent system takes from receiving a request to returning a response, or generating tokens. It may include queuing, routing, retrieval, tool calls, prefill, first token, decoding, and post-processing.

Read the fable →

Inference

Retrospective decoding

Lookahead Decoding

Lookahead decoding is a class of methods for accelerating autoregressive generation: it constructs candidate n-gram sequences in parallel, then the main model verifies the candidates in parallel. It is related to speculative decoding but does not rely on a separate draft model.

Read the fable →

Inference

Medusa

Medusa

Medusa is a speculative decoding method: multiple decoding heads are added on top of the base model, letting these heads predict future tokens in parallel, and then the base model verifies which can be accepted.

Read the fable →

Inference

Model serving

Model Serving

Model serving is the runtime layer that puts a model into production and reliably handles inference requests through APIs. It is not just "the model can run"; it also includes endpoints, batching, scheduling, autoscaling, GPU allocation, caching, streaming output, authentication, monitoring, rate limiting, fallback, and SLA management.

Read the fable →

Inference

Paged attention

Paged Attention

Paged attention stores the KV cache in fixed-size, potentially non-contiguous pages or blocks, rather than requiring each sequence to occupy one large contiguous stretch of VRAM. This reduces memory fragmentation and improves GPU memory utilization.

Read the fable →

Inference

Prefill

Prefill Phase

The prefill stage is the stage at the very beginning of inference when the model first processes all input tokens in parallel and builds the KV cache. It occurs before token-by-token decoding and usually significantly affects time to first token.

Read the fable →

Inference

Prefix caching

Prefix Caching

Prefix caching reuses the already-computed KV cache for the same prompt prefix, such as system prompts, shared policy text, product documents or long reference context. It caches the computation results of the shared context, not the final answer directly.

Read the fable →

Inference

Quantization

Quantization

Quantization uses low-precision numerical representations for model weights or activations to reduce memory, storage, and compute costs, but precision loss must be controlled.

Read the fable →

Inference

Speculative decoding

Speculative Decoding

Speculative decoding first uses a small model to generate candidate tokens, then has a large model verify them in parallel, accelerating generation with essentially no quality loss.

Read the fable →

Inference

Speculative editing

Speculative Editing

Speculative editing applies the idea of speculative decoding to editing tasks: a faster assistant first proposes local edits or continuations, and then a stronger model verifies, accepts, or corrects them.

Read the fable →

Inference

Speculative prefix tree

Speculative Prefix Tree

Speculative prefix trees organize multiple candidate generation paths into a tree structure, exploring and verifying them in parallel to improve the acceptance rate of speculative decoding.

Read the fable →

Inference

Speculative sampling

Speculative Sampling

Speculative sampling, often also described as a form of speculative decoding, first samples candidate tokens through a draft process, then has the target model accept or reject them. The final output should still preserve the target model's original distribution.

Read the fable →

Inference

Test-time compute

Test-Time Compute / Inference-Time Scaling

Test-time compute, or more plainly inference-time scaling, is spending extra compute while the model is running to improve output quality. Here, "test-time" does not mean the software testing phase, but the phase when the model generates an answer for a new input.

Read the fable →

Inference

Throughput

Throughput

Throughput measures the number of requests or tokens a model service processes per unit time, and is a core metric for evaluating inference system capacity and cost efficiency.

Read the fable →

Inference

Tree search

Tree Search

It expands a decision problem into a tree structure: the current state is the root node, each action produces child nodes, future possible states continue to expand, and finally a better path is chosen through evaluation.

Read the fable →

Inference optimization

Continuous batching

Continuous Batching

Continuous batching dynamically schedules the tokens of multiple requests together while the model is running. When some sequences finish, new requests can enter the still-running batch without waiting for the entire batch of requests to finish.

Read the fable →

Inference optimization

Prompt caching

Prompt Caching

Prompt caching reuses already processed system prompts, document prefixes or shared context, reducing repeated prefill computation and thereby lowering latency and cost.

Read the fable →

Infrastructure

Runtime

Runtime

A runtime is the environment that executes an Agent, responsible for tool calls, permissions, memory, state, and lifecycle control, determining what the system can do and how it converges.

Read the fable →

Knowledge access

Retrieval-Augmented Generation

Retrieval-Augmented Generation (RAG)

Retrieval-Augmented Generation (RAG) retrieves relevant material from external knowledge bases, document stores, databases or search systems before generating an answer, then passes that material to the model as context for generating the answer.

Read the fable →

Knowledge representation

Knowledge graph

Knowledge Graph

A knowledge graph uses entities, relationships, and attributes to represent knowledge in a structured way, suitable for entity queries, relationship analysis, compliance tracing, and recommendations.

Read the fable →

Knowledge representation

Ontology

Ontology

Ontology is a structured definition of the concepts, categories, properties, relationships, and constraints in a domain. It helps systems unify "what is what, how they relate to each other, and which inferences are allowed." In enterprise Agents and knowledge graphs, ontologies are used to reduce naming confusion and support relational reasoning, permission boundaries, data integration, and explainable retrieval.

Read the fable →

Knowledge representation

Triple

Triple

A triple is usually expressed in a "subject-predicate-object" structure to represent a fact or relationship, for example "Shopkeeper Zhao-operates-Linji Tea House."

Read the fable →

Knowledge-augmented generation

Graph-enhanced retrieval generation

Graph RAG

Graph RAG introduces knowledge graphs, entity relationships, graph traversal, or community summaries into RAG. Traditional chunk-level vector search is good at finding similar text, but it easily misses structure for questions involving multi-hop relationships, entity associations, or supply chain/organization/contract chains.

Read the fable →

LLM

Context window

Context Window

Context Window is the total amount of input and output a model can process in a single request, usually measured in tokens. It determines the space that prompts, retrieved materials, historical messages, tool results, and generated answers can collectively occupy.

Read the fable →

LLM

Language model

Language Model

A language model models sequences of language based on context. Common capabilities include predicting the next token, generating text, understanding intent, rewriting, summarizing, and question answering.

Read the fable →

LLM

Large Language Model

Large Language Model, LLM

A large language model is a language model trained on large-scale corpora and parameter scale, with generation, comprehension, reasoning expression, code and generalization capabilities.

Read the fable →

LLM API gateway and SDK

LiteLLM

LiteLLM

LiteLLM provides an OpenAI-style unified interface, SDK and proxy layer across multiple model providers. Developers can integrate different models in a more consistent way without having to write a completely different calling logic for each provider.

Read the fable →

LLM Agents

Agent

Agent

An agent is an AI work unit that, under a given goal, perceives context, plans steps, calls tools, executes actions, and continues advancing based on results.

Read the fable →

LLM Agents

Memory

Memory

Memory is the ability of an AI system to save and reuse information, enabling an Agent to maintain continuity across steps, sessions or user interactions. Enterprise Agent memory typically includes working memory, long-term memory, episodic memory and semantic memory.

Read the fable →

LLM Agents

Planning

Planning

Planning is the process by which an AI system breaks down goals into steps, selects actions, and adjusts its route as conditions change. It is closer to real delivery than single-pass inference: it must handle goals, constraints, resources, dependencies, risks, approvals, and failure branches.

Read the fable →

LLM Agents

Tool calling

Tool Use, Function Calling

Tool calling lets models request external APIs or functions to retrieve information, compute results, or execute actions, and is a key capability for agents moving from conversation to getting things done.

Read the fable →

LLM Applications

Retrieval-Augmented Generation

Retrieval-Augmented Generation, RAG

RAG first retrieves external knowledge, then passes the relevant content as context to the model to generate an answer, reducing hallucinations and connecting private knowledge.

Read the fable →

LLM Behavior

Hallucination

Hallucination

Hallucination is information generated by a model that sounds plausible but is actually wrong, unsupported by evidence, or fabricated out of thin air. It commonly occurs when a model tries to fill in missing facts, answers with overconfidence, confuses similar information, or lacks reliable context.

Read the fable →

LLM Interaction

Few-shot prompting

Few-Shot Prompting

Few-Shot Prompting provides a small number of input-output examples in the prompt, letting the model learn the task format, judgment scale, and output style from the examples. It does not change the model weights, but guides model behavior within the current context.

Read the fable →

LLM Interaction

In-context learning

In-Context Learning

In-Context Learning is the model's ability to temporarily adjust its behavior based on instructions, examples and context in the prompt, without updating model weights. Few-shot, format examples, counterexamples and task descriptions all make use of this ability.

Read the fable →

LLM Interaction

Prompt

Prompt

A prompt is the input instruction or context given to a language model, and can include the task, question, background, examples, constraints, and expected output. It is the primary interface through which a user or application conveys intent to the model.

Read the fable →

LLM Interaction

Prompt engineering

Prompt Engineering

Prompt Engineering is the practice of designing prompts to guide model behavior and improve task performance, without changing model weights. It includes clarifying goals, providing context, setting constraints, giving examples, specifying output formats, and iterating on evaluation.

Read the fable →

LLM Interaction

System prompt

System Prompt, System Message

System Prompt or System Message is an instruction with high priority over model behavior, used to define roles, task boundaries, policy constraints, safety rules, and interaction methods. It sits at the upper level of the instruction hierarchy and should usually be higher than user messages.

Read the fable →

LLM Interaction

Zero-shot prompting

Zero-Shot Prompting

Zero-Shot Prompting is a prompting method that gives no examples and only uses task instructions to get the model to complete the work. It is suitable for scenarios where the model already has general capabilities, the task standards are clear, the risk is low, or it is not worth using context for examples.

Read the fable →

LLM Reasoning

Chain of Thought

Chain-of-Thought, CoT

Chain-of-Thought, CoT, is a prompting or training pattern that has models use intermediate reasoning steps to solve complex tasks. It can improve performance on multi-step tasks such as math, logic and planning; in application, the truthfulness and correctness of intermediate steps must be verified, and the display method chosen according to user needs.

Read the fable →

LLM application framework

LangChain

LangChain

LangChain is a framework for building LLM applications, using composable components to connect prompts, models, retrievers, tools, chains, and Agent workflows.

Read the fable →

LLM evaluation and observability library

TruLens

TruLens

TruLens is an LLM application evaluation and observability library that can add feedback functions to RAG and Agents to measure relevance, trustworthiness, and groundedness.

Read the fable →

LLM inference

Decoding stage

Decode Phase

The decoding phase is the autoregressive generation phase after prefill: the model generates one token at a time, reads the KV cache at each step, computes the next token, appends the new cache, and may stream tokens back to the user.

Read the fable →

LLM inference

Prefill

Prefill

Prefill is the stage in LLM inference that processes the input prompt/context and builds the initial KV cache. It occurs before the model generates the first token, and its computation usually grows with input length.

Read the fable →

LLM inference optimization

Paged attention

PagedAttention

PagedAttention manages KV cache blocks in a paged manner, reducing memory fragmentation and improving LLM serving throughput in high-concurrency scenarios.

Read the fable →

LLM inference server

Text generation inference

Text Generation Inference, TGI

TGI is Hugging Face's text generation inference server, supporting LLM deployment, batching, streaming output, and production serving interfaces.

Read the fable →

LLM infrastructure optimization

Cache

Caching

Cache and reuse existing responses, embeddings, retrieval results, tool results, or prompt prefixes to reduce latency, cost, and duplicate calls.

Read the fable →

LLM observability and evaluation platform

LangSmith

LangSmith

LangSmith is an observability, debugging, evaluation, monitoring and testing platform for LLM applications in the LangChain ecosystem. It helps teams record traces, manage datasets, run evals, compare experiments, debug prompts and observe Agent workflows.

Read the fable →

LLM observability and gateway tool

Helicone

Helicone

Helicone is an observability platform for LLM APIs, often used as a proxy to log latency, cost, cache hits and user feedback.

Read the fable →

LLM operations

Cost tracking

Cost Tracking

Cost tracking measures token usage, provider charges, cache savings, retry costs, tool call costs, and spend allocated by user, customer, team, or workflow.

Read the fable →

LLM orchestration abstraction

LangChain Expression Language

LangChain Expression Language, LCEL

LCEL is LangChain's declarative composition layer, used to connect prompts, models, parsers, retrievers and functions into a runnable pipeline.

Read the fable →

LLM program interface

Signature

Signature

Signature here refers to a task signature in DSPy, not a cryptographic signature. It is used to declare the input fields, output fields and semantic description of an LLM task.

Read the fable →

LLM programming and optimization framework

DSPy

DSPy

DSPy is a framework for programming and optimizing LLM systems.

Read the fable →

LLM runtime / optimization

KV cache

KV Cache, Key-Value Cache

The KV cache stores the keys and values already computed by the Transformer, so autoregressive generation does not need to repeatedly recompute historical tokens.

Read the fable →

LLM runtime / user experience

Time to First Token

Time to First Token, TTFT

Time to First Token (TTFT) measures the time from when a request is sent to when the first genuinely generated token is received in a streaming LLM response. It determines how quickly the system appears to start responding.

Read the fable →

LLMOps / application platform

Prompt management

Prompt Management

Prompt management is the practice of systematically managing prompt templates, variables, versions, experiments, approvals, and performance tracking. In LLM applications, prompts determine task boundaries, tone, tool calls, output formats, and safety constraints.

Read the fable →

LLMOps / quality

Evaluation

Evaluation, Evals

Evaluation uses human, rule-based, or model judges to measure an AI system's performance in task quality, safety, stability, and cost. Evals for enterprise Agents should cover real tasks, edge cases, regression samples, safety red lines, latency, and cost, and be tied to the release process.

Read the fable →

LLMOps / quality

Golden dataset

Golden Dataset, Golden Set

A golden dataset is a set of manually confirmed, reusable high-quality examples used for regression evaluation and comparison of models or prompts. For LLM applications, it usually contains real task inputs, expected outputs, scoring criteria, edge cases and safety prohibitions.

Read the fable →

Local model packaging

Model file configuration

Modelfile

A Modelfile is a configuration file for local model tools such as Ollama, used to define the base model, parameters, system prompt, and custom build method.

Read the fable →

Local model runtime

Ollama

Ollama

Ollama is a local model running and management tool that can pull, package, run and serve LLMs, suitable for deployment on personal machines or in private environments.

Read the fable →

MLOps / data platform

Feature Store

Feature Store

A feature store is a data platform component that centrally produces, stores, reuses, and serves machine learning features. It manages features used in training and features used in online inference in a unified way, reducing training-serving skew and giving features versions, lineage, quality checks, and reuse boundaries.

Read the fable →

MLOps / governance

Model version management

Model Versioning

Model version management tracks different combinations of models, data, parameters, and code to ensure deployment, rollback, and audit are reproducible. It is not just assigning version numbers to models; it also records training data, features, hyperparameters, evaluation results, approval status, deployment environment, and scope of use.

Read the fable →

MLOps / monitoring

Model drift

Model Drift

Model drift is the phenomenon in which changes in input distribution, target relationships, or business context in a production environment cause model or Agent performance to decline. It may come from user changes, business process changes, data collection method changes, external market changes, or adjustments to tools, policies, and upstream systems.

Read the fable →

MLOps / platform

Model registry

Model Registry

A model registry is a system for centrally managing model versions, metadata, approval status and deployment flow. It typically records model artifacts, versions, training sources, evaluation results, owners, risk levels, stage status and deployment targets.

Read the fable →

Machine Learning

Generalization

Generalization

Generalization means a model still performs well on unseen samples outside the training data, rather than only scoring high on data it has seen.

Read the fable →

Machine Learning

Gradient descent

Gradient Descent

Gradient Descent is an optimization method that uses gradient information to gradually update model parameters and reduce the loss function. The learning rate, batch size, and optimizer affect whether it descends steadily, oscillates, or falls into a poor region.

Read the fable →

Machine Learning

Hyperparameters

Hyperparameters

Hyperparameters are configurations set by people before or during training, such as learning rate, number of training epochs, batch size, number of model layers, context length and regularization strength. They are not learned by the model itself from data, yet they profoundly affect training cost, stability and final results.

Read the fable →

Machine Learning

Loss function

Loss Function

A loss function is a mathematical objective that measures the gap between the model's output and the target answer. During training, the model adjusts its parameters in the direction that reduces the loss, so the loss function is equivalent to telling the model "what counts as wrong, and by how much."

Read the fable →

Machine Learning

Machine learning

Machine Learning, ML

It lets computers work not only by rules written by hand, but also by learning patterns from data samples, using the learned patterns to predict, classify, generate, or decide on new inputs.

Read the fable →

Machine Learning

Overfitting

Overfitting

The model performs very well on the training data, but learns noise, accidental patterns or overly fine details, causing worse performance on new data.

Read the fable →

Machine Learning

Parameters

Parameters

Parameters are learnable numerical values inside a model, such as weights and biases in a neural network. The training process continuously adjusts these values so the model produces outputs from inputs that better match the objective.

Read the fable →

Machine Learning

Reinforcement Learning

Reinforcement Learning, RL

The agent observes states in the environment, chooses actions, receives rewards or punishments, and through repeated trial and error learns a policy that maximizes long-term returns.

Read the fable →

Machine Learning

Supervised Learning

Supervised Learning

The model is trained on labeled data: each sample has an input and its corresponding correct answer, and the model learns to predict the label from the input.

Read the fable →

Machine Learning

Test set

Test Set

A Test Set is held-out data used only after development choices are fixed, to estimate the model's final performance on unseen samples. It is one of the last acceptance checks before launch; once contaminated, metrics become inflated and business risk is underestimated.

Read the fable →

Machine Learning

Training set

Training Set

The Training Set is the data used to fit model parameters. It directly participates in learning, so data quality, coverage, label consistency, and leakage control determine what the model learns. Enterprises must not mix validation or test samples into the training set.

Read the fable →

Machine Learning

Unsupervised Learning

Unsupervised Learning

Unsupervised Learning finds structure in data without explicit labels, such as clustering, dimensionality reduction, anomaly detection, and topic discovery. It is suited to exploring unknown patterns, organizing large amounts of data, and discovering similar groups. When enterprises use it, they should avoid treating automatically discovered clusters directly as business truth; domain expert interpretation and validation are usually needed.

Read the fable →

Machine Learning

Validation set

Validation Set

A Validation Set is a dataset held out during development for tuning parameters and selecting approaches. It helps judge whether a model generalizes, but because it gets reviewed repeatedly, it cannot be treated as a final objective score.

Read the fable →

Managed agent API

OpenAI Assistants API

OpenAI Assistants API

The OpenAI Assistants API is a managed assistant interface that maintains persistent conversation state around threads, messages, runs, tools and file management.

Read the fable →

Managed agent object

Assistant

Assistant

An assistant is a preconfigured AI entity in a hosted Agent platform, usually bound to instructions, models, tools, and files—not just a one-off temporary chat.

Read the fable →

Managed model and agent API

OpenAI Responses API

OpenAI Responses API

The OpenAI Responses API is a unified interface for models and Agent-style workflows, supporting capabilities such as model responses, tool calls, multimodal input, structured output, and built-in tools.

Read the fable →

Managed retrieval tool

File search

File Search

File Search is a managed retrieval capability: it indexes uploaded files and retrieves relevant content when the model generates an answer. It typically handles the file ingestion, chunking, indexing, and recall stages of RAG, and is suitable for contracts, manuals, knowledge bases, and similar scenarios, but it still requires handling permission isolation, file updates, citation quality, and answer evaluation.

Read the fable →

Managed tool execution

Code Interpreter

Code Interpreter

Code Interpreter is a hosted tool that lets models write and run code in a controlled sandbox, commonly used for data analysis, file processing, computation, visualization, and temporary script execution.

Read the fable →

Managed vector database

Pinecone

Pinecone

Pinecone is a managed vector database service that provides vector storage, similarity search, and metadata filtering for production-grade AI applications.

Read the fable →

Marketing / Enterprise sales

Benchmark case

Reference Case, Lighthouse Case, Benchmark Customer Case

A benchmark case is a reusable representative customer success sample, used to prove that the product has truly produced results in a certain industry, scenario, or budget pool.

Read the fable →

MoE

Auxiliary loss

Auxiliary Loss / Load Balancing Loss

Auxiliary loss is an additional constraint in MoE training, used to distribute tokens more evenly across experts and avoid overloading or idling a small number of experts.

Read the fable →

MoE

Expert routing

Expert Routing / Gating

Expert routing is the mechanism in MoE that determines which experts each token is sent to for processing, usually by having a gating network score and select experts.

Read the fable →

MoE

Top-k routing

Top-k Routing

Top-k Routing is a strategy for MoE gating: each token is sent only to the k highest-scoring experts, rather than all experts.

Read the fable →

Model Risk Management

Model inventory

Model Inventory

A Model Inventory is a centralized record of models in development, validation, production, retirement, or third-party use, including ownership, purpose, status, risk, and metadata.

Read the fable →

Model Risk Management

Model monitoring

Model Monitoring

Model monitoring is the continuous measurement of a model's behavior, performance, inputs, outputs, risks, and incidents after deployment. It covers data drift, concept drift, quality degradation, latency, cost, anomalous outputs, safety incidents, and business metrics.

Read the fable →

Model Risk Management

Model risk management

Model Risk Management, MRM

Model risk management is the discipline of governing the risks arising from model errors, misuse, drift, limitations, assumptions and operational failures. MRM typically includes model inventory, risk tiering, model validation, approval, monitoring, change management, vendor model management, exception handling and periodic review.

Read the fable →

Model Risk Management

Model validation

Model Validation

Model validation is an independent or structured review used to determine whether a model is suitable for its intended use, whether its performance meets expectations, and whether its limitations are clear. It typically examines the model's purpose, data, assumptions, methods, performance, stability, bias, boundary conditions, documentation, and monitoring plan.

Read the fable →

Model interface

Function calling

Function Calling

Function Calling is a model interface: developers predefine function names, parameter schemas, and descriptions; when the model needs to call an external capability, it outputs a machine-readable function name and parameters, which the application validates and executes.

Read the fable →

Model interface

JSON mode

JSON Mode

JSON Mode is a generation mode used to encourage or constrain a model to output valid JSON rather than free text. It is suitable for scenarios that require machine parsing, such as information extraction, configuration generation, and lightweight structured returns.

Read the fable →

Model interface

Structured output

Structured Output

Structured Output is the practice of constraining a model response to a specified structure or schema, such as a JSON object, field types, enums, arrays, and nested objects.

Read the fable →

Model interface

Structured output

Structured Outputs

Structured output constrains the model to return results according to a fixed schema such as JSON, so downstream systems can reliably parse, validate, and process them automatically.

Read the fable →

Multi-agent architecture

Supervisor agent

Supervisor Agent

A Supervisor Agent is the supervision and coordination role in a multi-agent system. It monitors task progress, assigns subtasks, coordinates subagents, handles failures, and decides when to replan, escalate to a human, merge results or stop execution.

Read the fable →

Multi-agent coordination

Group chat orchestration

Group Chat Orchestration

Group Chat Orchestration is the orchestration mechanism in a multi-agent shared conversation. It selects the next speaker, routes messages, manages context, determines whether the task is complete, and prevents repetition, drift and infinite loops.

Read the fable →

Multi-agent framework

AutoGen

AutoGen

AutoGen is a framework for building multi-agent applications. It lets multiple conversational agents collaborate through message passing, and can call tools, execute code, involve humans, or orchestrate group chats.

Read the fable →

Multi-agent organization unit

Agent team

Crew

A Crew is a team organizational unit in a multi-Agent system, typically composed of multiple Agents with roles, goals, tools, and task boundaries. It emphasizes organizing complex work into a collaborative team rather than having a single Agent handle all capabilities.

Read the fable →

Multi-agent role

User Proxy Agent

User Proxy Agent

User Proxy Agent is a role representing the user in multi-Agent systems, commonly seen in AutoGen. It can provide human input, approve actions, execute controlled code on the user's behalf, or hand questions back to a real person.

Read the fable →

Multi-agent workflow framework

CrewAI

CrewAI

CrewAI is a multi-Agent workflow framework that organizes collaboration through role-based Agents, tasks, tools, and processes, and is suited to building team-style automation.

Read the fable →

Multimodal

CLIP

Contrastive Language-Image Pre-training

CLIP (Contrastive Language-Image Pre-training) aligns image and text representations through contrastive learning: matching image-text pairs are closer in vector space, while mismatched ones are farther apart. It is an important foundation for multimodal retrieval, zero-shot classification, and image-text understanding.

Read the fable →

Multimodal

Cross-Modal Alignment

Cross-Modal Alignment

Cross-modal alignment makes different forms of information—text, images, audio, video—point to the same object or meaning. For example, a text description, an image, and an operation video should all be understood by the model as the same artifact, step, or risk point.

Read the fable →

Multimodal

Multimodal models

Multimodal Model

A Multimodal Model is a model capable of handling multiple modalities, such as text, images, audio, and video, and may generate or reason across modalities. In enterprise scenarios, multimodal models can be used for quality inspection, customer service, document understanding, video patrol, voice interaction, training, and on-site support.

Read the fable →

Multimodal AI

Video understanding

Video Understanding

Video Understanding is a model's ability to comprehend visuals, objects, actions, speech, subtitles, and temporal relationships in a video. Unlike single-image recognition, it focuses on sequence, events, causality, and cross-modal cues.

Read the fable →

Multimodality

Contrastive learning

Contrastive Learning

Contrastive Learning is a method of learning representations by comparing positive and negative samples. The model is trained to bring vectors of semantically similar or same-class samples closer together and push unrelated or easily confused samples farther apart. It is commonly used in embedding models, cross-modal alignment, retrieval models, recommendation, and similar case matching.

Read the fable →

Multimodality

Cross-modal embedding

Cross-Modal Embedding

Cross-Modal Embedding maps data from different modalities, such as text, images, audio, video or structured objects, into a comparable shared vector space.

Read the fable →

Multimodality

Multimodal

Multimodality

Multimodality means an AI system can process, combine, or generate data from multiple modalities, including text, images, audio, video, and structured signals. In enterprise Agent implementation, multimodal capabilities let the system understand screenshots, scanned contracts, customer voice, operation videos, tables, and logs, rather than relying only on users' text descriptions.

Read the fable →

Multimodality

Vision-language model

Vision-Language Model, VLM

Vision-Language Model, VLM, is a model that can process both visual and language input and use language to explain, answer questions, or make decisions. It can be used for screenshot understanding, parsing scanned documents, on-site fault analysis, product recognition, multimodal RAG, and UI operation Agents.

Read the fable →

NLP / RAG

Entity extraction

Entity Extraction

Entity Extraction is the identification and extraction of entities from unstructured text, image OCR or conversations, such as names, companies, products, amounts, dates, addresses, contract numbers and business objects. It is an important preprocessing step for knowledge base construction, search, risk control, CRM automation and Agent tool invocation.

Read the fable →

NLP / knowledge graph

Relation extraction

Relation Extraction

It identifies entities from text and determines what relationships exist between them, such as employment, acquisition, located-in, causes, belongs-to, treats, supplies, and so on.

Read the fable →

NLP and RAG framework

Haystack

Haystack

Haystack is an open-source framework for search, question answering, RAG, and LLM pipelines, commonly used for retrieval-augmented applications over enterprise documents and knowledge bases.

Read the fable →

Observability

Tool call latency

Tool Call Latency

Tool call latency is the time an Agent waits for an external tool, API, database, browser or service to return a result. Even if the model itself is fast, tool waiting can become the main bottleneck in user experience.

Read the fable →

Observability artifact

Span

Span

A span is a specific operation record within a trace. It usually represents a model call, retrieval, tool call, database query, parsing, approval or intermediate step, and includes start time, end time, duration, inputs and outputs, status, errors and associated context.

Read the fable →

Observability artifact

Tracking records

Trace

A trace records the complete execution path of a request or task from start to finish. For an agent system, a trace usually includes user input, model calls, retrieval steps, tool calls, parameters, returned results, latency, errors, and intermediate states.

Read the fable →

Observability standard

OpenTelemetry

OpenTelemetry, OTel

OpenTelemetry is a vendor-neutral observability standard for collecting traces, metrics, and logs, helping track the full lifecycle of Agent applications.

Read the fable →

Open-source AI observability and evaluation tool

Arize Phoenix

Arize Phoenix

Arize Phoenix is an open-source AI observability and evaluation tool used to trace, evaluate, and analyze the behavior of LLM, RAG, and machine learning applications.

Read the fable →

Open-source LLM observability platform

Langfuse

Langfuse

Langfuse is an open-source LLM observability platform for tracing calls, prompts, generated outputs, scores, costs, and user feedback.

Read the fable →

Open-source vector database

Milvus

Milvus

Milvus is an open-source distributed vector database designed for large-scale vector similarity search. It uses a storage-compute separation architecture and supports multiple index types (HNSW, IVF_FLAT, IVF_PQ, DiskANN, etc.), horizontal scaling, data persistence and hybrid queries.

Read the fable →

Open-source vector database

Qdrant

Qdrant

Qdrant is an open-source vector database and search engine that supports vector similarity search, structured metadata filtering, HNSW indexing and quantization.

Read the fable →

Open-source vector database

Weaviate

Weaviate

Weaviate is an open-source vector database that combines vector search, structured filtering, keyword search (BM25) and schema-based object storage. Its core design philosophy is 'vectorize everything': each data object can simultaneously have a vector, structured attributes and a keyword inverted index, and queries can use a weighted mix of them.

Read the fable →

Operations

Change management

Change Management

Change management is a controlled process for requesting, reviewing, approving, testing, communicating, releasing, and rolling back changes. It doesn't slow down iteration; it gives high-risk changes evidence, an owner, and an exit path.

Read the fable →

Operations

Upgrade path

Escalation Path

The escalation path is a predefined exception reporting and handoff process for handling high-risk, low-confidence, insufficient-permission or compliance-sensitive situations.

Read the fable →

Operations

Exception handling

Exception Handling

Exception Handling is the mechanism by which a system identifies, routes, records, recovers from, and escalates situations when it cannot continue normally, when inputs are abnormal, tools fail, permissions are insufficient, confidence is low, or risk rises.

Read the fable →

Operations

Hot reload

Hot Reload

Hot Reload is the ability to update configurations, prompts, tools, routing, policies, or model versions without interrupting or with minimal interruption to service. For LLM/Agent systems, it can increase iteration speed, but it requires version management, validation, canary rollout, rollback, state consistency, and audit records to avoid configuration drift or half-updated states during runtime.

Read the fable →

Operations

Human-in-the-loop oversight

Human-on-the-Loop, HOTL

Human-on-the-Loop is an operating mode in which AI or an Agent can execute tasks automatically, but a human monitors alongside and can intervene, pause, override, or take over when there is an anomaly, rising risk, or a result that does not meet expectations.

Read the fable →

Operations

Post-mortem review

Postmortem

A postmortem is a structured review after an incident, outage, or major failure, used to reconstruct the timeline, analyze root causes, assess impact, and define remediation actions and recurrence prevention. A good postmortem emphasizes system improvement rather than simple blame, and must ultimately produce actionable items, owners, and verification methods.

Read the fable →

Operations

Quality assurance

Quality Assurance, QA

Quality Assurance, QA is about establishing quality standards, testing processes, sampling reviews, defect grading and regression checks in AI application and Agent delivery to ensure outputs meet business requirements. It covers knowledge accuracy, process completion, tool invocation, format, compliance, safety and user experience.

Read the fable →

Operations

Rollback

Rollback

Rollback is a mechanism for quickly restoring a previous stable state when a new version, model, prompt, tool, configuration or process runs into problems. It is not a temporary fix after failure, but part of release and change design.

Read the fable →

Operations

Rollback plan

Rollback Plan

A Rollback Plan is a recovery plan defined in advance before a change goes live, including trigger conditions, owners, recovery steps, time limits, verification methods and communication methods. It is more complete than a simple rollback action, emphasizing when to roll back, who decides, how to execute, and how to confirm successful recovery.

Read the fable →

Operations

Root cause analysis

Root Cause Analysis, RCA

Root Cause Analysis (RCA) is an analytical method for finding the true cause behind a problem, rather than only treating surface symptoms. It is often used in postmortems of incidents, quality issues, system failures, and business anomalies.

Read the fable →

Operations / finance

Cloud cost operations

FinOps

FinOps is a practice framework spanning engineering, finance and business teams for managing cloud resources, model calls, budgets, attribution and cost optimization.

Read the fable →

Operations / infrastructure

Autoscaling

Autoscaling

Autoscaling dynamically adjusts the number of resources based on load, queue length, CPU, GPU or request metrics to balance cost and performance.

Read the fable →

Operations / platform

Large language model operations

LLMOps

LLMOps is an operations system for large language model applications, focused on managing prompts, retrieval, evaluation, security, cost, latency, and model versions.

Read the fable →

Operations / platform

Machine Learning Operations

MLOps

MLOps is the engineering system that moves machine learning models from experiments to stable production, covering data, training, deployment, monitoring, and governance. It emphasizes data and feature management, experiment tracking, model registry, CI/CD, release approval, performance monitoring, drift detection, and rollback.

Read the fable →

Operations / reliability

Dead letter queue

Dead-Letter Queue, DLQ

The dead letter queue stores messages and tasks that still fail after multiple retries or fail validation. It isolates problematic tasks to avoid blocking the normal main flow.

Read the fable →

Operations / reliability

Disaster recovery

Disaster Recovery, DR

Disaster recovery is a set of architectures, backups, plans, drills, and operational procedures used to restore critical systems and data after a major failure.

Read the fable →

Operations / reliability

Observability

Observability

Observability is the ability to understand a system's internal state through logs, metrics, traces, and events. For Agent systems, observability is not just knowing whether a task succeeded or failed, but being able to review model calls, retrieval, tool calls, parameters, latency, errors, cost, and intermediate outputs.

Read the fable →

Operations / reliability

Recovery point objective

Recovery Point Objective, RPO

Recovery point objective defines the maximum acceptable data loss time for a system, and is used to determine the frequency of backup, replication, and recovery strategies.

Read the fable →

Operations / reliability

Recovery time objective

Recovery Time Objective, RTO

Recovery Time Objective (RTO) is the longest acceptable recovery time for a service or business capability after a failure occurs. It answers: how long can it be down at most.

Read the fable →

Operations / security

Incident response

Incident Response

Incident Response is the complete set of handling procedures when a system failure, security incident, quality accident, or business risk occurs, including detection, triage, containment, isolation, recovery, communication, forensics, and retrospective review.

Read the fable →

Operations/Audit

Sampling review

Sampling Review

Sampling Review is when full manual review of all AI outputs or agent tasks is not possible, samples are drawn for manual inspection by risk, scenario, customer, amount, historical issues and randomness.

Read the fable →

Operations/Auditability

Version control

Version Control

Version control records changes to prompts, models, datasets, tools, policies, code and configuration, making historical states auditable, rollback-ready and reproducible.

Read the fable →

Operations/Governance

Approval threshold

Approval Gate

An Approval Gate is a control point in a workflow that requires human approval, policy validation or permission confirmation before proceeding. It is typically used for high-risk, high-value, irreversible, externally committed, privacy-sensitive or compliance-related actions.

Read the fable →

Operations/Governance

Change Advisory Board

Change Advisory Board, CAB

A change advisory board is a cross-functional review mechanism used to assess the risk, readiness, compliance impact and operational impact of major changes.

Read the fable →

Operations/Risk

AI incidents

AI Incident

An AI incident is an event in which an AI system caused or nearly caused harm, violation, a safety problem, a data leak, or major operational disruption.

Read the fable →

Operations/Risk

Business continuity

Business Continuity

Business continuity focuses on whether key business commitments can still be fulfilled when an interruption occurs. Disaster recovery is more about restoring technical systems; business continuity is more concerned with whether there are alternatives for order taking, fulfillment, collection, customer service, compliance notifications, and other capabilities.

Read the fable →

Operations/Risk

Confidence threshold

Confidence Threshold

A confidence threshold is a preset confidence or risk threshold used to decide whether AI output automatically passes, is reviewed, rejected, downgraded, or escalated.

Read the fable →

Operations/Risk

Fact-checking

Fact Verification

Fact verification is the process of checking AI-generated claims, conclusions or key facts against trusted sources, original evidence, authoritative systems or business records. It is used to reduce the risk of hallucinations, outdated information, misreadings and the spread of errors.

Read the fable →

Operations/Security

Incident Management

Incident Management

Incident management covers discovery, classification, containment, investigation, communication, and remediation processes, used to handle AI, security, privacy, or operational incidents.

Read the fable →

Orchestration

Directed acyclic graph

Directed Acyclic Graph, DAG

Directed Acyclic Graph (DAG) is a graph structure composed of nodes and directed edges with no cycles, commonly used to represent dependencies in tasks, data pipelines, or workflows.

Read the fable →

Orchestration

Intent recognition

Intent Classification

Intent Classification is the ability to determine which category a user request belongs to, in order to decide the subsequent process, tools, Agent, or response strategy. It can be done by rules, traditional classifiers, or an LLM.

Read the fable →

Orchestration

Semantic routing

Semantic Routing

Semantic Routing distributes requests to the appropriate model, tool, Agent, knowledge base or workflow based on the request's meaning, intent, context and task type. Unlike simple keyword matching, it focuses more on what the user truly wants to accomplish.

Read the fable →

Orchestration component

Router

Router

A Router is a component that dispatches requests, tasks or intermediate steps to the appropriate model, tool, workflow, skill or Agent. It can make decisions based on intent, capability, cost, latency, risk, permissions, load and policy.

Read the fable →

PEFT

Adapter

Adapter

Adapter is a parameter-efficient fine-tuning method that typically inserts small trainable modules between model layers while freezing most of the base model's weights. It allows the same base model to adapt to different tasks, domains, or customers through different adapters.

Read the fable →

PEFT

IA3

Infused Adapter by Inhibiting and Amplifying Inner Activations

IA3 is an extremely efficient parameter fine-tuning method. By learning vectors that scale keys, values, and feed-forward activations, it usually requires fewer parameters than LoRA.

Read the fable →

PEFT

Merge weights

Merge Weights / Merge Adapters

Merging weights means folding the incremental weights trained by PEFT methods such as LoRA or Adapter into the base model weights, to facilitate deployment and reduce runtime dependencies.

Read the fable →

PEFT

Prefix Fine-Tuning

Prefix Tuning

Prefix Tuning is a PEFT method that freezes the base model parameters and trains only a set of learnable continuous prefix vectors, using them as additional context for attention at each layer to influence the output.

Read the fable →

PEFT

Prompt fine-tuning

Prompt Tuning

Prompt Tuning is a PEFT method that typically freezes model parameters and learns only a small set of continuous soft prompt vectors, prepending them to the input to steer the model toward a specific task.

Read the fable →

PEFT

Quantized low-rank adaptation

Quantized LoRA, QLoRA

QLoRA quantizes the base model to 4 bit and trains only the LoRA adapters, enabling fine-tuning of large models on devices with lower VRAM.

Read the fable →

PEFT

Target module selection

Target Module Selection

Target module selection is the process of deciding which model modules to insert, train, or adjust among methods such as LoRA, Adapter, or IA3.

Read the fable →

Platform / backend infrastructure

Workflow engine

Workflow Engine

The workflow engine is responsible for persisting, scheduling, executing and recovering multi-step tasks. It records the state of each step, inputs and outputs, dependencies, failure reasons, retry rules, human approvals and next-step routing.

Read the fable →

Platform / billing

Quota

Quota

Quota defines the upper limit of resources a user, tenant, or plan can use within a certain period, such as tokens, request counts, storage, or concurrency. For LLM/Agent platforms, quota is used to protect shared models, GPUs, tool executors, retrieval services, and budgets, preventing a single tenant or abnormal task from exhausting resources.

Read the fable →

Platform / integration

Connector

Connector

A Connector is an adapter component that connects an AI system to external applications, databases, files, SaaS, or enterprise systems. It handles API calls, authentication and authorization, permission boundaries, parameter transformation, error handling, rate limiting, and auditing, enabling Agents to use external capabilities reliably rather than relying on one-off glue code.

Read the fable →

Platform / reliability

Durable execution

Durable Execution

Durable execution is an execution approach that lets long-running tasks continue or recover after process crashes, machine restarts, network interruptions, timeouts, or personnel handovers. By persisting events, state, inputs and outputs, and checkpoints, it prevents tasks from existing only in memory or within a single session.

Read the fable →

Platform architecture

Cloud native

Cloud Native

Cloud native is an approach to designing, building, and running applications for cloud environments, emphasizing containerization, microservices, elastic scaling, automated deployment, observability, and fault isolation.

Read the fable →

Platform engineering

Internal developer platform

Internal Developer Platform, IDP

An internal developer platform provides engineering teams with a standardized self-service entry point for creating, deploying, monitoring, and operating applications, typically including a service catalog, templates, permissions, environments, and CI/CD capabilities.

Read the fable →

Platform engineering / governance

Golden path

Golden Path, Paved Road

Golden Path / Paved Road refers to the recommended processes, templates, and default configurations that platform teams provide for common development, deployment, and operations scenarios. It lets teams complete compliant, reliable delivery with fewer decisions, while allowing controlled exceptions for special cases.

Read the fable →

Policy

AI policy

AI Policy

AI Policy is the formal set of rules an organization has for AI use, procurement, deployment and governance, specifying permitted and prohibited uses, data processing boundaries, approval processes, oversight requirements, disclosure obligations, log auditing and consequences of violations.

Read the fable →

Policy

Acceptable Use Policy

Acceptable Use Policy, AUP

An acceptable use policy defines the permitted and prohibited uses of an AI or Agent product, constraining risks such as fraud, harm, illegality, and privacy infringement.

Read the fable →

PostgreSQL vector extension

pgvector

pgvector

pgvector is a PostgreSQL extension that adds vector storage, similarity search, and metadata filtering to relational databases, and is often used in lightweight RAG systems.

Read the fable →

Preprocessing

BPE

Byte-Pair Encoding

BPE is a subword tokenization method that repeatedly merges the most common adjacent symbol pairs in a corpus to form a fixed vocabulary.

Read the fable →

Preprocessing

SentencePiece

SentencePiece

SentencePiece is a commonly used subword tokenization tool and algorithm framework. Its distinguishing feature is that it treats input as a raw character sequence and does not rely heavily on whitespace tokenization, making it suitable for multilingual and mixed text.

Read the fable →

Pretraining

Corpus

Corpus

A corpus is a set of data materials collected, organized, and used for training, retrieval, evaluation, or analysis. It can be text, images, audio, code, tables, or conversation records.

Read the fable →

Pretraining

Foundation model

Foundation Model

A Foundation Model is a large model trained on broad data that can be transferred to many downstream tasks. It is the capability foundation of an enterprise Agent, but not a complete product; actual delivery still requires data access, tools, permissions, evaluation, cost control, and business processes.

Read the fable →

Pretraining

Pretraining

Pretraining

Pre-training is the large-scale initial training phase of a model, typically learning language, knowledge and general patterns from massive corpora through self-supervised objectives. It gives the model its foundation, but it does not automatically understand a given company's processes, boundaries and tools.

Read the fable →

Pretraining

Self-supervised learning

Self-Supervised Learning

Self-supervised learning is a way of learning that constructs supervisory signals from the data itself, such as predicting the next token, filling in masked words, or judging the relationship between segments. It does not require every piece of data to have a manually labeled answer.

Read the fable →

Privacy

Anonymization

Anonymization

Anonymization is processing personal data to a state where specific individuals cannot be identified, and re-identification is difficult under reasonably available information and means.

Read the fable →

Privacy

Data Minimization

Data Minimization

It requires collecting, processing, accessing and retaining only the data necessary to fulfill a clearly defined purpose, not taking more just because it "might be useful later."

Read the fable →

Privacy

Data protection impact assessment

Data Protection Impact Assessment, DPIA

A DPIA is an impact assessment conducted before processing personal data, especially high-risk activities, to identify privacy risks, controls, and compliance basis.

Read the fable →

Privacy

Data retention policy

Data Retention Policy

It specifies how long different types of data should be retained, whether data is deleted, archived, anonymized, or kept after expiry, and who approves exceptions.

Read the fable →

Privacy

Differential privacy

Differential Privacy

Differential privacy adds designed mathematical noise to limit the influence of any single sample on statistical results. The goal is to make it hard for outsiders to determine from the output whether a particular person's data was included in the computation.

Read the fable →

Privacy

Membership inference attack

Membership Inference Attack

A membership inference attack is when an attacker repeatedly queries a model and observes confidence or output characteristics to determine whether a piece of data appeared in the training set. What it leaks is not the full text of the data, but the fact of whether a certain person or record was used.

Read the fable →

Privacy

Model inversion attack

Model Inversion Attack

Attackers observe model outputs, probability scores, similarity, confidence, or repeated queries to infer sensitive features in the training data, and even reconstruct part of the original data.

Read the fable →

Privacy

Personal data

Personal Data

Personal data refers to information related to an identified or identifiable natural person. As long as it can directly or indirectly point to a specific person, it may constitute personal data.

Read the fable →

Privacy

Personally identifiable information

Personally Identifiable Information, PII

PII. It is information that can directly or indirectly identify a specific individual, such as name, ID number, mobile number, email, photo and address, and also includes clues that can identify an individual when combined with other information.

Read the fable →

Privacy

Pseudonymization

Pseudonymization

Pseudonymization replaces direct identifiers such as names and mobile numbers with codes or pseudonyms, and stores the mapping information that could re-identify individuals separately. It reduces exposure risk, but it is not anonymization.

Read the fable →

Privacy

Purpose limitation

Purpose Limitation

Purpose limitation is a privacy protection principle: personal data should be collected for explicit, specific purposes and must not later be repurposed for incompatible uses without justification.

Read the fable →

Privacy

Secure aggregation

Secure Aggregation

Secure aggregation is often used in scenarios such as federated learning: the server only obtains the sum of the updates from multiple parties, without seeing any single party's plaintext update. It allows everyone to train or compute statistics together while reducing the risk of data leakage for any individual participant.

Read the fable →

Privacy

Sensitive personal data

Sensitive Personal Data

It is a category of personal data with higher harm risk, such as health, financial, biometric, precise location, minors' information, race and religion, political views, sexual orientation, or data that may lead to discrimination and major harm to rights and interests.

Read the fable →

Privacy/Compliance

Cross-border data transfer

Cross-Border Data Transfer

It refers to personal data, business data, or other regulated data flowing from one country or region to another, or being remotely accessed, processed, stored, or backed up by overseas entities.

Read the fable →

Privacy/Compliance

Data localization

Data Localization

Data localization means laws, policies, or contracts require certain types of data to remain within a specific country, region, or regulatory boundary, and cannot be freely transmitted, processed, or stored across borders.

Read the fable →

Privacy/Compliance

Data residency

Data Residency

It requires that certain data must be stored, processed, replicated, backed up or recovered within a specified country, region, cloud zone, data center or customer-controlled environment.

Read the fable →

Procurement

Supplier evaluation

Vendor Evaluation

Vendor Evaluation is the process by which procurement and risk teams assess an AI vendor's capabilities, security, compliance, economics, support capability, and operational fit.

Read the fable →

Procurement/Architecture

Vendor Lock-In

Vendor Lock-In

Vendor lock-in is the dependency risk in which proprietary APIs, data formats, workflows, contract terms, or model behavior make switching vendors too costly.

Read the fable →

Procurement/Privacy

Data processing agreement

Data Processing Agreement, DPA

A Data Processing Agreement (DPA) is a contract stipulating how a vendor or processor handles personal data on behalf of a customer.

Read the fable →

Procurement/Privacy

Data usage rights

Data Usage Rights

Data usage rights define whether and how a vendor may use customer data, often covering service delivery, statistical analysis, product improvement, training, and fine-tuning.

Read the fable →

Procurement/Privacy

Sub-processor

Subprocessor

Sub-processors are third parties engaged by the processor to deliver the service, and may include cloud providers, model APIs, vector databases, and logging platforms.

Read the fable →

Procurement/Privacy

Training data exclusion

Training Data Exclusion

Training data exclusion is a contractual or technical commitment stating that customer data may not be used to train, fine-tune or improve the vendor's models without permission.

Read the fable →

Procurement/Risk

Exit plan

Exit Plan

An Exit Plan is a plan to safely terminate or replace a vendor, with the goal of completing the migration while preserving data access, service continuity, compliance evidence and operational control.

Read the fable →

Procurement/Risk

Third-party risk management

Third-Party Risk Management, TPRM

Third-Party Risk Management (TPRM) is the lifecycle discipline of onboarding assessment, contractual constraints, continuous monitoring, incident handling, and exit management for vendors, outsourced parties, and partners.

Read the fable →

Procurement/Risk

Supplier due diligence

Vendor Due Diligence

Supplier due diligence is a structured review of a supplier's security, privacy, compliance, financial stability, service reliability, and operational capability.

Read the fable →

Procurement/Security

Security questionnaire

Security Questionnaire

A Security Questionnaire is a structured questionnaire used by buyers to assess a supplier's security controls, compliance status, data handling, and incident practices. It often covers identity and permissions, encryption, logging, vulnerability management, penetration testing, compliance certifications, subprocessors, data retention, backup, business continuity, and incident response.

Read the fable →

Product / business strategy

Product-market fit

Product-Market Fit, PMF

Product-market fit (PMF) is the state in which a product solves a strong need for a clearly defined customer group and shows signals such as retention, repeat purchase, referrals, willingness to pay, and revenue growth. It is not people praising the product, and it is not one successful demo.

Read the fable →

Product / customer success

Time to value

Time to Value, TTV

Time to Value (TTV) refers to the time it takes for a customer to gain perceivable business value from starting to use a product. The shorter the TTV, the better for trial conversion, customer confidence, adoption and retention.

Read the fable →

Product / platform

Self-service

Self-Service

Self-Service lets users or internal teams complete registration, configuration, deployment, queries, upgrades, troubleshooting, and other operations without manual intervention. It lowers marginal service costs, speeds up onboarding, and makes PLG and scaled delivery possible.

Read the fable →

Product / research

User profile

Persona, User Persona

Persona / User Persona is an abstract description of a typical user's goals, tasks, pain points, environment, and behavioral patterns.

Read the fable →

Product / sales

Proof of concept

Proof of Concept, POC

A Proof of Concept (POC) is a project that validates technical feasibility, business value or purchasing confidence within a limited scope. A high-quality POC must have clear assumptions, scope, success criteria, a time box, data conditions, assigned responsibilities and a next-step decision.

Read the fable →

Product engineering / release management

Feature flag

Feature Flag, Feature Toggle

Feature flags control whether a capability is enabled without redeploying code. They can be rolled out gradually by user, tenant, region, task type, model, tool, policy, or risk level.

Read the fable →

Product experience / customer success

Onboarding

Onboarding

Onboarding is the process of helping new users or customers complete account setup, data import, first tasks, permission settings, team collaboration and value confirmation. Good onboarding is not just a tutorial; it brings users to activation and their first business result.

Read the fable →

Product growth

Activate

Activation

Activation is the process or key action through which a new user first experiences the core value of a product, often designed as an activation metric. It is different from registration, login or watching a tutorial; true activation must get the user to complete an action that represents the product’s value.

Read the fable →

Product strategy

Minimum viable product

Minimum Viable Product, MVP

Minimum Viable Product (MVP) is an early product that uses the minimum necessary scope to validate core user needs, value propositions or business assumptions.

Read the fable →

Product strategy / research

Tasks to be completed

Jobs to Be Done, JTBD

Jobs to Be Done (JTBD) focuses on the progress a user wants to make in a specific situation, rather than understanding needs only by identity, industry or feature preference.

Read the fable →

Product strategy / workflow design

AI-native workflow

AI-Native Workflow

AI-native workflows redesign work processes around AI's abilities to understand, generate, call tools, remember, evaluate, and involve humans.

Read the fable →

Prompt optimization tool

Prompt optimizer

Teleprompter

In DSPy, Teleprompter refers to an optimizer used to optimize prompts, demonstrations or program settings. Based on training samples, evaluation metrics and module structure, it searches for more effective few-shot examples, instructions or reasoning strategies.

Read the fable →

Prompt/function abstraction

Semantic function

Semantic Function

A Semantic Function is an abstraction that wraps a prompt or natural-language instruction into a callable unit, commonly seen in Semantic Kernel. Like a function, it has a name, inputs and outputs, and can be combined with native functions, plugins and planners.

Read the fable →

Quality assurance

Evaluation framework

Evaluation Harness

An Evaluation Harness is a repeatable testing environment and set of test cases used to assess a model or Agent's performance across different tasks, boundary conditions, tool calls, latency, quality, and failure scenarios.

Read the fable →

Quantization

Double quantization

Double Quantization

Double Quantization is a quantization technique in QLoRA: after model weights are quantized, constants such as quantization scales still need to be stored; double quantization further quantizes these quantization constants, saving additional GPU memory—about 0.4 bit/parameter in the paper.

Read the fable →

Quantization

NF4

NormalFloat 4-bit

NF4 is a 4-bit data type introduced by QLoRA, designed for approximately normally distributed weights, used to quantize large models more efficiently.

Read the fable →

RAG

Multimodal RAG

Multimodal RAG

Multimodal RAG incorporates multiple modalities such as text, images, tables, drawings, audio, and video into retrieval-augmented generation, enabling the model to cite different types of evidence when answering. In enterprise scenarios, a large amount of knowledge exists in scanned documents, product images, ticket screenshots, contract tables, recordings, and videos.

Read the fable →

RAG / search

Reranker

Reranker

A reranker is a model or component that rescores and reorders candidate documents or chunks after initial retrieval.

Read the fable →

RAG evaluation

Answer Relevance

Answer Relevance

Answer Relevance measures whether a model's answer truly responds to the user's question and task goal. An answer can be fluent, truthful and informative yet still irrelevant, because it does not address what the user actually asked.

Read the fable →

RAG evaluation

Context precision

Context Precision

Context Precision measures how much of the context retrieved or provided to the model is truly relevant to the question in the earlier positions. It focuses not only on whether the answer was retrieved, but also on whether relevant material is ranked near the front and whether there is too much irrelevant noise.

Read the fable →

RAG evaluation

Context recall

Context Recall

Context Recall measures whether the key evidence needed to answer a question is retrieved and placed into context. It focuses on whether necessary information has been missed.

Read the fable →

RAG evaluation

Faithfulness

Faithfulness

Faithfulness measures whether a model's answer stays true to the given evidence or context. An answer may be fluent, logical, and even broadly correct in direction, but if it adds content not supported by the evidence, rewrites factual relationships or exaggerates conclusions, it is not faithful enough.

Read the fable →

RAG evaluation

Retrieval precision

Retrieval Precision

Retrieval Precision measures the proportion of truly relevant results among those returned by retrieval. In RAG, it answers the question: of the chunks that enter the model's context, how many actually support the current question.

Read the fable →

RAG evaluation

Retrieval recall

Retrieval Recall

Retrieval Recall measures the proportion of all relevant results that the system successfully retrieves. In RAG, it answers: was the key evidence recalled? Low recall causes the model to answer based on incomplete context, which is especially dangerous in compliance, contracts, after-sales, and medical scenarios.

Read the fable →

Reasoning

Graph of Thoughts

Graph of Thoughts

A thought graph organizes intermediate ideas with a graph structure, letting reasoning nodes branch, merge, backtrack, and be reused—well suited to compositional reasoning tasks.

Read the fable →

Reasoning

Self-consistency

Self-Consistency

Self-Consistency is a method that samples multiple reasoning paths for the same question, then selects the final answer through voting or consistency. It is often used together with Chain-of-Thought to improve the stability of complex reasoning.

Read the fable →

Reasoning

Tree of Thoughts

Tree of Thoughts

Tree of Thoughts is a method that expands model reasoning into multiple candidate paths and performs search, evaluation, pruning, and selection among branches. It is suitable for tasks such as planning, puzzles, and strategic decision-making that require exploring multiple possible solutions. The cost is higher inference expense and the need to design branch generation, evaluation functions, stopping conditions, and search budgets.

Read the fable →

Reasoning / tool use

Program-aided language model

Program-Aided Language Model, PAL

Program-Aided Language Model, PAL, is a method that has the model generate programs or executable code, and then solves math, logic, data processing, and other problems by executing the program. The model is responsible for converting natural language problems into programs, and the executor is responsible for precise computation.

Read the fable →

Reasoning/action pattern

Reasoning-Action Paradigm

ReAct

ReAct is a prompting and Agent pattern that alternates reasoning and action. The model first performs short-step reasoning, selects a tool or action, observes the result, then continues to the next round. It suits tasks that require external information, tool calls and step-by-step decision-making.

Read the fable →

Regulation

EU AI Act

EU AI Act

The EU AI Act is the EU's legal framework for regulating AI by risk level, setting requirements for high-risk systems, general-purpose AI, and transparent disclosure.

Read the fable →

Regulation

General-purpose AI

General-Purpose AI, GPAI

General-purpose AI refers to general AI models or systems that can adapt to multiple downstream uses and can serve as the foundational capability for multiple products and Agents.

Read the fable →

Regulation

High-risk AI systems

High-Risk AI System

High-risk AI systems are systems that bear stricter obligations under regulatory frameworks because their use affects safety, fundamental rights, or important opportunities.

Read the fable →

Regulation/Compliance

Conformity assessment

Conformity Assessment

Conformity assessment is the procedure that verifies whether a regulated AI system meets applicable legal and standard requirements before it is placed on the market or put into use.

Read the fable →

Reliability / AI platform

Rollback

Fallback

Fallback is the backup path enabled when the preferred model, tool, service or process fails, slows down, becomes unavailable or is too risky.

Read the fable →

Reliability / architecture

Circuit breaker

Circuit Breaker

A circuit breaker temporarily stops calls when a dependency keeps failing or latency is too high, avoiding cascading failures and gradually probing during the recovery period.

Read the fable →

Reliability / operations

Error budget

Error Budget

An error budget is the amount of unreliability that can be consumed within the range allowed by the SLO, used to balance release speed, experiment frequency, and system stability.

Read the fable →

Reliability / operations

Service Level Objective

Service Level Objective, SLO

A service level objective is a measurable commitment to service reliability, such as availability, latency, error rate, or task completion rate.

Read the fable →

Reliability / product experience

Degradation

Graceful Degradation

Graceful degradation means that when capacity, dependencies, models, tools, or data sources are abnormal, the system still provides reduced but useful service rather than failing entirely.

Read the fable →

Reliability pattern

Model fallback

Model Fallback

Model fallback is a reliability pattern that routes requests to a backup model or provider when the primary model fails, times out, exceeds budget or violates policy.

Read the fable →

Reliability technique

Fact Anchoring

Grounding

Grounding anchors model outputs and decisions to given evidence, tool results, source documents, or verified system states, rather than relying on model guesses. In enterprise Agents, grounding is a key mechanism for reducing hallucinations, supporting audits, generating citations, and building user trust.

Read the fable →

Representation learning

Embed

Embeddings

Embeddings are a representation method that converts text, images, audio, code, entities, or business objects into dense numeric vectors. Embedding and Embeddings describe the same core mechanism; the plural form emphasizes assetization in enterprise systems: large numbers of objects are continuously encoded, stored, retrieved, updated, and evaluated.

Read the fable →

Reranking

Cross-encoder

Cross-Encoder

A Cross-Encoder feeds the query and candidate text together into the same model, letting the model judge relevance in joint context. It is usually more precise than encoding queries and documents separately, and is suitable for RAG reranking, search result fine ranking, QA evidence selection, and compliance material matching.

Read the fable →

Retrieval

BM25

BM25

BM25 is a classic keyword retrieval ranking algorithm, commonly used in search engines and sparse retrieval for RAG. It judges document-query relevance based on term frequency, inverse document frequency and document length normalization. BM25 excels at literal matching problems such as proper nouns, numbers, exact terminology and regulatory clauses.

Read the fable →

Retrieval

Dual encoder

Bi-Encoder

A Bi-Encoder encodes queries and documents separately, converts both into vectors, and matches them by similarity. Because document vectors can be precomputed offline and stored in a vector database, it is well suited for large-scale semantic retrieval, first-stage recall in RAG, similar case search, and recommendation.

Read the fable →

Retrieval

Hypothetical document embeddings

Hypothetical Document Embeddings, HyDE

HyDE first generates a hypothetical answer or document, then embeds it for retrieval, to improve recall for short or ambiguous queries.

Read the fable →

Retrieval

Maximum Marginal Relevance

Maximal Marginal Relevance, MMR

Maximal Marginal Relevance, MMR is a method for selecting retrieval results that balances relevance and diversity. It prioritizes documents that are both relevant to the query and not too repetitive with already-selected results.

Read the fable →

Retrieval

Multi-hop retrieval

Multi-Hop Retrieval

Multi-hop retrieval performs multiple retrieval steps to answer complex questions, first finding evidence fragments, then continuing to retrieve based on entities, relations or intermediate conclusions.

Read the fable →

Retrieval

Query rewriting

Query Rewriting

Query Rewriting is the process of rewriting a user's original question into a form better suited to retrieval, database queries or tool calls. It can fill in references, standardize terminology, split complex questions, generate multiple query paths and improve RAG recall quality.

Read the fable →

Retrieval

Recursive retrieval

Recursive Retrieval

Recursive Retrieval is a retrieval method in RAG or knowledge retrieval that continues generating follow-up queries, tracking new entities, or filling in missing evidence based on already retrieved content. It is suitable for multi-hop questions, complex fact-checking, and long-chain business analysis.

Read the fable →

Retrieval infrastructure

Approximate nearest neighbor search

Approximate Nearest Neighbor Search (ANN Search)

Approximate nearest neighbor search finds sufficiently similar vectors within limited time and compute resources, and is a foundational technique for large-scale vector retrieval.

Read the fable →

Retrieval infrastructure abstraction

Document storage

Document Store

A Document Store is a storage abstraction in RAG, search, and question-answering pipelines that holds text, metadata, embedding vectors, and index information. It can be implemented by Elasticsearch, OpenSearch, a vector database, a relational database, or a framework's built-in storage.

Read the fable →

Retrieval infrastructure ecosystem

Vector database ecosystem

Vector Database Ecosystem

The vector database ecosystem includes databases and retrieval libraries such as Pinecone, Milvus, Qdrant and FAISS, used to store, index and query vectors.

Read the fable →

Retrieval method

Dense retrieval

Dense Retrieval

Dense Retrieval uses neural network embeddings to encode queries and documents into low-dimensional dense vectors, then finds semantically close content through vector similarity. It can handle synonyms, paraphrases, cross-language cases, and implicit intent, and is one of the core retrieval methods in modern RAG.

Read the fable →

Retrieval method

Hybrid search

Hybrid Search

Hybrid Search is a retrieval method that combines keyword/sparse retrieval (such as BM25) with vector/semantic retrieval. Keyword retrieval is good at exact matching of proper nouns, numbers, codes, and regulatory clauses; vector retrieval is good at finding content that differs literally but is similar in meaning.

Read the fable →

Retrieval method

Semantic search

Semantic Search

Semantic Search retrieves results based on meaning rather than exact keyword matching. It embeds both queries and documents into the same vector space, and finds the semantically closest content by calculating vector distance. Compared with traditional keyword search, semantic search can handle synonyms, near-synonymous expressions, cross-language, and fuzzy descriptions, with more complete recall.

Read the fable →

Retrieval method

Sparse retrieval

Sparse Retrieval

Sparse retrieval represents queries and documents with high-dimensional sparse features, typically including BM25, inverted indexes, and learned sparse representations such as SPLADE. Its advantage is precisely hitting keywords, rare words, numbers, proper nouns, error codes and clauses.

Read the fable →

Retrieval preparation

Chunking

Chunking

Chunking is the process of cutting long documents into small passages suitable for retrieval and for placing into the model context. RAG systems usually cannot directly stuff an entire document into the model; instead, they first chunk, vectorize, and index the document, then recall relevant chunks based on the question. Chunking quality directly affects recall precision, context completeness, citation accuracy, and answer quality.

Read the fable →

Retrieval preparation

Parent-child chunking

Parent-Child Chunking

Parent-child chunking uses smaller child chunks for vector retrieval, then returns larger parent chunks as context, balancing hit precision and semantic completeness.

Read the fable →

Retrieval preparation

Semantic chunking

Semantic Chunking

Semantic Chunking splits documents according to semantic boundaries, rather than mechanically by fixed character count, token count, or line count. It tries to make each chunk a relatively complete unit of meaning, such as a rule, a step, a definition, a set of exceptions, or a case.

Read the fable →

Retrieval preparation

Sliding Window Chunking

Sliding Window Chunking

Sliding Window Chunking splits long documents using fixed-size windows and preserves a certain overlap between adjacent chunks. Its goal is to reduce the risk of semantics or facts being cut off right at chunk boundaries.

Read the fable →

Retrieval quality

Reranking

Reranking

Reranking is the step after first-stage retrieval that rescores and reorders candidate documents, chunks, or search results. It usually combines the query and candidate content for a finer-grained relevance judgment, often performed by a cross-encoder, an LLM, or a dedicated reranking model.

Read the fable →

Retrieval/application abstraction

Query engine

Query Engine

Query Engine is an application abstraction in frameworks such as LlamaIndex: it receives user queries, calls retrievers or indexes to retrieve relevant data, and synthesizes the final answer through an LLM or other strategy.

Read the fable →

Risk Management

AI risk management

AI Risk Management

AI Risk Management is the systematic process of identifying, measuring, prioritizing, mitigating, monitoring and reporting risks across the full lifecycle of an AI system.

Read the fable →

Risk Management

AI risk management framework

AI Risk Management Framework, AI RMF

The AI RMF is a structured framework for governing AI risk, usually organized around govern, map, measure, and manage to identify and control risk.

Read the fable →

Risk Management

Hallucination risk

Hallucination Risk

Hallucination Risk is the risk that generative AI produces false, unsupported or fabricated content that users treat as fact.

Read the fable →

Risk Management

Residual risk

Residual Risk

Residual Risk refers to the risk that remains after controls, mitigations, and monitoring measures are implemented. In enterprise Agent governance, permission limits, approval flows, logs, evaluations, and guardrails reduce risk, but they do not bring risk to zero.

Read the fable →

Risk Management

Risk acceptance

Risk Acceptance

Risk Acceptance is a governance action in which an authorized responsible person formally decides to accept a known residual risk. It usually requires stating the risk content, business rationale, scope, duration, compensating controls, monitoring metrics and escalation conditions.

Read the fable →

Risk Management

Risk appetite

Risk Appetite

Risk Appetite is the types and level of risk an organization is willing to accept in order to achieve its business objectives. It provides the upper-level boundary for an Agent's permissions, automation scope, approval thresholds, testing intensity and monitoring requirements.

Read the fable →

Risk Management

Risk assessment

Risk Assessment

Risk assessment identifies, analyzes, and grades the potential risks of an AI use case or system, judging harm, compliance obligations, likelihood, severity, and controls.

Read the fable →

Risk Management

Risk owner

Risk Owner

A Risk Owner is the person or function with management responsibility for a specific risk, responsible for ensuring the risk is identified, assessed, mitigated, monitored, and kept within approved thresholds. It differs from a Control Owner: the control owner is responsible for a control's operation, while the risk owner is responsible for the overall treatment and accountability of that risk.

Read the fable →

Risk Management

Risk Register

Risk Register

The risk register continuously records identified risks, owners, likelihood, impact, mitigation measures, residual risk, acceptance status, and review cycle.

Read the fable →

SaaS / platform architecture

Multi-tenant

Multi-Tenancy

Multi-tenancy is letting multiple customers or organizations share the same platform while isolating data, permissions, configuration, usage, billing, and operational controls. Its core is not simply sharing servers, but having sharing and isolation hold true at the same time.

Read the fable →

SaaS / security architecture

Tenant isolation

Tenant Isolation

Tenant isolation ensures that one customer's data, configuration, permissions, context, tools, logs, and resources cannot be accessed or affected by other customers.

Read the fable →

Safety and Alignment

Safety guardrails

Guardrails

Security guardrails are a set of security and governance controls around AI/Agents, used to restrict inputs, outputs, tool calls, permissions, and high-risk actions.

Read the fable →

Sales AI / Revenue operations

Sales Agent

Sales Agent, AI Sales Agent, Sales Copilot

A sales agent is an AI execution system for sales and revenue operations, covering customer research, lead scoring, personalized outreach, and meeting preparation.

Read the fable →

Security

AI safety

AI Security

AI Security is the practice of protecting AI/Agent systems from prompt injection, data leakage, model misuse, tool overreach, training/retrieval data poisoning, supply chain risks, credential leakage and adversarial attacks.

Read the fable →

Security

Attribute-based access control

Attribute-Based Access Control, ABAC

Attribute-Based Access Control (ABAC) doesn't look only at a person's role; it decides whether to grant access based on attributes of the subject, resource, action, and environment together. The subject can be a user or an Agent, the resource can be customer data or a tool, the action can be read, export, or delete, and the environment can be time, device, network, tenant, and approval status.

Read the fable →

Security

Backdoor attack

Backdoor Attack

Backdoor attacks implant hidden behavior in models, data, dependencies, or systems, so they behave normally day-to-day but abnormally when specific trigger conditions occur.

Read the fable →

Security

Context contamination

Context Poisoning

Context contamination occurs when malicious, outdated, irrelevant, or low-quality content enters an Agent's context and affects its reasoning, decisions, or tool calls.

Read the fable →

Security

Data exfiltration

Data Exfiltration

Data exfiltration is the act of data leaving a controlled boundary without authorization, and it can occur through tool calls, prompt injection, or integrated systems.

Read the fable →

Security

Data poisoning

Data Poisoning

Data poisoning is when attackers manipulate training, fine-tuning, evaluation, retrieval, or feedback data so that an AI system learns incorrect, biased, unsafe, or attacker-favorable behavior. It does not necessarily happen in the training set; it may also hide in document libraries, tickets, logs, user feedback, and human annotations.

Read the fable →

Security

Unauthorized agency

Excessive Agency

Over-privileged agency means that the autonomy, tool access, decision-making authority, or operational scope given to an AI Agent exceeds the task risk and governance capacity. It is not an ordinary minor permission error, but the system allowing the Agent to do things that should not be completed independently by it.

Read the fable →

Security

Model poisoning

Model Poisoning

Model poisoning manipulates weights, adapters, checkpoints or the training process to make the model produce backdoors, bias or erroneous behavior.

Read the fable →

Security

OWASP LLM Top 10

OWASP Top 10 for LLM Applications

The OWASP LLM Top 10 is a risk classification for large model applications, covering common vulnerabilities such as prompt injection, data leakage, and tool misuse.

Read the fable →

Security

Permission boundaries

Permission Boundary

Permission boundaries are the maximum limits on what an Agent, user, role, or tool can read, write, invoke, modify, delete, or delegate. They are not suggestions, nor soft reminders in prompts, but hard boundaries that must be enforced at runtime or the tool layer.

Read the fable →

Security

Role-based access control

Role-Based Access Control, RBAC

RBAC assigns permissions to roles rather than individual identities, letting users or Agents inherit access scope through roles, which makes governance easier.

Read the fable →

Security

Supply chain risk

Supply Chain Risk

Supply chain risk comes from dependency libraries, models, datasets, tools, plugins or external services, and may affect security, compliance and business continuity.

Read the fable →

Security

Tool output contamination

Tool Output Poisoning

Tool output contamination refers to external tools, web pages, files, APIs or plugins returning malicious or misleading content that induces an Agent to ignore policies, call other tools, leak data or change objectives.

Read the fable →

Security / agent runtime

Sandbox

Sandbox

A sandbox is an isolated execution environment used to restrict file, process, network access, system calls, tools and credentials. It ensures that even if code or tool output goes wrong, it is unlikely to affect external systems.

Read the fable →

Security / compliance

Audit logs

Audit Log

Audit logs record who performed what operations on which resources and when, usually including identity, time, resource, action, input/output and result status.

Read the fable →

Security / governance

Permission model

Permission Model

The permission model defines the relationships and boundaries among users, Agents, tools, resources, actions, authorization, approval, and audit.

Read the fable →

Security / operations

Principle of least privilege

Principle of Least Privilege

The principle of least privilege grants users, Agents, services, or tools only the minimum permissions and shortest effective time needed to complete the current task.

Read the fable →

Security / operations

Secrets management

Secrets Management

Secrets management handles the secure storage, distribution, rotation, revocation, and auditing of sensitive credentials such as API keys, passwords, tokens, and certificates.

Read the fable →

Security/Compliance

Information Security Management System

Information Security Management System, ISMS

Information Security Management System, ISMS is a system for managing information security, typically including security policies, asset identification, risk assessment, risk treatment, controls, roles and responsibilities, training, auditing, evidence, and continuous improvement.

Read the fable →

Security/Governance

Separation of duties

Segregation of Duties, SoD

Separation of duties splits conflicting responsibilities apart, preventing a single person or Agent from independently completing a high-risk process without checks and balances.

Read the fable →

Security/Privacy

Data loss prevention

Data Loss Prevention, DLP

DLP. It's a set of mechanisms for discovering, monitoring, and preventing sensitive data from leaving the security boundary, often covering endpoints, email, chat, cloud drives, web uploads, APIs, and database exports.

Read the fable →

Serving

vLLM

vLLM

vLLM is a high-throughput LLM inference engine that uses paged attention and continuous batching to improve concurrency efficiency, and is a common choice for production serving.

Read the fable →

Serving / UX

Streaming responses

Streaming Response

Streaming responses return results as tokens or content chunks are generated, rather than waiting for the complete output and returning it all at once.

Read the fable →

Serving metric

Tokens per second

Tokens Per Second, TPS

Tokens per second (TPS) measures how many tokens a model or service system generates per second, usually focusing mainly on the decoding stage. It is an important indicator of speed and throughput.

Read the fable →

Serving optimization

Chunked Prefill

Chunked Prefill

Chunked Prefill splits the prefill processing of long prompts into small chunks, preventing a single long request from occupying GPU scheduling resources for a long time.

Read the fable →

Serving optimization

Draft model

Draft Model

A draft model is a smaller or faster model in speculative decoding, used to first propose a string of candidate tokens. The larger target model then verifies these candidates and accepts only the prefixes that match its own distribution.

Read the fable →

Serving optimization

KV Cache

Key-Value Cache

When a large model generates text, each old token produces a Key and Value that the attention mechanism can use. By caching these Keys/Values, subsequent generation of new tokens does not require recomputing the entire history.

Read the fable →

Software architecture / workflow

State machine

State Machine

A State Machine describes system behavior with a set of explicit states and state transition rules. It is suitable for managing approval flows, task execution, Agent lifecycles, complex UIs, and exception handling, because the system is in an identifiable state at any moment and can only move to the next state under allowed conditions.

Read the fable →

Speech AI

Speech recognition

Automatic Speech Recognition, ASR

Automatic Speech Recognition, ASR, is the technology that converts speech into text. In enterprise Agents, ASR is commonly used for voice customer service, meeting notes, outbound calls, quality inspection and real-time voice assistants.

Read the fable →

Speech AI

Speech synthesis

Text-to-Speech, TTS

Text-to-Speech, TTS is the technology that converts text into audible speech. In enterprise agents, TTS is used in voice customer service, real-time assistants, notification broadcasts, accessibility, and outbound calling scenarios.

Read the fable →

System architecture

Multi-agent orchestration

Multi-Agent Orchestration

Multi-agent orchestration assigns tasks to multiple specialized Agents and coordinates roles, dependencies, messages, outputs, conflicts, and final results.

Read the fable →

System architecture

Orchestration

Orchestration

Orchestration coordinates models, tools, workflows, Agents, human approvals, state, and error handling so that a complete task can advance reliably across multiple components. It focuses on global dependencies, routing, permissions, retries, escalation, parallelism, and result merging.

Read the fable →

System design

Context Engineering

Context Engineering

Context Engineering is the engineering practice of selecting, organizing, compressing, updating and isolating context for a model. It is broader than traditional Prompt Engineering: it not only writes instructions, but also handles memory, retrieval, tool results, task state, permission boundaries, source trustworthiness and token constraints.

Read the fable →

Tokenization

Byte Pair Encoding

Byte Pair Encoding, BPE

Byte Pair Encoding, BPE is a common subword tokenization method. It starts from basic symbols and repeatedly merges the most frequently adjacent symbol pairs in the training corpus to obtain a fixed vocabulary.

Read the fable →

Tokenization

Token

Token

A token is the basic unit of text or data that a model processes; it may be a word, word piece, character fragment, punctuation mark or symbol. A model's context window, API billing, latency, throughput and output length are usually calculated in tokens, not characters or words.

Read the fable →

Tokenization

Tokenization

Tokenization

Tokenization is the process of converting raw text into a sequence of tokens that a model can process. Common methods include subword tokenization approaches such as BPE and SentencePiece. Tokenization affects token count, context usage, cost, speed, multilingual performance, code handling, and special character behavior.

Read the fable →

Tokenization

Tokenizer

Tokenizer

A Tokenizer is a software component that maps text to token IDs and restores generated token IDs back to text. It usually includes a vocabulary, a tokenization algorithm, and special token rules.

Read the fable →

Tokenization

Vocabulary

Vocabulary

A vocabulary is the set of tokens a tokenizer or model can recognize, usually including subword pieces, symbols, special tokens, and their token IDs. It determines how text is encoded, which pieces can be represented efficiently, and how much context space the same text occupies.

Read the fable →

Tool

Browser tools

Browser Tool

Browser Tool is a tool that lets an Agent open web pages, read pages, click controls, fill out forms, or execute web tasks.

Read the fable →

Tool interface

Plugin

Plugin

A Plugin is an external capability package that an AI system can discover and invoke, usually describing the purpose, parameters, permissions, and return format of an API, tool, or service. It lets an Agent connect to calendars, CRMs, databases, ticketing systems, payments, and other systems to perform actions.

Read the fable →

Training

Activation Checkpoint

Activation Checkpointing / Gradient Checkpointing

Activation checkpointing saves only part of the intermediate activations during training, and recomputes the rest during backpropagation, trading memory for computation.

Read the fable →

Training

bf16

Brain Floating Point 16

Brain Floating Point 16, or bf16, is a 16-bit floating-point format with the same exponent range as fp32 but fewer mantissa bits. Compared with fp32, it saves memory and bandwidth; compared with fp16, it is less prone to numerical overflow and usually does not require complex gradient scaling.

Read the fable →

Training

Catastrophic forgetting

Catastrophic Forgetting

Catastrophic Forgetting is the phenomenon in which a neural network, after fine-tuning on new data or a new task, significantly loses previously learned capabilities. When enterprises fine-tune LLMs, overly narrow data, too high a learning rate, or too many training epochs can all cause degradation of general capabilities, safety alignment, or existing business capabilities.

Read the fable →

Training

Chain-of-thought training

Chain-of-Thought Training

Chain-of-Thought Training is fine-tuning or training with step-by-step reasoning traces to improve a model's ability on multi-step tasks such as mathematics, planning, and logic. It conveys the problem-solving process better than supervising only with final answers, but it depends on high-quality, real, verifiable reasoning data.

Read the fable →

Training

Chinchilla approach

Chinchilla Optimal

Chinchilla Optimal refers to the compute-optimal scaling view proposed in DeepMind's Chinchilla work: under a fixed training compute budget, both model parameter count and training token count should be increased together; many early large models were oversized relative to their parameters and undertrained on tokens.

Read the fable →

Training

Continued pretraining

Continual Pre-training / Continued Training

Continued pretraining means continuing to train an existing foundation model on data from a new domain, a new time period, or a new language style. It lets the model add knowledge and adapt to industry phrasing, but it can also dilute its original abilities or introduce new biases.

Read the fable →

Training

Curriculum learning

Curriculum Learning

Curriculum Learning is a strategy of organizing training samples from easy to hard or by capability stage, similar to a human learning curriculum. It can be used for model pretraining, instruction fine-tuning, Agent trajectory training, and tool-use training, helping models more stably master foundational capabilities before handling complex tasks.

Read the fable →

Training

Data mixing

Data Mixing

Data mixing is the strategy of combining different data sources in proportions during pretraining or fine-tuning. When the proportions of code, math, Chinese, safety, customer service, industry documents, and other data differ, the capabilities the model ultimately excels at and the biases it develops will also differ.

Read the fable →

Training

Denoising objective

Denoising Objective

The Denoising Objective is the core objective in diffusion model training: the model learns to predict and remove noise from noise-added data, gradually restoring clean samples. By training under different noise intensities, the model grasps the structure of the data distribution, and during generation it works backward step by step from random noise to images, audio, or other content.

Read the fable →

Training

GRPO

Group Relative Policy Optimization

GRPO is a reinforcement learning optimization method commonly used for large model alignment and reasoning ability training. It generates a set of candidate responses for the same prompt and uses relative performance within the group to calculate reward advantages, thereby reducing dependence on an independent value function model.

Read the fable →

Training

Masked language modeling

Masked Language Modeling, MLM

Masked Language Modeling (MLM) is a training objective that randomly masks some tokens in the input and has the model predict the masked content based on context. It is commonly used for pretraining BERT-style bidirectional encoders, enabling the model to learn comprehension-oriented representations.

Read the fable →

Training

Mixed precision training

Mixed Precision Training

Mixed Precision Training uses different numerical precisions simultaneously during model training, such as FP32, FP16 and bf16, to reduce memory usage and increase throughput while preserving the stability of critical computations.

Read the fable →

Training

Multi-task learning

Multi-Task Learning

Multi-Task Learning trains one model jointly on multiple related tasks, sharing representations or parameters while learning the output of each task. It can improve data efficiency and generalization, especially when common structure exists among the tasks.

Read the fable →

Training

Next-word prediction

Next-Token Prediction

Next-Token Prediction is the training objective that has a model predict the next token based on existing context, and it is the core of GPT-style autoregressive language models. It can learn language, code, and reasoning patterns from large-scale data; practical applications still need to combine fact verification, permission checks, and execution validation.

Read the fable →

Training

Pretraining

Pre-training

Pre-training is the foundational stage in the training process, first letting the model learn general representations and generation capabilities from large-scale corpora. It forms a chain with subsequent fine-tuning, alignment, and evaluation; if the foundational heat is insufficient, later enterprise adaptation will be very difficult.

Read the fable →

Training

Reinforcement fine-tuning

Reinforcement Fine-Tuning, RFT

Reinforcement fine-tuning (RFT) uses verifiable or scorable outcome signals to continue optimizing model behavior. It is often used to help models learn strategies in reasoning, code, mathematics or enterprise processes that are more stable than demonstration data.

Read the fable →

Training

Verifiable reward reinforcement learning

Reinforcement Learning with Verifiable Rewards, RLVR

RLVR uses programmatically verifiable outcomes as reward signals to train models, such as whether a math answer, code test, or rule check passes.

Read the fable →

Training

Scaling laws

Scaling Laws

Scaling Laws describe the empirical relationship between model performance and scale factors such as parameter count, training data, and compute. They help teams predict the returns and costs of scaling up models, data, or compute, and avoid piling on parameters alone, insufficient data, or wasted compute. In enterprise decision-making, scaling laws are used for budget planning, model selection, and training strategy judgment.

Read the fable →

Training / privacy

Federated learning

Federated Learning

Federated Learning is a multi-party collaborative training method in which each participant keeps its local raw data and shares only model updates, gradients, or protected statistical information. It is often used in finance, healthcare, government, and enterprise scenarios where data cannot be centralized.

Read the fable →

Training and Inference

Knowledge distillation

Knowledge Distillation

Knowledge distillation lets a small model learn the output distribution or behavior of a large model, preserving as much capability as possible at lower inference cost.

Read the fable →

Training data

Data augmentation

Data Augmentation

Data Augmentation is a method of expanding training data by transforming, perturbing, rewriting, synthesizing, or combining samples, used to improve a model's adaptability to real variation. It can cover synonymous expressions, noisy inputs, format differences, boundary conditions, and rare scenarios.

Read the fable →

Transformers

Attention mechanism

Attention Mechanism

It lets the model, when processing a string of information, not treat all positions equally, but dynamically judge which positions are more important based on what is currently being generated or understood.

Read the fable →

Transformers

Decoder

Decoder

The Decoder is the part of the Transformer used to generate the output sequence. A typical Decoder uses a causal mask during generation, can only attend to already-generated tokens, and predicts the next token step by step.

Read the fable →

Transformers

Encoder

Encoder

The encoder is the part of the Transformer architecture responsible for encoding an input sequence into contextualized representations. It can usually view the input bidirectionally, making it suitable for understanding tasks such as classification, retrieval vectors, reranking, entity extraction, and document representation.

Read the fable →

Transformers

Multi-head attention

Multi-Head Attention

Multi-Head Attention splits attention into multiple heads, letting the model learn different types of relationships in parallel within the same layer, then merges the results. Different heads can focus on different patterns such as syntax, coreference, position, task constraints, and tool output.

Read the fable →

Transformers

Positional encoding

Positional Encoding

Positional Encoding injects order and relative position information into the Transformer, because self-attention itself is insensitive to token order. It can be fixed encoding, learnable encoding, or evolve into positional schemes like RoPE and ALiBi.

Read the fable →

Transformers

Self-attention

Self-Attention

Self-Attention lets each token in a sequence look at the other tokens in the same sequence and assign weights by relevance when computing its own representation. It is the core capability of the Transformer, enabling the model to build dependencies within the context.

Read the fable →

Transformers

Transformer

Transformer

It is a neural network architecture centered on the self-attention mechanism, allowing different positions in a sequence to directly reference each other and process text, code, image fragments and other information in parallel.

Read the fable →

Trust and attribution

Citation

Citations

Citations attach source references to key claims in generated content, allowing users to check evidence, verify facts, and trace provenance. In enterprise RAG and Agent systems, citations should point to the document fragments, tool results, or record versions that truly support the claim.

Read the fable →

User-facing product / Productivity

AI assistant

AI Assistant, Copilot

An AI Assistant / Copilot is an AI system embedded in the user's workflow that helps complete specific tasks. It typically handles retrieval, drafting, reminders, analysis, generating candidate options or executing low-risk steps, while responsibility and key decisions remain with people or business processes.

Read the fable →

Vector search library

FAISS

Facebook AI Similarity Search, FAISS

FAISS is Meta's open-source library for efficient vector similarity search and clustering, commonly used for local vector retrieval and large-scale nearest-neighbor search.

Read the fable →

Workflow automation / Orchestration

AI workflow

AI Workflow, Agentic Workflow

It orchestrates model judgment, rule validation, tool calls, business systems, human approval, and exception handling together, so AI doesn't just answer questions but reliably advances a business task.

Read the fable →

Interaction mechanism

Agent negotiation

Agent Negotiation

Agent negotiation lets multiple Agents reach decisions when goals, resources, or constraints conflict by exchanging information, making concessions, committing, and verifying.

Read the fable →

Collaboration mechanisms

Multi-agent reflection

Multi-Agent Reflection

Multi-Agent Reflection is a mechanism in which multiple agents independently review, critique, correct and consolidate plans, reasoning, tool results or outputs. It can improve quality on complex tasks, but it must guard against groupthink, shared errors, overconfidence and circular consumption.

Read the fable →

Collaboration mechanisms

Task decomposition

Task Decomposition

Task Decomposition is breaking a complex goal into executable, orderable, and verifiable subtasks. For an Agent, it determines planning quality, tool-call order, parallel boundaries, and failure recovery. Good task decomposition should include dependencies, inputs and outputs, acceptance criteria, risk points, and a replanning mechanism.

Read the fable →

Collaboration model

Agent debate

Agent Debate

Agent debate has multiple Agents separately propose, rebut, and test evidence to improve the reliability of complex reasoning or high-risk decisions.

Read the fable →

Collaboration model

Agent swarm

Agent Swarm

An agent swarm lets many relatively simple Agents solve problems together through local rules, shared signals and lightweight coordination.

Read the fable →

Collaboration model

Multi-agent consensus

Multi-Agent Consensus

Multi-Agent Consensus is a mechanism for multiple Agents, models, or roles to form controllable agreement on evidence, viewpoints, or action recommendations. It applies to high-risk decisions, complex task decomposition, cross-review, and multi-source information judgment.

Read the fable →

Collaboration model

Role-playing multi-agent

Role-Playing Multi-Agent

Role-playing multi-agent is when multiple agents take on different professional roles, stakeholder perspectives, or review viewpoints to jointly complete analysis, generation, review, or decision-making. Its value lies in explicitly introducing role boundaries and differences in responsibility, preventing a single model perspective from overlooking constraints in legal, operational, customer, technical, security, and other areas.

Read the fable →

Collaboration phenomena

Emergent behavior

Emergent Behavior

Emergent Behavior refers to overall behavior that appears after multiple models, Agents, or rules interact in a system, behavior that the designer did not write out item by item. It can bring efficiency, but it can also create congestion, collusion, circular calls, or risk amplification. Enterprise deployment must bring emergent behavior into simulation, observation, and governance.

Read the fable →

Observability

Agent decision tracing

Agent Decision Tracing

Agent Decision Tracing refers to recording the key judgments, context sources, tool calls, rule hits, alternative paths, and reasons for abandonment when an enterprise Agent executes a task, so the team can review "why it did this." It is not an ordinary pile of logs, but explainable evidence of the decision chain.

Read the fable →

Observability

Compliance log

Compliance Logging

Compliance logs retain records of system interactions, control execution, and key decisions as required by regulations, contracts, audits, or internal policies.

Read the fable →

Observability

User feedback loop

Feedback Loop

The user feedback loop continuously routes behavior, errors, complaints, manual corrections, and business outcomes back into the product, prompts, knowledge base, model, or process.

Read the fable →

Observability

Hallucination detection

Hallucination Detection

Hallucination detection determines whether model output is inconsistent with the given context, source documents, or known facts, commonly using claim extraction and evidence matching.

Read the fable →

Observability

LLM observability

LLM Observability

LLM Observability is the collection, tracing, and analysis of inputs, prompts, model calls, retrieval, tool calls, outputs, latency, errors, cost, and quality metrics for LLM/Agent applications. It helps teams pinpoint hallucinations, retrieval failures, cost anomalies, vendor issues, and version regressions.

Read the fable →

Observability

Latency monitoring

Latency Monitoring

Latency monitoring continuously measures how long LLM or Agent requests take, often focusing on time to first token, decoding speed, tool latency and end-to-end latency.

Read the fable →

Observability

Production drift detection

Production Drift Detection

Production Drift Detection continuously monitors in the online production environment whether input distributions, user behavior, tool returns, business scenarios, model output quality, and outcome metrics deviate from the state at launch.

Read the fable →

Observability

Prompt version management

Prompt Versioning

Prompt version management records prompt template versions and links them to deployment time, online performance, evaluation results, rollback records and business metrics.

Read the fable →

Observability

Token usage monitoring

Token Usage Monitoring

Token usage monitoring tracks input tokens, output tokens, total tokens, cost, user, product area, model, and request type. It lets the team know where the money is going, which requests are abnormal, and which features have pressured margins.

Read the fable →

Observability

Call chain tracing

Tracing

Tracing is an observability mechanism that records the path of a request as it flows across multiple services, agents, models, tools, and APIs. It typically links multiple spans via a trace id, recording latency, input/output summaries, errors, retries, and dependencies.

Read the fable →

Benchmark

BIG-bench (Beyond the Imitation Game Benchmark)

Beyond the Imitation Game Benchmark

BIG-bench, Beyond the Imitation Game Benchmark, is a language model capability benchmark covering a large number of tasks. Its goal is to go beyond single judgments such as "whether it is human-like" and systematically evaluate model performance on reasoning, knowledge, language, mathematics, creativity, and many other tasks.

Read the fable →

Benchmark

HumanEval (code generation evaluation)

HumanEval

HumanEval is a benchmark for evaluating code generation models, typically providing a function signature, description, and tests, and requiring the model to generate code that passes the tests.

Read the fable →

Benchmark

MMLU (Massive Multitask Language Understanding)

Massive Multitask Language Understanding

MMLU is a language understanding benchmark covering multiple disciplines and difficulty levels, used to evaluate a model's ability on knowledge, reasoning and exam questions.

Read the fable →

Benchmark

SWE-bench

SWE-bench

SWE-bench is a benchmark for evaluating models on real software engineering problems, typically requiring the model to modify code based on real open-source repository issues and pass tests.

Read the fable →

Benchmark framework

HELM (Holistic Evaluation of Language Models)

Holistic Evaluation of Language Models

Holistic Evaluation of Language Models, HELM, is an overall language model evaluation framework proposed by Stanford, emphasizing systematic evaluation of models across multiple dimensions such as accuracy, calibration, robustness, fairness, efficiency, bias, and toxicity.

Read the fable →

Security methods

Model safety evaluation

Model Safety Evaluation

Model safety evaluation uses standardized or customized test sets to systematically assess model behavior in scenarios such as harmful content, jailbreaks, misuse, privacy, bias, dangerous advice, and policy bypass. It focuses on refusal rate, harmful output rate, boundary consistency, alternative response quality, and stability under multi-turn attacks.

Read the fable →

Security methods

Red team testing

Red Teaming

Red team testing actively simulates attackers or high-risk users to test an AI system's security boundaries, policy vulnerabilities, and failure modes.

Read the fable →

Security mechanisms

Harmful content filtering

Harmful Content Filtering

Harmful content filtering identifies and blocks violence, pornography, hate, self-harm, illegal guidance, and harassment, forming the foundational layer of safety governance.

Read the fable →

alignment techniques

Reinforcement learning from human feedback

RLHF (Reinforcement Learning from Human Feedback)

It usually first lets the model learn to generate, then collects human preference comparisons over multiple answers, uses those preferences to train a reward model, and finally adjusts the model with reinforcement learning so its output moves closer to human preferences.

Read the fable →

alignment techniques

Safety fine-tuning

Safety Fine-Tuning

Safety fine-tuning continues training the model on safety data so that it more reliably refuses dangerous requests, reduces harmful outputs, and respects enterprise policy boundaries.

Read the fable →

Tools

Evaluation suite

Eval Suite / Eval Harness

An evaluation suite brings together test data, task scenarios, execution workflows, scoring rules and reports for repeatably evaluating a model or Agent.

Read the fable →

Metrics

Task success rate

Task Success Rate

Task Success Rate measures the proportion of times an Agent or automated system truly completes the user's goal on a given task. It cannot look only at call counts, response counts or whether a process started; it must clearly define success conditions, acceptance evidence and failure classification.

Read the fable →

Attack types

Adversarial examples

Adversarial Examples

Adversarial Examples are deliberately designed inputs that look normal but induce a model or system to make mistakes. In enterprise Agents, they may appear as malicious prompts, similar but incorrect documents, format traps, visual noise, edge business requests, and so on.

Read the fable →

Attack types

Denial-of-service attack

Denial-of-Service (DoS) on LLM

LLM denial-of-service attacks exhaust model service resources through extremely long contexts, recursive tasks, massive concurrency or expensive tool calls.

Read the fable →

Attack types

Indirect prompt injection

Indirect Prompt Injection

Indirect prompt injection hides malicious instructions in external content such as web pages, documents and emails, waiting for the Agent to retrieve or read them and trigger them.

Read the fable →

Attack types

Jailbreak

Jailbreak

Jailbreaking is an attempt to bypass the safety, policy, and permission boundaries of a model or Agent through role-playing, restating the question, obfuscating expression, multi-turn inducement, encoded language, and other methods.

Read the fable →

Attack types

Multimodal jailbreak

Multi-modal Jailbreak

Multimodal jailbreaks bypass model safety boundaries through non-text inputs such as images, audio, video, screenshots, QR codes or layout.

Read the fable →

Attack types

Prompt injection

Prompt Injection

Prompt injection is an attack method in which user-controllable text attempts to override, bypass or manipulate AI system instructions.

Read the fable →

Attack types

Jailbreak

Prompt Leaking

Prompt leakage is an attack technique in which attackers use inducement, role-playing, translation, format conversion, or multi-turn extraction to make a model reveal system prompts, developer instructions, hidden rules, tool descriptions, private context, or sensitive data.

Read the fable →

Architecture

Agent orchestration

Agent Orchestration

Agent Orchestration is the orchestration of task assignment, state transitions, tool calls, approvals, retries, and termination conditions for one or more Agents.

Read the fable →

Architecture

Blackboard architecture

Blackboard Architecture

Blackboard Architecture is a collaborative architecture: multiple specialized modules or Agents read the problem, write intermediate results, update hypotheses, and trigger the next processing step through a shared blackboard state.

Read the fable →

Architecture

Decentralized multi-agent

Decentralized Multi-Agent

Decentralized Multi-Agent is a multi-agent system without a single central controller, in which multiple Agents work together through local observations, protocols, message passing, and consistency rules.

Read the fable →

Architecture

Hierarchical multi-agent

Hierarchical Multi-Agent

Hierarchical Multi-Agent organizes multiple agents into layers: the upper layer handles goals, strategy, allocation and supervision, while the lower layer handles execution, local decisions and exception feedback.

Read the fable →

Architecture

Hybrid multi-agent

Hybrid Multi-Agent

Hybrid Multi-Agent is a multi-agent design that combines centralized orchestration, hierarchical control, decentralized collaboration, and local autonomy. Enterprise systems often need hybrid modes: high-risk actions go through central approval, low-risk local tasks execute autonomously, and exceptions escalate. The key is defining the control plane, autonomy scope, synchronization points, and governance rules.

Read the fable →

Architecture

Multi-agent system

Multi-Agent System (MAS)

A Multi-Agent System (MAS) is a system composed of multiple autonomous or semi-autonomous Agents that work together through communication, collaboration, competition, negotiation, or orchestration to achieve goals that a single Agent struggles to accomplish.

Read the fable →

Governance

AI Governance

AI Governance

AI governance is the framework of policies, processes, roles, controls, and accountability that an organization establishes around the development, procurement, deployment, operation, and retirement of AI systems.

Read the fable →

Governance

Access control

Access Control

Access control limits which specific actions which users, Agents, tools, models, knowledge bases and resources can perform.

Read the fable →

Governance

Agent Identity and Authentication

Agent Identity & Authentication

Agent identity and authentication establishes verifiable identity for Agents and completes authentication and authorization checks before calling systems, tools, or data.

Read the fable →

Governance

Audit logs

Audit Logs

Audit logs are traceable records a system leaves for key actions, typically including who, when, from where, with what permissions, requested what, called which tools, saw or changed what, what the result was, and whether it went through approval.

Read the fable →

Governance

Autonomy level

Autonomy Levels

It describes how much decision-making power, action power, and exception-handling power an Agent has in a task, and how frequently and at how critical a point humans need to intervene.

Read the fable →

Governance

Data privacy and PII masking

Data Privacy & PII Masking

Data Privacy & PII Masking refers to protecting personal privacy when AI/agents process data, and reducing PII exposure risk through masking, substitution, generalization, de-identification, minimization, access control, and auditing.

Read the fable →

Governance

Human in the loop

Human-in-the-Loop (Deep HITL)

It refers to a person participating multiple times during AI or Agent execution—not just final approval, but providing judgment at stages such as understanding, planning, execution, error correction and takeover.

Read the fable →

Governance

Human in the loop

Human-in-the-Loop (HITL)

It inserts human review, approval, correction or takeover at specific nodes of an automated process, so the system has human judgment in risky, low-confidence or high-impact scenarios.

Read the fable →

Governance

Humans out of the loop

Human-on-the-Loop (HOTL)

A looser control mode in which the AI system executes autonomously but humans maintain a supervisory posture, intervening only when the system issues an alert or anomaly.

Read the fable →

Governance

Model approval process

Model Approval Workflow

Model Approval Workflow is the approval process before a model moves from experimentation into production or expanded use, typically covering purpose statements, risk classification, evaluation results, security compliance, data restrictions, responsible owners, launch scope, and rollback plans.

Read the fable →

Governance

Model risk assessment

Model Risk Assessment

Model risk assessment is a structured evaluation, before launch, of a model's capability boundaries, potentially harmful use scenarios, bias amplification risks, and potential for misuse.

Read the fable →

Governance

Rate limiting

Rate Limiting

Rate limiting controls how many requests, actions, tokens, tool calls or expensive operations a given user, tenant, IP, API key, workflow or Agent can initiate within a time window.

Read the fable →

Governance

Responsible AI

Responsible AI

Responsible AI means incorporating legality, fairness, privacy, security, transparency, human oversight and accountability into the design, deployment and operation of AI/Agents, rather than pursuing only automation efficiency.

Read the fable →

Governance

Right of regret and revocation mechanisms

Right to Appeal & Rollback

Right to Appeal & Rollback is a mechanism that provides appeal, review, revocation, restoration, and version rollback when AI or Agent decisions affect users, customers, or business rights.

Read the fable →

Governance

Security incident response

Security Incident Response

Security incident response is a structured process for handling security events such as prompt injection, data leakage, credential exposure, and unauthorized access.

Read the fable →

Governance

Usage policy

Usage Policy

A usage policy defines which uses of AI, models, data, tools or agents are acceptable, which are prohibited or require approval. It must cover user types, data categories, task risk, prohibited behaviors, exception handling and enforcement mechanisms.

Read the fable →

Evaluation

LLM evaluation

LLM Evaluation (Eval)

LLM evaluation measures model or Agent performance through automated tests, human scoring, model judges, adversarial probes and online monitoring.

Read the fable →

Evaluation methods

Adversarial evaluation

Adversarial Evaluation

Adversarial evaluation deliberately constructs confusing, boundary, malicious, or stress-type inputs to test the robustness, safety boundaries, and failure modes of models and Agents. It covers prompt injection, jailbreak, tool abuse, data leakage, policy bypass, combined attacks, and high-pressure business scenarios.

Read the fable →

Evaluation methods

Alignment Evaluation

Alignment Evaluation

Alignment evaluation measures whether a model or agent conforms to human intent, enterprise policy, safety boundaries, and business goals.

Read the fable →

Evaluation methods

Capability assessment

Capability Evaluation

Capability Evaluation is itemized, reproducible testing of a model's or Agent's specific capabilities, such as reasoning, retrieval, tool use, long context, collaboration, refusal, safety boundaries, and business task completion.

Read the fable →

Evaluation methods

Human evaluation

Human Evaluation

Human evaluation is when human reviewers judge model or Agent output according to a rubric, business context, and quality standards. It suits subjective, complex, high-risk tasks or tasks where automated metrics do not cover enough, such as sales pitch quality, customer tone, factual explanation, risk judgment, and final delivery usability.

Read the fable →

Evaluation methods

Round-by-round evaluation

Per-Turn Evaluation

Per-Turn Evaluation evaluates an Agent or dialogue system at each turn of action, tool call, observation, and reply, rather than only looking at the final result.

Read the fable →

Evaluation questions

Capability contamination and data leakage

Contamination & Data Leakage

Contamination & Data Leakage refers to exposure to evaluation sets, answers, similar questions, or sensitive business data during training, tuning, or prompting, causing model performance to be overestimated or privacy to leak. It undermines benchmark credibility and may also bring customer data into outputs where it should not appear.

Read the fable →

Evaluation questions

Prompt sensitivity

Prompt Sensitivity

Prompt Sensitivity means a model shows noticeable performance fluctuations in response to changes in prompt wording, order, format, example selection or field naming. It can cause enterprise Agents to make different judgments under the same facts, affecting evaluation stability and production reliability.

Read the fable →

Scheduling

Agent routing

Agent Routing

Agent routing assigns tasks based on request content, subtask type, capability descriptions, permission boundaries, load and historical performance.

Read the fable →

Communication

Agent communication protocol

Agent Communication Protocol

Agent Communication Protocol is a protocol or language that defines the message format, semantics and interaction rules between Agents. It not only specifies fields, but also expresses communication intent, such as request, notification, commitment, refusal, query, delegation and confirmation.

Read the fable →

京ICP备2026014272号