This page defines the terms used in the Control Hub and its documentation. The terms are listed alphabetically. Each entry includes a brief definition and a link to the page where you can find more information on the topic.
|
Term |
Description |
Further Information |
|---|---|---|
|
Active Platform |
The platform connection that the PAS CLI currently works against. Exactly one stored connection is active at a time. |
|
|
Agent |
A feature of a service component. An AI agent that answers questions and performs tasks on the platform. It is reached through the service that provides it and therefore has no endpoint of its own. |
|
|
AI Coding Assistant |
The assistant that you use in your editor. Every project created with |
|
|
App |
A component type. A web frontend that users open in the browser. |
|
|
Approval Gate |
The end of a phase of the development workflow. The result is presented to you, and the workflow advances only after you approve it explicitly. |
|
|
Bundle |
A group of components that are deployed together. A bundle is a package of the project and lists its components in a |
|
|
Cluster Development |
Running the project on a Kubernetes cluster with |
|
|
Component |
A part of a project. A component is a service or an app. A service can additionally provide one or more agents. |
|
|
Component Default |
The baseline values of a component, built into its image. They apply wherever no other source sets a value. |
|
|
Component Deployment |
The running instance of a single component inside a project deployment. It has its own status, type, endpoint, and configuration. |
|
|
Component Deployment Detail View |
The right-hand view of the deployment detail page. It shows the status, the type, the endpoint, and the configuration of the selected component deployment. |
|
|
Component-Level Configuration |
The configuration values of a single component. You author them in the configuration file of that component. |
|
|
Configuration |
The runtime settings of a deployment, stored as JSON. Configuration exists at project level and at component level. |
|
|
Configuration Editor |
The editor in which you view and change the configuration of a deployment. |
|
|
Content Area |
The part of the interface to the right of the sidebar. It displays the current view and changes as you navigate. |
|
|
Control Hub |
The web application in which you deploy and operate the projects that are published on the platform. |
|
|
Conversation |
All messages you have exchanged with the AI assistant since you last started a new conversation. |
|
|
Default Bundle |
The implicit bundle of a project that defines no bundle of its own. It contains all components of the project. |
|
|
Deployment |
A running instance of a PAS project in an environment. Each deployment has its own name and its own configuration. |
|
|
Deployment Configuration |
The runtime settings that a project ships. You author them as files in your project, and they are published with the version. |
|
|
Deployment Detail Page |
The page on which you monitor and manage a single deployment. It consists of the deployment panel and the component deployment detail view. |
|
|
Deployment Name |
The name that identifies a deployment. It must be unique within an environment. |
|
|
Deployment Panel |
The left-hand panel of the deployment detail page. It identifies the project deployment, holds its actions, and lists its components. |
|
|
Deployments View |
The landing page of the Control Hub. It lists the deployments running across your environments and is where you monitor and manage them. |
|
|
Endpoint |
The address at which a running component can be reached. A component that has no endpoint shows a dash instead of a link. An agent has no endpoint of its own. |
|
|
Environment |
The target a project is deployed to. Environments keep deployments separate from one another, for example a development and a production environment. |
|
|
Legacy Standalone Service |
A deployed service that is not part of a project. It carries a Legacy badge and cannot be managed from the Control Hub. |
|
|
Local Development |
Running the project on your own computer with |
|
|
Logout |
The sidebar option that ends your session and returns you to the sign-in page. |
|
|
Merge |
The default strategy for the configuration values an operator sets on a deployment. It keeps a shipped value wherever the operator sets no value. |
|
|
Multiple |
The status of a project deployment whose component deployments are currently in different states, for example some started and some stopped. |
|
|
Navigation Header |
The bar above the content area. It holds the back button and the Ask Assistant button, which opens the AI assistant. |
|
|
PAS CLI |
The command line tool that developers call through |
|
|
PAS Code |
The solution that covers scaffolding, development, testing, deployment, and operation of software for the Scheer PAS platform in a single workflow. |
|
|
PAS Resource Monitor |
The separate application in which the logs of a project or component deployment are displayed. The Control Hub links to it and does not display logs itself. |
|
|
Pipeline |
The platform process that a push starts. It builds the components of the project, creates a version, publishes the images and the configuration, and registers the version with the platform. |
|
|
Platform |
A Scheer PAS installation. It hosts the Git repositories of your projects, builds and publishes your projects, and runs your deployments. |
|
|
Platform Assistant |
The name of the AI assistant of the Control Hub. |
|
|
Platform Connection |
The stored connection between your computer and one platform. You can store more than one connection, and you activate one of them. |
|
|
Precedence |
The order in which a configuration value wins when more than one source sets it. A component default is overridden by a referenced value, and a referenced value is overridden by a value set directly in the configuration. |
|
|
Profile |
A named Kubernetes cluster target, stored as a JSON file in |
|
|
Project |
A versioned, deployable unit made of one or more components. Definition of a PAS project. Published projects appear in the Projects Catalog. |
|
|
Project Deployment |
A running instance of a project in an environment, with its own name and its own configuration. It contains one component deployment per component of the project. |
|
|
Project-Level Configuration |
The configuration values that apply to the whole deployment and that its components share. You author them in the configuration file of the bundle. |
|
|
Projects Catalog |
The view in which you browse the published projects and their versions, and from which you deploy them. |
|
|
Push |
The handover of your project from your computer to the platform. A push starts the pipeline. |
|
|
Quick Actions |
The actions in the last column of a row in the Deployments table, for example start, stop, delete, and open logs. |
|
|
Readme |
The description of a project written by its author. It is displayed on the Readme tab of the project detail view. |
|
|
Reference |
A pointer to a configuration value instead of a copy of the value: to a project-level value by name, or to a secret kept in the cluster. The platform resolves a reference when the project is deployed. |
|
|
Repository |
The Git repository of your project on the platform. |
|
|
Rules |
The code, specification, and documentation rules that the skills apply. A project completes or overrides them in its .agents folder. |
|
|
Secret |
A configuration value that is kept in the cluster and used through a reference. A referenced secret appears neither in your sources nor in the published images. |
|
|
Service |
A component type. A component that provides functions and data to apps and to other services. |
|
|
Sidebar |
The panel on the left of the window. It holds your identity, the navigation between the two views, and the Logout button. |
|
|
Skill |
A packaged instruction set that your AI coding assistant loads when it recognizes a matching task. A skill names the PAS CLI command to call, the options that apply, and the rules to follow. |
|
|
Skill Source |
A location that a project declares its skills from, for example an installed package or a local folder. |
|
|
Spec-Driven Development |
The fixed order that every change follows: specification, then code, then documentation. Each phase ends with an approval gate. |
|
|
Specification |
A SPEC.md file that describes what the code must achieve. It sits next to the code it governs and applies to its own directory and to the subdirectories of that directory. |
|
|
Status |
The state of a project or component deployment: Started, Starting, Stopped, Multiple, or Failed. |
|
|
Type |
The classification of a component: service, or app. |
|
|
Version |
The result of publishing a project. Each time a project is published, it becomes a new version. You select the version when you deploy. |