Onboarding Your Team

Use the Nomos Agent to submit a structured onboarding request. It validates team data and proposes changes through pull requests in the repositories that own each capability.

Ready to go?

You have your team's details and want to build a prompt to paste straight into the Nomos Agent.

Build your agent prompt →

How It Works

Collect your details

Gather the team key, display name, purpose, GitHub usernames, and administrator email.

Build your prompt

Use the prompt builder below, then paste the generated text straight into the Nomos Agent.

Review and promote

Review the proposed pull request. Logos creates the team foundation; optional Corpus or Pneuma changes follow their own promotion workflows.

Build Your Agent Prompt

You have all the details

Fill in the form, select Copy, and paste the result into Nomos. The agent confirms the requested scope and opens the required pull request or pull requests. Toggle Optional for cloud, workflow, database, and Kubernetes capabilities.

Required (8)

Optional (8)

General

Team key

Team key. Must match the team_type prefix scheme: pt- (platform), st- (stream-aligned), ct- (complicated-subsystem), et- (enabling).

Display name

Team display name. Title Case; spaces and the lowercase word "and" are allowed.

Description required

Inline comment rendered after display_name in the tfvars file. Used for the team etymology blurb. Also used as the `description` frontmatter on the team's docs index page; render_team_docs_index and open_team_docs_pr require this field to be non-empty — an empty string will produce a docs_input_invalid error.

GitHub

Maintainers required

GitHub parent team memberships. All team members should be listed here. Use GitHub usernames (NOT email addresses).

Use these maintainers for all four required child teams

GitHub child team memberships. The four standard teams are required for every team, and every standard or custom child team must have at least one maintainer.

Google group ownership

Owners for every basic group in all environments required

Per-environment Google Cloud Identity basic groups: admin, reader, writer. Every role/environment group requires at least one owner. Binds each role directly to environment folders — no team-folder binding, no inheritance.

authentik and OpenBao

OpenBao administrators in every environment required

OpenBao secret administrator group with at least one member in each deployment environment.

Datadog

Admin email required

Datadog team memberships. At least one team admin is required; admins manage the team. Ordinary members have read-only access and may be empty.

Generated prompt

Onboard a new team.


Declare openbao-secret-readers and openbao-secret-writers with empty memberships in every environment. Logos supplies their fixed labels and descriptions.

How to Invoke the Agent

Copilot CLI

With Docker available, install the plugin, set NOMOS_GITHUB_TOKEN, and start Copilot CLI:

copilot plugin marketplace add osinfra-io/pt-ai-plugins
copilot plugin install techne-agents@osinfra-io
printf 'NOMOS_GITHUB_TOKEN: '
read -rs NOMOS_GITHUB_TOKEN
printf '\n'
export NOMOS_GITHUB_TOKEN
copilot --enable-all-github-mcp-tools

Type /agent, select Nomos Agent, and paste your prompt. The plugin registers its version-pinned MCP server automatically.

GitHub UI

Navigate to pt-techne-agents/agents on GitHub, select the Nomos Agent, and paste your prompt. The agent opens a PR automatically.

VS Code

Open pt-techne-agents in VS Code, start a Copilot Chat session, type /agent, select Nomos Agent, and paste your prompt.

GitHub access

The agent opens pull requests through the GitHub MCP server. In Copilot CLI, start with --enable-all-github-mcp-tools so write tools are available; no separate GitHub token is needed. NOMOS_GITHUB_TOKEN above is only for the Nomos plugin's own MCP server.