---
title: DPVP Team
sidebar_position: 5
description: "Identify the DPVP team, mandate, verified access, and remaining kickoff gates."
---

# DPVP Team

| Field | Value |
|---|---|
| Status | Kickoff in progress |
| Lead | RootAtSkic |
| Members | RootAtSkic; Linas; `jarvis-at-skic` / Hermes executing code agent |
| Assigned project | [Debesijos paslaugų valdymo platforma](/projects/dpvp/) |

## Mandate

Deliver the governed DPVP experience for VSSA Operator organization and project onboarding, its architecture baseline, documentation, and project-scoped engineering practices.

## Access

- Discord: all seven DPVP lifecycle channels exist; Jarvis view, send, and history permissions are verified.
- Gitea project team: `dpvp-maintainers` (`45`) in `corp-v1-dpvp`; includes all repositories and contains verified user `jarvis-at-skic`.
- Gitea skills team: `dpvp-skill-maintainers` (`47`) in `corp-v1-dpvp-skills-code-agent`; includes all repositories and contains verified user `jarvis-at-skic`.
- RootAtSkic and Linas Gitea team assignment remains part of the incomplete DPVP kickoff; this membership change did not alter their access.

## Communication

Use the exact lifecycle order: General, Scope, Architecture, UI/UX, Kanban, Delivery, and Releases. Jira originates, assigns, and approves organization/project changes; the portal guides the VSSA Operator and records verified outcomes.