FDC3 Terminology Changes

## Enhancement Request

### Use Case:

A developer or enterprise architect new to FDC3 encounters terms like **"Desktop Agent."** This creates immediate confusion, as **"Agent"** is now synonymous with AI, misrepresenting the component's role as a runtime/broker. This ambiguity is compounded by variations like **"Web Desktop Agent"** and the fact that the name **"FDC3"** itself implies a scope limited to Finance and the Desktop, which no longer reflects its modern capabilities.

***

### Workflow Description

The target workflow is one where a developer can read the FDC3 specification and immediately grasp the role of each architectural component due to clear, intuitive, and consistent naming. This developer can then confidently build applications that correctly interact with the FDC3 environment, embed FDC3-aware components, and use different channel types without ambiguity, leading to faster and more reliable integrations.

***

### Workflow Examples

* **Example 1 (Avoiding Confusion):** An enterprise architect is evaluating FDC3. They read **"Desktop Agent"** and spend time investigating whether FDC3 has dependencies on AI services, only to discover it's a message broker. With a clearer term like **"FDC3 Runtime,"** its function would be immediately understood, saving evaluation time.

***

### Additional Information

This proposal addresses several ambiguous, outdated, or inconsistent terms within the FDC3 standard. The goal is to establish clear, intuitive naming conventions that reflect the standard's evolving capabilities and broadening adoption.

This starts with the name **"FDC3"** itself. While the brand is strong, its origin as an acronym (Financial Desktop Connectivity and Collaboration Consortium) is now limiting as the standard is adopted in new domains and on platforms beyond the traditional desktop. It is proposed that FDC3 be treated as a standalone brand name, decoupling it from its historical acronym. This mindset of evolving the language to match the standard's modern reality is the foundation for the specific proposals outlined below.

#### Key Terms for Discussion

Here is a summary of the current terms requiring review:
* **FDC3** (as an acronym)
* **Desktop Agent**
* **Sub-Agent Specification**
* **WCP** (Web Connection Protocol) & **DACP** (Desktop Agent Communication Protocol)
* **Private Channels**

Additional terms:
* **User Channels**
* **Workspaces, Groups, Frames, Layouts** *

#### Proposed Terminology Changes

| Current Term/Concept | Proposed New Term / Action | Reasoning |
| :--- | :--- | :--- |
| **FDC3 (as an acronym)** | **Formalize FDC3 as a brand name** | Decouples the standard from its "Financial Desktop" origin, supporting broader adoption in new domains and platforms. The brand itself is already strong and well-recognized. |
| **Desktop Agent** | **FDC3 Runtime** | "Runtime" accurately describes the environment that enables FDC3 applications to run and interoperate. It avoids "Agent," which is now heavily associated with AI, preventing future confusion. |
| **WCP (Web Connection Protocol)** | **FDC3 Web Handshake Protocol** | Renaming to "Handshake Protocol" more accurately describes its single purpose: managing the initial discovery and secure connection handshake between a web application and the FDC3 Runtime. |
| **DACP (Desktop Agent Comms Protocol)** | **FDC3 Message Protocol** | Renaming to "Message Protocol" clarifies this as the main "wire protocol" used for all ongoing communication (context, intents, etc.) after a connection has been established by the Handshake Protocol (WCP). |
| **Private Channels** | **"Unlisted Channels OR Hidden Channels"** | "Unlisted" is an intuitive adjective to describe the shared characteristic of these channel types. It correctly implies they are not in the system channel list but are otherwise fully functional, avoiding ambiguity. Private is often means encryption, TLS etc. |

----

| Current Term/Concept | Group Suggestions | Reasoning |
| :--- | :--- | :--- |
| **Sub-Agent** | **FDC3 App Component, sub-app, child app, widget, module, component, microagent** | There were many suggestions during the last meeting that have been included. |
| **Workspaces, Groups, Frames, Layouts**| **?** | Different vendors use inconsistent terms for a saved collection of applications. The FDC3 standard should formally adopt a way to describe a collection of apps. |

No files, tests, or entry points are identified. Begin by reviewing the FDC3 specification terminology and the proposed replacements in this issue. Done would require agreement on a defined terminology set and corresponding specification updates.

Written by the indexing model from the issue text.