Glossary¶
This glossary provides definitions for ConnectSoft AI Software Factory-specific terms, acronyms, and concepts used throughout the documentation. It is written for anyone reading AI Factory documentation who needs clarification on terminology.
If you encounter a term that's not defined here, or if you think a definition needs improvement, please propose an update (see "How to Propose New Terms" below).
Terms¶
| Term | Definition | Notes |
|---|---|---|
| AI Factory | The ConnectSoft AI Software Factory — core platform that generates SaaS solutions using AI agents | Also called "Factory" |
| Agent | Specialized AI component that performs specific tasks (e.g., Architect Agent, Developer Agent, QA Agent) | See Agent System Overview |
| Aggregate | Cluster of domain objects treated as a single unit for data changes | DDD concept |
| Blueprint | Structured specification that describes features, domains, or systems to be generated by the Factory | See Agent Microservice Standard Blueprint |
| Bounded Context | Explicit boundary within which a domain model applies | DDD concept |
| Coordinator | Factory component that orchestrates agent execution and manages workflow state | See Coordinators |
| Domain Event | Event that represents something that happened in the domain | Event-driven architecture |
| Factory Run | Single execution of the Factory to generate code and artifacts | See Agent Execution Flow |
| Knowledge System | System that stores and retrieves code, docs, blueprints, and patterns for agent use | See Knowledge and Memory System |
| Library | Reusable component or NuGet package (e.g., ConnectSoft.Extensions.*) | See Libraries List |
| Microservice Template | Template for generating microservices with Clean Architecture, DDD, and event-driven patterns | See Microservice Template |
| Multi-Tenant | Architecture pattern where a single instance serves multiple tenants | Each tenant's data is isolated |
| Orchestrator | Factory component that coordinates agent execution and manages workflows | See Orchestration Layer |
| Orchestration Domain | Central domain coordinating multi-agent collaboration, phase-driven execution, and automated project flows | See Orchestration Domain |
| Template | Starting point for generating code (microservice, library, infrastructure) | See Templates Overview |
| Template Catalog | Domain managing reusable, versioned, and validated solution templates | See Template Catalog |
| Template Overlay | Specialized template that adds domain-specific functionality on top of a base template | See template architecture documentation |
| Tenant | Organization or customer using a multi-tenant system | Each tenant has isolated data |
| Trace | Complete record of a Factory execution including all agent actions, outputs, and metadata | Every run produces a traceId |
| TraceId | Unique identifier for a Factory execution trace | Links all artifacts to their execution context |
| Studio | AI Software Factory Studio — web-based interface for managing projects, runs, and Factory operations | See Studio Overview |
| Workflow | Orchestrated sequence of agent actions to accomplish a specific goal | See Workflows |
| Blueprint Version | Version identifier for a blueprint specification | Enables traceability and replay |
| Agent Skill | Specific capability or action that an agent can perform | Agents are skill-scoped |
| Execution Graph | Graph structure representing agent collaboration and execution flow | See Agent Execution Flow |
| Phase | Stage in the Factory lifecycle (e.g., Vision, Architecture, Development, Deployment) | See Project Lifecycle |
| Milestone | Significant checkpoint in project execution | See Timing, Milestones, and Sprint Orchestration |
| Sprint | Time-boxed iteration in the Factory execution model | See Timing, Milestones, and Sprint Orchestration |
| MCP | Model Context Protocol — standard protocol for exposing context to AI models | See MCP Servers Catalog |
| MCP Server | Service implementing the Model Context Protocol to provide context to AI agents | See MCP Servers Catalog |
| DSL | Domain-Specific Language — specialized language for expressing domain concepts | See DSLs |
| RAG | Retrieval-Augmented Generation — AI technique combining retrieval and generation | Used in knowledge system |
| Vector Search | Semantic search using vector embeddings | Used in knowledge system for pattern matching |
| Span | Unit of work in distributed tracing | See observability documentation |
| Trace (Observability) | Collection of spans representing a request flow | Different from Factory execution trace |
| Health Check | Endpoint or mechanism for verifying service health | Generated by templates |
| IaC | Infrastructure as Code — managing infrastructure through code | Bicep, Terraform, Pulumi, etc. |
| Bicep | Domain-specific language for deploying Azure resources declaratively | Used in generated infrastructure |
| Pulumi | Infrastructure as Code platform using general-purpose programming languages (C#, TypeScript, Python, etc.) | Used in Platform Template for type-safe, multi-cloud infrastructure |
| Clean Architecture | Architecture pattern emphasizing separation of concerns and dependency inversion | See Clean Architecture and DDD |
| DDD | Domain-Driven Design — approach to software development focusing on domain modeling | See Clean Architecture and DDD |
| Event-Driven Architecture | Architecture pattern using events for communication between components | See Event-Driven Mindset |
| Cloud-Native | Approach to building applications designed for cloud environments | See Cloud-Native Mindset |
| Observability | Ability to understand system behavior through logs, metrics, and traces | See Observability-Driven Design |
| Security-First | Design approach where security is considered from the beginning | See Security-First Architecture |
| Modularization | Design principle of separating responsibilities into independent units | See Modularization |
| AI-First Development | Development approach prioritizing AI agents and automation | See AI-First Software Development |
Acronyms¶
| Acronym | Meaning | Notes |
|---|---|---|
| ADR | Architecture Decision Record | Technical decisions |
| BDR | Business Decision Record | Business decisions |
| DDD | Domain-Driven Design | Architecture approach |
| EDA | Event-Driven Architecture | Architecture pattern |
| IaC | Infrastructure as Code | Bicep, Terraform, etc. |
| IdP | Identity Provider | Authentication provider |
| MCP | Model Context Protocol | Protocol for AI context |
| OIDC | OpenID Connect | Authentication protocol |
| OAuth2 | OAuth 2.0 | Authorization framework |
| RAG | Retrieval-Augmented Generation | AI technique for knowledge bases |
| RBAC | Role-Based Access Control | Access control model |
| SLA | Service Level Agreement | Uptime and performance guarantees |
| SLO | Service Level Objective | Performance targets |
| SSO | Single Sign-On | Authentication pattern |
| API | Application Programming Interface | Interface for service communication |
| BFF | Backend for Frontend | API Gateway pattern |
| CI/CD | Continuous Integration / Continuous Deployment | Automation pipeline |
| gRPC | gRPC Remote Procedure Calls | RPC framework |
| REST | Representational State Transfer | API architectural style |
| OpenAPI | OpenAPI Specification | API description format |
| GraphQL | GraphQL Query Language | API query language |
| K8s | Kubernetes | Container orchestration platform |
| YAML | YAML Ain't Markup Language | Data serialization format |
| JSON | JavaScript Object Notation | Data format |
| PII | Personally Identifiable Information | Sensitive data requiring protection |
| RBAC | Role-Based Access Control | Access control model |
| SaaS | Software as a Service | Software delivery model |
| SDK | Software Development Kit | Set of development tools |
| UI | User Interface | User-facing interface |
| UX | User Experience | User interaction design |
| MVP | Minimum Viable Product | Initial product version |
| OKR | Objectives and Key Results | Goal-setting framework |
How to Propose New Terms¶
To propose a new term or improve an existing definition:
- Create a Pull Request - Edit this file and add/update the term
- Provide Context - Include where the term is used and why it needs definition
- Link to Docs - If relevant, link to detailed documentation
Note
This glossary focuses on AI Factory-specific terms. General software engineering terms (e.g., "API", "REST") are included only if they have specific meaning in the AI Factory context.
Related Documents¶
- Agent System Overview - Agent concepts
- Platform Architecture - Architecture concepts
- Templates Overview - Template terminology
- Vision Overview - Vision and strategy concepts