jarvis-at-skic
a7951c6130
Build and publish Corp v1 Board portal / build (pull_request) Successful in 36s
45 lines
3.1 KiB
Plaintext
45 lines
3.1 KiB
Plaintext
---
|
|
id: context
|
|
title: "Context"
|
|
description: "See the Corp v1 home-lab system boundary, its human actors, and its only external systems: the LLM provider and Discord."
|
|
---
|
|
|
|
import Drawio from '@theme/Drawio';
|
|
import contextDiagram from '!!raw-loader!./diagrams/context.drawio';
|
|
|
|
# Context
|
|
|
|
The target system is the **Corp v1 managed delivery platform in Lego's home lab**. The boundary follows operational responsibility: services and managed service slices that Lego deploys, configures, versions, upgrades, secures, or restores are inside the Corp v1 system boundary.
|
|
|
|
<Drawio content={contextDiagram} title="Corp v1 home-lab system context" toolbar="zoom layers lightbox" responsive maxHeight={760} />
|
|
|
|
## Human actors
|
|
|
|
| Actor | Relationship to Corp v1 |
|
|
|---|---|
|
|
| **Corp v1 Board members** | Govern the portfolio and approve project lifecycle, membership, the global operating model, and central channel-reference changes. |
|
|
| **Project leads and contributors** | Define value, approve solution work and Task admission, review architecture and UI/UX, implement changes, and accept releases. |
|
|
| **Prospective project sponsors and contributors** | May request or join future Corp v1 projects after explicit Board approval and onboarding. |
|
|
| **Solution users and reviewers** | Provide needs, usability feedback, acceptance observations, and evidence about the products delivered through Corp v1. |
|
|
|
|
Human authority remains outside automation. Hermes, CI, deployments, inferred intent, and silence never substitute for an approval reserved to a listed person.
|
|
|
|
## External systems
|
|
|
|
Corp v1 currently has only two external software systems:
|
|
|
|
| External system | Relationship to Corp v1 |
|
|
|---|---|
|
|
| **LLM Provider** | Supplies model inference to Hermes Agent. The currently used providers are ICA or GPT Codex. Model execution is consumed as an external capability; Corp v1 does not deploy or maintain the provider platform. |
|
|
| **Communication Service — Discord** | Carries Board governance and project conversations. Corp v1 configures and maintains its channel structure, permissions, guidance, and pins, while Discord operates the communication platform itself. |
|
|
|
|
## Inside the system boundary
|
|
|
|
Hermes Agent and the home-lab services it depends on are internal containers in this architecture: Gitea, Actions runners, Penpot, the Board portal, Pages, Harbor, Argo CD, the access and identity stack, MicroK8s, and the hosted workloads. Their Corp v1 configuration is not modeled as an external dependency because Lego is responsible for its lifecycle and operational state.
|
|
|
|
The [Container Overview](/architecture-high-level/overview/) shows those internal containers and their delivery relationships. The [Operating Model](/architecture-high-level/operating-model/) separately explains Board authority, channel sessions, skills, approvals, and handoffs.
|
|
|
|
## Product boundary
|
|
|
|
A project product delivered through Corp v1 remains its own product boundary. Corp v1 operates the delivery platform and governs the lifecycle, while every project must maintain its own product context, requirements, architecture, data, security, UI/UX, and release decisions.
|