---
title: Maze Next Gen Team
sidebar_position: 2
---

# Maze Next Gen Team

| Field | Value |
|---|---|
| Status | Active |
| Lead | RootAtSkic |
| Members | RootAtSkic; Jenny; `jarvis-at-skic` / Hermes code agent |
| Assigned project | [Maze Next Gen](/projects/mazeng/) |

## Mandate

Deliver the Maze Next Gen multi-cloud inventory and visualization platform, documentation, and project-scoped engineering practices.

## Gitea access

`maze-next-gen-team` exists independently in `corp-v1-mazeng` and `corp-v1-mazeng-skills-code-agent`, includes all repositories, and contains `root-at-skic` and `jarvis-at-skic`. Effective write access is verified for both existing Gitea members across two project and thirteen skill repositories. Jenny's repository access is pending until she signs in to Gitea at least once and supplies a verified username.

## Communication

Six exact Maze channels and their purpose messages and pinned guidance are verified. Jenny has effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access in all six. The membership update was announced in General as message `1540048213090771034`. Corp v1 project scheduler jobs are prohibited by the current operating model.

## Remaining gate

Harbor-dependent publication waits only for organization secret name `HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET`; members must enter its value directly in Gitea and never send it to Hermes.