30 lines
1.0 KiB
Markdown
30 lines
1.0 KiB
Markdown
---
|
|
title: Maze Next Gen Team
|
|
sidebar_position: 2
|
|
---
|
|
|
|
# Maze Next Gen Team
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Status | Active |
|
|
| Lead | RootAtSkic |
|
|
| Technical member | `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 members across two project and thirteen skill repositories.
|
|
|
|
## Communication
|
|
|
|
Six exact Maze channels, purpose messages, pinned guidance, and six isolated staggered hourly synchronization jobs are verified.
|
|
|
|
## 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.
|