corp-v1/portal
2
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

docs: explain Corp v1 SDLC and rebuild diagrams
Build and publish Corp v1 Board portal / build (pull_request) Successful in 36s
Details

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-25 19:45:33 +00:00
parent 1881254315
commit 17e09ee8ec
9 changed files with 165 additions and 186 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture-high-level/overview-repositories.mdx
+3 -3
View File
@@ -9,7 +9,7 @@ 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.
Each project has two Gitea organization boundaries and sixteen required repositories: two project repositories plus fourteen adopted skill repositories.
<Drawio content={repositoriesDiagram} title="Corp v1 organizations, repositories, and delivery" toolbar="zoom layers lightbox" responsive maxHeight={720} />
@@ -26,7 +26,7 @@ A project team grants access to both repositories. Project-specific environment
The corresponding skills team grants access to:
- six adopted channel-skill repositories;
- seven adopted channel-skill repositories—General, Scope, Architecture, UI/UX, Kanban, Delivery, and Releases;
- seven adopted engineering-skill repositories;
- their complete supporting assets, scripts, templates, references, and preserved adoption history.
@@ -34,4 +34,4 @@ The global `drawio-main` and `corp-v1--glossary` remain shared references unless
## 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.
Documentation commits are validated by Gitea Actions 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.