Glossary¶
This glossary provides definitions for ConnectSoft-specific terms, acronyms, and concepts used throughout the documentation. It is written for anyone reading ConnectSoft 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" |
| AI Squad | Virtual team of AI agents delivering defined outcomes on a subscription basis | Also called "Squad" |
| Agent | Specialized AI component that performs specific tasks (e.g., Architect Agent, Developer Agent) | See Agent System Overview |
| Aggregate | Cluster of domain objects treated as a single unit for data changes | DDD concept |
| Bounded Context | Explicit boundary within which a domain model applies | DDD concept |
| BDR | Business Decision Record — documents business and product decisions | See BDR Index |
| ADR | Architecture Decision Record — documents technical architecture decisions | See ADR Index |
| Blueprint | Standard structure and patterns for generated microservices | See Agent Microservice Standard Blueprint |
| Bounded Context | Explicit boundary within which a domain model applies | DDD concept |
| 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 | See Knowledge & Memory System |
| Library | Reusable component or NuGet package (e.g., ConnectSoft.Extensions.*) | See Libraries Catalog |
| Microservice Template | Template for generating microservices with Clean Architecture | 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 | See Factory Overview |
| Platform | Ready-made SaaS service (Identity, Audit, Config, Bot, and 100+ more planned) | See Product Portfolio |
| Platform Category | One of 12 logical groupings of platforms (Infrastructure, Data & Analytics, etc.) | See Platform Categories |
| Platform Bundle | Group of related platforms sold together (e.g., Security Bundle, Healthcare Bundle) | See Platform Categories |
| Platform Maintenance Tier | Maintenance level assigned to platforms (Tier 1 = active development, Tier 2 = regular maintenance, Tier 3 = security updates only) | See Platform Maintenance |
| Tier ½/3 Platforms | Prioritization tiers for platform development (Tier 1 = high priority, Tier 2 = medium, Tier 3 = lower) | See Platform Prioritization Framework |
| Template | Starting point for generating code (microservice, library, infrastructure) | See Templates Overview |
| Tenant | Organization or customer using a multi-tenant system | Each tenant has isolated data |
| Vertical-Specific Platform | Industry-specific platform tailored to particular sectors (Healthcare, Finance, Insurance, IT, etc.) | See Vertical-Specific Solutions |
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 |
| 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 |
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 ConnectSoft-specific terms. General software engineering terms (e.g., "API", "REST") are not included unless they have ConnectSoft-specific meaning.
Related Documents¶
- FAQ - Frequently asked questions
- Factory Overview - Factory concepts
- Architecture & Engineering - Architecture concepts
- Product Portfolio - Product terminology