docs: approve Maze Next Gen kickoff
Build and publish Corp v1 Board portal / build (push) Successful in 35s
Build and publish Corp v1 Board portal / build (push) Successful in 35s
This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Maze Next Gen kickoff
|
||||
---
|
||||
|
||||
# Maze Next Gen kickoff — 2026-08-17
|
||||
|
||||
## Context
|
||||
|
||||
RootAtSkic proposed rebuilding Maze as a governed multi-cloud inventory and visualization platform. The proposal was refreshed to the current six-channel and thirteen-skill Corp v1 model.
|
||||
|
||||
## Decision
|
||||
|
||||
Begin provisioning **Maze Next Gen**, code `mazeng`, as a restricted Corp v1 project with RootAtSkic as sponsor and accountable lead and Hermes (`jarvis-at-skic`) as the initial technical member.
|
||||
|
||||
Approval was explicit from Board member `discord:1518725627845283888` in message `1539019060770242611`.
|
||||
|
||||
## Authorized resources
|
||||
|
||||
- Exactly six same-project Discord channels under `corp-v1`: General, Scope, Architecture, Kanban, Delivery, and Releases.
|
||||
- `corp-v1-mazeng` project organization.
|
||||
- `corp-v1-mazeng-skills-code-agent` skills organization.
|
||||
- Application and documentation repositories.
|
||||
- Seven adopted engineering skills and six adopted channel skills, all suffixed `--mazeng`.
|
||||
- Six same-project staggered hourly synchronization jobs.
|
||||
- Corresponding project and skills organization teams for RootAtSkic and `jarvis-at-skic`.
|
||||
- Two approved non-secret Harbor organization variables and secret-name-only validation.
|
||||
- Global `home-v1-skills-code-agent/drawio-main` reference without a project copy.
|
||||
|
||||
## Initial deliverable
|
||||
|
||||
A governed discovery MVP for one organization and one initial hyperscaler using read-only credentials, normalized timestamped inventory snapshots, version change visibility, an organization-scoped UI, interactive estate diagrams, and extensible provider-adapter contracts.
|
||||
|
||||
The first hyperscaler and exact inventory scope are not pre-approved implementation choices; they must be proposed and decided through the project lifecycle.
|
||||
|
||||
## Owner
|
||||
|
||||
RootAtSkic
|
||||
|
||||
## Current state
|
||||
|
||||
Approved and provisioning. Completion evidence and any remaining gates will be appended after remote verification.
|
||||
Reference in New Issue
Block a user