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 →

🔐

Kryptos

OpenBao runtime, secrets policy, authentication, and secret-engine lifecycle.

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 → Kryptos. Kryptos depends on Pneuma for runtime but exposes secrets services back to all teams. Arche, Ekklesia, and Techne are shared capabilities used across the grouping.

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