Platform Grouping

The platform grouping is the set of platform teams that together provide the internal platform. Each team owns a distinct context; together they expose a single, coherent interface to the teams that use the platform: the Nomos Agent. This section documents how each team's capability is built and operated. Teams using the platform should start with Getting Started instead.

Teams

Logos

Team structure, identity, repositories, and organization governance.

Learn more →

Corpus

GCP projects, networking, DNS, registries, state, and managed data foundations.

Learn more →

Pneuma

Managed GKE runtime, service mesh, gateway authentication, certificates, policy, and telemetry.

Learn more →

Arche

Reusable OpenTofu modules used to implement consistent platform capabilities.

View modules →

Ekklesia

Customer-facing platform documentation and contribution standards.

Learn more →

Techne

Reusable workflows, hooks, development environments, agents, and platform tooling.

Learn more →

Team context

Each team owns a distinct context with explicit upstream/downstream relationships.

Team dependencies

The deployment supply chain is Logos → Corpus → Pneuma. Pneuma supplies runtime and platform services, including secrets, to all teams. Arche, Ekklesia, and Techne are shared capabilities used across the grouping.

Shared capabilities

Arche

Reusable infrastructure modules

Ekklesia

Platform documentation

Techne

Workflows and tooling

Support the deployment chain

Deployment supply chain

1. Logos

   Team structure and identity
2. Corpus

   Projects and cloud foundations
3. Pneuma

   Runtime and platform services

Runtime and platform services, including secrets — from Pneuma

All teams

Consume the runtime and platform services.

Documentation and tooling also reach all teams directly from Ekklesia and Techne.

Interaction modes, cognitive load, staffing, and the innersource model are in the Operating Model.