1.5 KiB
title, sidebar_position
| title | sidebar_position |
|---|---|
| Maze Next Gen Team | 2 |
Maze Next Gen Team
| Field | Value |
|---|---|
| Status | Active |
| Lead | RootAtSkic |
| Members | RootAtSkic; Jenny; Piotras; jarvis-at-skic / Hermes code agent |
| Assigned project | Maze Next Gen |
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 (team 29) and corp-v1-mazeng-skills-code-agent (team 31), includes all repositories, and contains root-at-skic, jarvis-at-skic, and piotras. Jarvis's verified memberships cover two project repositories and fourteen project-skill repositories, and its Discord view, send, and history access passes across all seven lifecycle channels. Piotras's memberships are also verified. Jenny has verified Discord access, but her Gitea team access remains pending a verified username or account creation; no identity was guessed.
Communication
Seven exact Maze channels exist in dedicated category corp-v1-mazeng (1542627645441839174) in lifecycle order. Channel IDs, permission overwrites, history, purpose messages, and pinned guidance remain attached to the moved channels; Hermes read access was reverified after migration.
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.