docs: add high-level Corp v1 architecture
Build and publish Corp v1 Board portal / build (pull_request) Successful in 38s
Build and publish Corp v1 Board portal / build (pull_request) Successful in 38s
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
---
|
||||
id: context
|
||||
title: "Context"
|
||||
description: "See the people, collaboration systems, repositories, and delivery platforms around the Corp v1 operating model."
|
||||
---
|
||||
|
||||
import Drawio from '@theme/Drawio';
|
||||
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.
|
||||
|
||||
<Drawio content={contextDiagram} title="Corp v1 operating context" toolbar="zoom layers lightbox" responsive maxHeight={720} />
|
||||
|
||||
## System boundary
|
||||
|
||||
The operating model joins four evidence-bearing environments:
|
||||
|
||||
- **Discord** routes work into six project channels with distinct concerns.
|
||||
- **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.
|
||||
Reference in New Issue
Block a user