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/context.mdx
+6 -4
View File
@@ -1,7 +1,7 @@
---
id: context
title: "Context"
description: "See the people, collaboration systems, repositories, and delivery platforms around the Corp v1 operating model."
description: "See the governance channel, project sessions, repositories, and delivery platforms around the Corp v1 operating model."
---
import Drawio from '@theme/Drawio';
@@ -9,7 +9,7 @@ import contextDiagram from '!!raw-loader!./diagrams/context.drawio';
# Context
Corp v1 is the **governed operating model for project delivery**. It is not an application runtime architecture. The Board supplies lifecycle authority and shared guardrails; project teams retain ownership of their scope, architecture, implementation, and release outcomes.
Corp v1 is the **governed operating model for project delivery**. It is not an application runtime architecture. The Board supplies lifecycle authority and shared guardrails; project teams retain ownership of their scope, architecture, user experience, implementation, and release outcomes.
<Drawio content={contextDiagram} title="Corp v1 operating context" toolbar="zoom layers lightbox" responsive maxHeight={720} />
@@ -17,9 +17,11 @@ Corp v1 is the **governed operating model for project delivery**. It is not an a
The operating model joins four evidence-bearing environments:
- **Discord** routes work into six project channels with distinct concerns.
- **Discord** provides one `corp-v1-board` governance channel and seven focused channels per project.
- **Gitea** preserves decisions, documentation, application source, adopted skills, pull requests, and CI evidence.
- **Delivery platforms** publish documentation through LEGO Cloud Pages and applications through Harbor plus GitOps/Argo CD.
- **This Board portal** records project, team, member, repository, lifecycle, and verification state.
The model does not approve a project's target solution architecture. Each project must separately record its approved context, containers, requirements, decisions, and implementation Tasks.
One Hermes agent operates across multiple channel sessions. Project-adopted skills define each session's concern, approval rules, evidence requirements, and handoffs while preventing one project's decisions from silently changing another.
The model does not approve a project's target solution architecture. Each project must separately record its approved context, containers, requirements, decisions, UI/UX evidence, and implementation Tasks.