Parent folderOpen Confluence

RWS Architecture article

Git

Git is the product-neutral architecture building block for source-control capability for DC 3.0 services. It states what DC 3.0 needs from this capability before a concrete SBB, pr

  1. Typeabb
  2. Statuscandidate
  3. Domainplatform
On this page
  1. ABB Git
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB Git

Summary

Git is the product-neutral architecture building block for source-control capability for DC 3.0 services. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides source-control capability for DC 3.0 services.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the platforms ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • The implementing SBB must define ownership, support boundaries, lifecycle policy, security controls, and acceptance criteria before selection.
  • The solution must remain traceable to this ABB and to the decisions that approve its implementation pattern.

Service Description

This ABB offers a product-neutral Git service that defines what solution building blocks must deliver for the platforms domain. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for Git.
  • MVP: validate the mapped SBB implementation and record the selected support and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud and central DC 3.0 landing zone for core infrastructure and platform services.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • Service catalog or request workflow for governed consumption.
  • Identity, audit, policy, monitoring, and automation interfaces.
  • Operational telemetry and evidence interfaces for service management.

Dependencies

  • Depends on automation for a supporting capability or integration boundary.
  • Depends on federated-authentication for a supporting capability or integration boundary.
  • Implemented by gitlab as currently mapped SBB traceability.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • forgejo - Forgejo is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.
  • gitlab - GitLab is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.