Repository Conventions
🤖 Generated with Claude Code
⚠️ Not yet reviewed
Co-Authored-By: Claude (noreply@anthropic.com)
Orientation for new developers: what the repository prefixes mean and which project types
exist. All repositories live in Azure DevOps under togethercca/tis-cca.
This document describes the naming scheme, not the full inventory. Which services actually run, and how heavily they are used, is covered by platform-usage-overview.md. How we work inside a repository — branches, commits, pull requests — is in git/.
Namespace Prefixes​
| Prefix | Meaning | Examples |
|---|---|---|
tis.gf.* | Geschäftsfall framework — business processes toward insurers and customers | tis.gf.api, tis.gf.smr5, tis.gf.soagfx, tis.gf.esign |
tis.bestand.* | Portfolio data management | tis.bestand.omdsexplorer, tis.bestand.klauselservice, tis.bestand.omdsdownload |
tis.identity.* | Identity and access management | tis.identity (IdentityServer), tis.identity.api, tis.identity.ovbselfservice |
Tis.Partner.* | Integrations with individual insurers (VU) | Tis.Partner.UniqaIntegration, Tis.Partner.AllianzIntegration |
Tis.Hosting.* | Platform building blocks and libraries | Tis.Hosting.Extensions, Tis.Hosting.ApiGateway, Tis.Hosting.Dispatcher |
Tis.Omds3.* | Services around the OMDS3 standard | Tis.Omds3.DeepLink |
tis-cca.* | Organisation-wide repositories, not a single service | tis-cca.documentation, tis-cca.pipeline-templates, tis-cca.wiki |
Further repositories follow none of these prefixes (tis.core, tis.userprofile,
tis.volltextsuche, boa-api, tiscca.cads-parent, …).
Casing: capitalisation is historically inconsistent —
Tis.Partner.UniqaIntegrationnext totis.partner.VigIntegration,tis.bestand.omdsCollectornext totis.bestand.omdsdownload. A new repository MUST follow whichever casing already dominates its prefix.
Project Types​
Together Platform​
| Type | Description | Examples |
|---|---|---|
| Internal API services | REST APIs consumed only by other TOGETHER/TIS services | tis.identity.api, tis.userabgleich |
| Public API services | REST APIs for partners, large customers and other software vendors | tis.gf.api, boa-api |
| Web applications | ASP.NET Core with a frontend | tis.identity (IdentityServer), tis.gf.wgp |
| Partner integrations | Insurer-specific integrations, used by API services as a backend | Tis.Partner.AllianzIntegration |
| Libraries | NuGet packages consumed by other services | Tis.Hosting.Extensions |
| Tools | Command-line utilities | tis-secrets (in Tis.Hosting.Extensions) |
| Windows services | Background services | tis.volltextsuche.gf.import.service |
API services use REST and OAuth2 throughout. Partner integrations additionally carry partner-specific OAuth2 flows and a reverse-proxy pattern.
CCA​
| Type | Description | Examples |
|---|---|---|
| Desktop applications | .NET Framework / WinForms, installed at the customer | CCA9 |
| Web applications | Web interfaces, either an add-on to CCA9 or standalone | CCAOnline |
Where Does the Documentation Live?​
Application-specific documentation MUST live in that repository under docs/. Anything
spanning several applications belongs here — see DOCUMENTATION-GUIDELINES.md in the
repository root.