1.9 KiB
title, sidebar_position
| title | sidebar_position |
|---|---|
| Maze Next Gen | 2 |
Maze Next Gen
| Field | Value |
|---|---|
| Code | mazeng |
| Status | Provisioning |
| Approved | 2026-08-17 |
| Sponsor and accountable lead | RootAtSkic |
| Initial technical member | jarvis-at-skic / Hermes code agent |
| Team | Maze Next Gen Team |
Purpose
Rebuild Maze as a multi-cloud inventory and visualization platform that connects to major hyperscalers, discovers organizations' services and resources, versions normalized inventory, and presents each organization's cross-cloud estate as navigable diagrams.
Initial deliverable
A governed discovery MVP for one organization and one initial hyperscaler that uses read-only provider access, inventories selected cloud containers and resources, stores normalized timestamped snapshots, displays version changes, provides an organization-scoped UI, renders an interactive estate diagram, and establishes provider-adapter contracts for later hyperscalers.
Approved kickoff scope
- Exactly six same-project Discord channels under
corp-v1. - Dedicated project and skills/code-agent Gitea organizations.
- Application and documentation repositories.
- Seven adopted engineering skills and six adopted channel skills.
- Six staggered hourly synchronization jobs.
- Global
drawio-mainreference; no project copy. - Project organization Harbor variables and secret-name-only validation.
Approval evidence
RootAtSkic (discord:1518725627845283888) explicitly approved the updated proposal in Board message 1539019060770242611 on 2026-08-17.
Provisioning status
Resource IDs, repository SHAs, CI tasks, Pages evidence, job IDs, and remaining gates will be added after independent remote verification. The first hyperscaler and exact inventory scope remain product Features to be decided through the project lifecycle rather than assumed at kickoff.