---
id: context
title: "Context"
description: "See the governance channel, project sessions, 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, user experience, 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** 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.

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.