jarvis-at-skic
cc3f461899
Build and publish Corp v1 Board portal / build (pull_request) Successful in 43s
61 lines
3.2 KiB
Markdown
61 lines
3.2 KiB
Markdown
---
|
|
title: Debesijos paslaugų valdymo platforma
|
|
sidebar_position: 5
|
|
description: "Track the DPVP kickoff, team, access, resources, and remaining provisioning gates."
|
|
---
|
|
|
|
# Debesijos paslaugų valdymo platforma
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Code | `dpvp` |
|
|
| Status | Kickoff in progress — repositories, adopted skills, and deployed documentation pending |
|
|
| Started | 2026-09-02 |
|
|
| Sponsor and accountable lead | RootAtSkic |
|
|
| Members | RootAtSkic; Linas; `jarvis-at-skic` / Hermes executing code agent; `friday-at-skic` / Friday code agent |
|
|
| Team | [DPVP Team](/teams/dpvp/) |
|
|
| Visibility | Restricted |
|
|
|
|
## Purpose
|
|
|
|
Guide the VSSA Operator through governed cloud-service organization and project lifecycle management, with Jira as the system of record for originating, assigning, and approving organization and project changes.
|
|
|
|
## Initial deliverable
|
|
|
|
Deployed project documentation and an architecture baseline for the VSSA Operator organization/project onboarding journey, without a placeholder application.
|
|
|
|
## Discord
|
|
|
|
Dedicated category `corp-v1-dpvp` (`1544621887844388965`) contains exactly seven lifecycle channels:
|
|
|
|
1. `corp-v1-dpvp-general` — `1544621890994184224`
|
|
2. `corp-v1-dpvp-scope` — `1544621895159255040`
|
|
3. `corp-v1-dpvp-architecture` — `1544621899370340362`
|
|
4. `corp-v1-dpvp-ui-ux` — `1544621902142771250`
|
|
5. `corp-v1-dpvp-kanban` — `1544621905494016080`
|
|
6. `corp-v1-dpvp-delivery` — `1544621909176746005`
|
|
7. `corp-v1-dpvp-releases` — `1544621912385130556`
|
|
|
|
Jarvis (`discord:1526860732917088266`) has verified effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access in every channel through its administrator role. Purpose guidance exists in all seven channels, and the General introduction is pinned as message `1544622184582877245`.
|
|
|
|
## Gitea
|
|
|
|
- Project organization: [corp-v1-dpvp](https://gitea.lego-cloud.eu/corp-v1-dpvp) — private; created and verified 2026-09-05.
|
|
- Skills/code-agent organization: [corp-v1-dpvp-skills-code-agent](https://gitea.lego-cloud.eu/corp-v1-dpvp-skills-code-agent) — private; created and verified 2026-09-05.
|
|
- Project team: `dpvp-maintainers` (`45`) — includes all repositories; `jarvis-at-skic` verified.
|
|
- Skills team: `dpvp-skill-maintainers` (`47`) — includes all repositories; `jarvis-at-skic` verified.
|
|
- Friday's Gitea account `friday-at-skic` is verified in both teams. The teams currently cover no repositories, and Friday's account activation remains pending.
|
|
|
|
## Approval
|
|
|
|
RootAtSkic requested the DPVP kickoff in Board message `1544616064162463854`; the dedicated Discord workspace was subsequently provisioned. RootAtSkic approved Jarvis's Board and all-project membership in Board message `1545759332845490208` on 2026-09-05.
|
|
|
|
## Outstanding gates
|
|
|
|
1. Create and assign the two required DPVP project repositories.
|
|
2. Adopt and verify the fourteen project-scoped skill repositories.
|
|
3. Configure the approved non-secret Harbor variables and validate only the required secret name's presence.
|
|
4. Build, publish, and read back the DPVP documentation site.
|
|
5. Complete project documentation and application kickoff acceptance without creating a placeholder application.
|
|
6. Add RootAtSkic and Linas to both Gitea teams after confirming the intended team permissions and Linas account activation state.
|