---
id: overview-repositories
title: "Overview Repositories"
description: "See how each Corp v1 project separates application and documentation source from adopted skills and delivery evidence."
---

import Drawio from '@theme/Drawio';
import repositoriesDiagram from '!!raw-loader!./diagrams/repositories.drawio';

# Overview Repositories

Each project has two Gitea organization boundaries and fifteen required repositories: two project repositories plus thirteen adopted skill repositories.

<Drawio content={repositoriesDiagram} title="Corp v1 organizations, repositories, and delivery" toolbar="zoom layers lightbox" responsive maxHeight={720} />

## Project organization: `corp-v1-<code>`

| Repository | Purpose |
|---|---|
| `corp-v1-<code>-documentation` | Docusaurus project portal, governed records, and editable Draw.io architecture sources |
| `corp-v1-<code>` | pnpm/TypeScript application monorepo with `applications/`, `packages/`, Docker, Helm, Taskfiles, and GitOps inputs |

A project team grants access to both repositories. Project-specific environment variables use `CORP_V1_<CODE>_*`.

## Skills organization: `corp-v1-<code>-skills-code-agent`

The corresponding skills team grants access to:

- six adopted channel-skill repositories;
- seven adopted engineering-skill repositories;
- their complete supporting assets, scripts, templates, references, and preserved adoption history.

The global `drawio-main` and `corp-v1--glossary` remain shared references unless an explicit project decision adopts a local copy.

## Delivery evidence

Documentation commits are validated and published to LEGO Cloud Pages. Deployable application commits produce immutable Harbor images and update GitOps/Argo CD desired state. Completion requires exact-commit CI plus deployed page or runtime readback; a local build or accepted push alone is not delivery evidence.