docs: complete E-Shop v1 governance records
Build and publish Corp v1 Board portal / build (pull_request) Successful in 34s
Build and publish Corp v1 Board portal / build (pull_request) Successful in 34s
This commit is contained in:
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: E-Shop v1 Team
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
# E-Shop v1 Team
|
||||
|
||||
| Field | Value |
|
||||
|---|---|
|
||||
| Status | Active |
|
||||
| Lead | RootAtSkic |
|
||||
| Members | RootAtSkic; `jarvis-at-skic` / Hermes code agent |
|
||||
| Assigned project | [E-Shop v1](/projects/eshopv1/) |
|
||||
|
||||
## Mandate
|
||||
|
||||
Deliver the governed E-Shop v1 toothbrush-commerce MVP, its source-evidence catalog, PayPal Sandbox boundary, documentation, CI, deployment assets, and release evidence.
|
||||
|
||||
## Gitea access
|
||||
|
||||
`e-shop-v1-team` exists independently in `corp-v1-eshopv1` and `corp-v1-eshopv1-skills-code-agent`. Both teams include all repositories, grant per-unit write access, and contain verified users `root-at-skic` and `jarvis-at-skic`.
|
||||
|
||||
## Communication and autonomy
|
||||
|
||||
Seven exact E-Shop v1 lifecycle channels and their pinned purpose/skill guidance are verified. One project-specific 30-minute General job is authorized under `ESHOPV1-BOOTSTRAP-AUTONOMY-20260826`; its authority ends at the first human-authored project-channel message.
|
||||
|
||||
## Remaining gates
|
||||
|
||||
Harbor image publication waits for organization secret name `HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET`, entered directly in Gitea. PayPal remains Sandbox-only and requires environment-injected credentials for an end-to-end capture test. Neither secret value may be sent to Hermes or Discord.
|
||||
@@ -10,5 +10,6 @@ sidebar_position: 1
|
||||
|---|---|---|---:|---:|
|
||||
| [AeroSim Team](/teams/aerosim/) | Active | RootAtSkic | 8 | 1 |
|
||||
| [Maze Next Gen Team](/teams/mazeng/) | Active | RootAtSkic | 4 | 1 |
|
||||
| [E-Shop v1 Team](/teams/eshopv1/) | Active | RootAtSkic | 2 | 1 |
|
||||
|
||||
A team record defines its mandate, lead, members, responsibilities, communication channels, and assigned projects.
|
||||
|
||||
Reference in New Issue
Block a user