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

docs: establish Corp v1 Guild architecture
Build and publish Corp v1 Board portal / build (pull_request) Successful in 34s
Details

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-27 18:19:03 +00:00
parent fdc366c7dc
commit 6c9b399043
9 changed files with 155 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture-high-level/operating-model.mdx
+10 -9
View File
@@ -1,7 +1,7 @@
---
id: operating-model
title: "Operating Model"
description: "Follow the single-agent, multi-session Corp v1 pilot from Board governance through design, delivery, release, and verified evidence."
description: "Follow Corp v1 from Board governance and Guild improvement through project delivery and verified evidence."
---
import Drawio from '@theme/Drawio';
@@ -16,14 +16,15 @@ Corp v1 is an SDLC operating-model pilot: **one AI agent works across multiple f
## How the setup fits together
1. **`corp-v1-board` governs the portfolio.** Listed Board members approve project kickoffs, closures, membership changes, and changes to the global operating model.
2. **General establishes the project workspace.** It handles onboarding, shared coordination, questions, and broadcasts verified outcomes.
3. **Scope decides what creates value.** Ideas become Epics and Features; a human project member approves an exact Feature for solution work.
4. **Architecture decides how the system should work.** Requirements, ADRs, interfaces, constraints, and implementation Tasks become durable project evidence.
5. **UI/UX makes the frontend experience implementable.** User journeys, information architecture, accessibility, Penpot designs, prototypes, and handoff evidence bridge Architecture and execution.
6. **Kanban controls admission and flow.** A human project member admits an exact Task to Focus before Delivery may execute it.
7. **Delivery produces a reviewed candidate.** Work proceeds through branches, pull requests, exact-head validation, and reviewable implementation evidence.
8. **Releases control deployment and outcomes.** Immutable artifacts, risk, rollback, deployment, acceptance, and post-release evidence are assessed explicitly.
9. **Verification closes the evidence loop.** Hermes reads the deployed page or runtime back, updates project documentation and the Board portal, and reports remaining gates honestly.
2. **`corp-v1-guild` improves the operating system.** RootAtSkic and Hermes identify recurring cross-channel friction, inventory affected skills and repositories, route decisions to their owners, and verify coordinated rollout without replacing Board or project authority.
3. **General establishes the project workspace.** It handles onboarding, shared coordination, questions, and broadcasts verified outcomes.
4. **Scope decides what creates value.** Ideas become Epics and Features; a human project member approves an exact Feature for solution work.
5. **Architecture decides how the system should work.** Requirements, ADRs, interfaces, constraints, and implementation Tasks become durable project evidence.
6. **UI/UX makes the frontend experience implementable.** User journeys, information architecture, accessibility, Penpot designs, prototypes, and handoff evidence bridge Architecture and execution.
7. **Kanban controls admission and flow.** A human project member admits an exact Task to Focus before Delivery may execute it.
8. **Delivery produces a reviewed candidate.** Work proceeds through branches, pull requests, exact-head validation, and reviewable implementation evidence.
9. **Releases control deployment and outcomes.** Immutable artifacts, risk, rollback, deployment, acceptance, and post-release evidence are assessed explicitly.
10. **Verification closes the evidence loop.** Hermes reads the deployed page or runtime back, updates project documentation and the Board portal, and reports remaining gates honestly.
## Why sessions and skills are separated