Glossary
Common Terms
This section organizes the terms used in the body of this documentation. When you want to check the meaning of a term in the text, refer to this glossary.
| Term | Description |
|---|---|
| Accel Orbit | The collective name for the suite of features for AI-assisted development on iAP. It consists of the Accel CLI, the context for AI agents, the AI-native Development Support Feature, and more. For its components, see What Is Accel Orbit?. |
| AI-native development | A style of developing iAP user modules in which you hand the specification of what you want to build to an AI agent, have it generate the artifacts, and repeat verification and fixes. For details, see Overview of AI-native Development. |
| CLI (Command-Line Interface) | A method of interacting with a computer by typing text commands. An example is running bun --version in a terminal. |
| IDE (Integrated Development Environment) | An environment that combines code editing, building, debugging, and other development tasks into a single application. In this guide, VSCode serves as the IDE. |
| JDK / JRE | JDK (Java Development Kit) is the complete package required for developing and building Java programs. JRE (Java Runtime Environment) is the set required only for running Java programs. This guide requires the JDK to build user modules. |
| PATH (environment variable) | A list the OS uses to find executable files. Executables in folders listed in PATH can be run by filename alone from any directory. |
| Clone | The operation of copying a remote repository (e.g., GitHub) to your local PC. Performed with the git clone command. |
| Shell | A program that interprets and executes commands entered in a terminal. Common examples are PowerShell on Windows, and bash or zsh on macOS/Linux. |
| Terminal | A screen for interacting with a shell. Examples include PowerShell on Windows, Terminal.app on macOS, and GNOME Terminal on Linux. |
| Package manager | A system for installing, updating, and removing software and libraries via commands. Examples in this guide include Bun, apt, brew, and dnf. |
| Proxy | A server that relays internet traffic. In corporate networks, external communication may only be possible through a proxy, requiring proxy settings to be configured for each tool. |
| User module | A module created by users (the smallest installable unit of functionality in IM-Juggling). |
| Runtime | Software that provides the foundation for running programs. In this guide, Bun serves as the JavaScript runtime, and the JDK serves as the Java runtime and build foundation. |
| Repository | A storage location for source code and its change history. There are two types: local (your PC) and remote (e.g., GitHub). |
| Extension | A plugin that adds functionality to VSCode. A wide variety of extensions are available, including language support, agent integration, and linters. |
Docker-related terms are summarized in Basic Docker Terminology.
AI-native Development Support Feature Terms
This section organizes terms related to operating the AI-native Development Support Feature (formerly the Development Support Module (velbench)).
| Term | Meaning |
|---|---|
| Staging (Environment) | A named, independent workspace created on the shared development server. Identified by a staging ID. |
| Staging ID | A name that the user specifies to identify a staging (alphanumerics, hyphens, and underscores; 1–100 characters). |
| Deployment | A single unit of transferring local assets to a staging. The latest one becomes that staging's active assets. |
| Deploy | The operation of transferring local assets to a staging. |
| Undeploy | The operation of disabling an active deployment and discarding its assets. It is also performed automatically when you deploy an update. |
| Owner (Participant) | A participant who can operate a staging. All participants are equal. |
| Staging switch | Switching your own session to a specific staging and running on its assets. "Cancel switch" returns you to main. |
| Main runtime | The normal (main) execution environment, when you have not switched to a staging. |
Visual Studio Code Extension Terms
This section organizes the debugging and testing terms used with the e Builder extensions described in Using Visual Studio Code. For deployment terms, see AI-native Development Support Feature Terms.
| Term | Meaning |
|---|---|
| Debugging | The work of investigating the cause of a defect while running a program. |
| Breakpoint | A marker set in advance to indicate "pause when execution reaches this line." |
| Attach | Connecting VSCode to an already running server so that it can be debugged. |
| Step execution | Advancing a program one line at a time from a paused state. |
| Coverage | The proportion of the code (lines, branches, and functions) that was executed when the tests ran. |