diff --git a/docs/architecture-high-level/diagrams/channels.drawio b/docs/architecture-high-level/diagrams/channels.drawio
index c9d1fb3..8f78761 100644
--- a/docs/architecture-high-level/diagrams/channels.drawio
+++ b/docs/architecture-high-level/diagrams/channels.drawio
@@ -1,62 +1,76 @@
-
-
+
+
-
-
-
-
+
+
+
+
-
-
+
+
-
-
+
+
+
+
+
-
+
-
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
-
-
-
-
-
-
+
-
+
-
+
-
+
\ No newline at end of file
diff --git a/docs/architecture-high-level/diagrams/skills.drawio b/docs/architecture-high-level/diagrams/skills.drawio
index 269ebe2..922e8e3 100644
--- a/docs/architecture-high-level/diagrams/skills.drawio
+++ b/docs/architecture-high-level/diagrams/skills.drawio
@@ -2,21 +2,45 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
+
\ No newline at end of file
diff --git a/docs/architecture-high-level/operating-model.mdx b/docs/architecture-high-level/operating-model.mdx
index 75a19d9..c985580 100644
--- a/docs/architecture-high-level/operating-model.mdx
+++ b/docs/architecture-high-level/operating-model.mdx
@@ -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
diff --git a/docs/architecture-high-level/overview-channels.mdx b/docs/architecture-high-level/overview-channels.mdx
index f8d38a9..82d0ffa 100644
--- a/docs/architecture-high-level/overview-channels.mdx
+++ b/docs/architecture-high-level/overview-channels.mdx
@@ -1,7 +1,7 @@
---
id: overview-channels
title: "Overview Channels"
-description: "Understand the Corp v1 Board channel, seven project workspaces, session boundaries, skills, and SDLC handoffs."
+description: "Understand the Corp v1 Board and Guild channels, seven project workspaces, session boundaries, skills, and SDLC handoffs."
---
import Drawio from '@theme/Drawio';
@@ -9,9 +9,15 @@ import channelsDiagram from '!!raw-loader!./diagrams/channels.drawio';
# Overview Channels
-Corp v1 uses **one portfolio-governance channel** and **seven purpose-specific channels per project**. These are operating boundaries for one AI agent and the human team—not separate delivery teams.
+Corp v1 uses **two central portfolio workspaces** and **seven purpose-specific channels per project**. The central Board and Guild channels serve different purposes; neither is an eighth project channel. All channels are operating boundaries for one AI agent and the human team—not separate delivery teams.
-
+
+
+## Improvement coordination: `corp-v1-guild`
+
+`corp-v1-guild` is the shared improvement workspace for RootAtSkic and Hermes. It correlates recurring friction across Corp v1 channels, skills, reference skills, repositories, and this portal; inventories the affected owners; and coordinates a verified rollout.
+
+The Guild does not grant approval that belongs to the Board or a project channel. It routes product, architecture, design, flow, implementation, and release decisions back to their owning project workspace. Its authoritative operating skill is [`corp-v1--guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--guild).
## Portfolio governance: `corp-v1-board`
diff --git a/docs/architecture-high-level/overview-skills.mdx b/docs/architecture-high-level/overview-skills.mdx
index 9134eca..085f045 100644
--- a/docs/architecture-high-level/overview-skills.mdx
+++ b/docs/architecture-high-level/overview-skills.mdx
@@ -20,6 +20,7 @@ The central sources live in [`home-v1-skills-code-agent`](https://gitea.lego-clo
| Skill | Purpose |
|---|---|
| [`corp-v1--main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main) | Board authority, project lifecycle, resource model, membership, adoption, publication, and verification rules. |
+| [`corp-v1--guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--guild) | Cross-channel improvement intake, impact inventory, ownership routing, coordinated rollout, and convergence verification. |
| [`corp-v1--glossary`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--glossary) | Shared terminology and rules for keeping canonical definitions in project documentation. |
| [`corp-v1-channel-general`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-general) | Onboarding, coordination, questions, and outcome broadcasts. |
| [`corp-v1-channel-scope`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-scope) | Ideas, Epics, Features, value, acceptance outcomes, and human solution approval. |
@@ -38,6 +39,8 @@ Every project owns fourteen adopted repositories in `corp-v1--skills-code-
A project adoption records the central source branch and commit, then adds the project code, repository links, environment namespace, approved authority, and operating lessons. Central updates are compared and adopted semantically; they never silently overwrite project-specific decisions or authorization overrides.
+`corp-v1--guild` remains central because it coordinates improvements across projects. It is not copied as a fifteenth project skill and does not replace any mapped project channel skill.
+
At runtime, a focused channel session loads its mapped project channel skill plus only the engineering or global skills needed for the current work.
## Mandatory engineering skills
diff --git a/docs/governance/decisions.md b/docs/governance/decisions.md
index 24eeb6e..a6b283e 100644
--- a/docs/governance/decisions.md
+++ b/docs/governance/decisions.md
@@ -8,6 +8,7 @@ sidebar_position: 2
| Date | Decision | Scope | Owner | Record |
|---|---|---|---|---|
+| 2026-08-27 | Establish the Corp v1 Guild improvement workspace, skill, Gitea source, and portal architecture representation | Corp v1 governance and operating-model improvement | RootAtSkic | [Corp v1 Guild establishment](/governance/decisions/corp-v1-guild-establishment/) |
| 2026-08-26 | Authorize E-Shop v1 kickoff, toothbrush-commerce MVP, and bounded bootstrap autonomy | E-Shop v1 | RootAtSkic | [E-Shop v1 kickoff and bootstrap autonomy](/governance/decisions/eshopv1-kickoff-bootstrap-autonomy/) |
| 2026-08-25 | Add Piotras to the Corp v1 Board and every active project | Corp v1 governance, AeroSim, Maze Next Gen | RootAtSkic | [Piotras Board and all-project membership](/governance/decisions/piotras-board-all-project-membership/) |
| 2026-08-20 | Add Jenny to the Corp v1 Board and every active project | Corp v1 governance, AeroSim, Maze Next Gen | RootAtSkic | [Jenny Board and all-project membership](/governance/decisions/jenny-board-all-project-membership/) |
diff --git a/docs/governance/decisions/corp-v1-guild-establishment.md b/docs/governance/decisions/corp-v1-guild-establishment.md
new file mode 100644
index 0000000..ad4f9a2
--- /dev/null
+++ b/docs/governance/decisions/corp-v1-guild-establishment.md
@@ -0,0 +1,41 @@
+---
+title: Corp v1 Guild Establishment
+---
+
+# Corp v1 Guild Establishment
+
+## Decision
+
+On 2026-08-27, RootAtSkic (`discord:1518725627845283888`) established `corp-v1-guild` as the central improvement workspace shared with Hermes.
+
+The approved implementation includes:
+
+- Discord channel `corp-v1-guild` (`1542596418215092264`) under the `corp-v1` category;
+- central operating skill `corp-v1--guild`;
+- private Gitea source repository [`home-v1-skills-code-agent/corp-v1--guild`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--guild) on default branch `test`;
+- runtime installation of the published skill;
+- Guild guidance linked and pinned in the channel;
+- Corp v1 portal architecture updates that distinguish Guild improvement coordination from Board governance and the seven project delivery channels.
+
+## Evidence
+
+The approving instruction is Discord message `1542596833266761748` in channel `1542596418215092264`. RootAtSkic requested a skill similar in durability to `corp-v1--main`, defined the channel's purpose as improvements across channels, their skills, and reference skills, and required both portal architecture and Gitea publication.
+
+## Authority boundary
+
+The Guild coordinates improvement discovery, impact inventory, ownership routing, implementation, rollout, and verification. It does not replace:
+
+- the Corp v1 Board for project lifecycle, membership, `corp-v1--main`, or central channel-reference approvals;
+- project Scope, Architecture, UI/UX, Kanban, Delivery, or Releases decisions;
+- preserved project-local authorization overrides;
+- repository validation, review, exact-head CI, deployed readback, or destructive-action safeguards.
+
+The Guild is a central portfolio workspace, not an eighth project channel and not an additional project-adopted skill.
+
+## Consequences
+
+1. Cross-cutting improvement work has one durable intake and coordination surface.
+2. Every material improvement records exact evidence, affected surfaces, owner, required approvals, rollout boundary, and verification.
+3. Central reference changes still follow Board approval and deliberate semantic adoption into every affected project copy.
+4. Portal architecture and channel guidance must remain synchronized with the Guild operating contract.
+5. No Guild or Corp v1 project scheduler job is created under the current model.
diff --git a/scripts/verify-portal.mjs b/scripts/verify-portal.mjs
index ba18415..73048f9 100644
--- a/scripts/verify-portal.mjs
+++ b/scripts/verify-portal.mjs
@@ -103,9 +103,13 @@ const architecturePages = {
for (const [name, page] of Object.entries(architecturePages)) {
assert.match(page, /!!raw-loader!\.\/diagrams\/.+\.drawio/, `${name} page must render an editable Draw.io source`);
}
-for (const term of ['seven channel skills', 'seven engineering skills', 'Gitea Actions', 'scheduler jobs', 'corp-v1-board', 'UI/UX', 'one AI agent', 'Hermes Agent', 'MicroK8s', 'Penpot', 'Argo CD', 'Harbor']) {
+for (const term of ['seven channel skills', 'seven engineering skills', 'Gitea Actions', 'scheduler jobs', 'corp-v1-board', 'corp-v1-guild', 'corp-v1--guild', 'UI/UX', 'one AI agent', 'Hermes Agent', 'MicroK8s', 'Penpot', 'Argo CD', 'Harbor']) {
assert.ok(Object.values(architecturePages).some((page) => page.includes(term)), `architecture explanation is missing: ${term}`);
}
+assert.match(architecturePages.channels, /two central portfolio workspaces/i, 'channels overview must distinguish Board and Guild as central workspaces');
+assert.match(architecturePages.channels, /neither is an eighth project channel/i, 'Guild must not be classified as an eighth project channel');
+assert.match(architecturePages.skills, /not copied as a fifteenth project skill/i, 'Guild must remain central rather than project-adopted');
+assert.doesNotMatch(architecturePages.channels, /one portfolio-governance channel/i, 'superseded single-central-workspace wording must not remain');
for (const term of ['Corp v1 Board members', 'Project leads and contributors', 'Prospective project sponsors and contributors', 'Solution users and reviewers']) {
assert.ok(architecturePages.context.includes(term), `system context is missing actor: ${term}`);
}
@@ -125,8 +129,8 @@ for (const [name, markers] of Object.entries({
'context.drawio': ['CORP V1 — HOME-LAB SYSTEM CONTEXT', 'HUMAN ACTORS', 'TARGET SYSTEM', 'EXTERNAL SYSTEMS · ONLY TWO', 'DISCORD', 'ICA OR GPT CODEX'],
'architecture-overview.drawio': ['CORP V1 — HOME-LAB CONTAINER OVERVIEW', 'EXTERNAL · DISCORD', 'EXTERNAL · LLM PROVIDER', 'INTERNAL CONTAINERS', 'GITEA ACTIONS RUNNERS', 'HARBOR', 'ARGO CD', 'GONDOR MICROK8S'],
'operating-model.drawio': ['CORP V1 — OPERATING MODEL FLOW', 'CORP-V1-BOARD', 'BOARD APPROVAL', 'UI/UX', 'KANBAN / FOCUS', 'VERIFY & RECORD'],
- 'channels.drawio': ['CORP V1 — BOARD & PROJECT CHANNELS', 'CORP-V1-BOARD', 'GENERAL', 'ARCHITECTURE', 'UI/UX', 'RELEASES', 'MULTIPLE FOCUSED SESSIONS'],
- 'skills.drawio': ['CORP V1 — SKILLS MODEL', 'CENTRAL SOURCES', 'DELIBERATE ADOPTION', 'PROJECT COPIES', 'FOCUSED SESSION'],
+ 'channels.drawio': ['CORP V1 — BOARD, GUILD & PROJECT CHANNELS', 'CORP-V1-BOARD', 'CORP-V1-GUILD', 'GENERAL', 'ARCHITECTURE', 'UI/UX', 'RELEASES', 'MULTIPLE FOCUSED SESSIONS'],
+ 'skills.drawio': ['CORP V1 — SKILLS MODEL', 'CENTRAL SOURCES', 'CORP-V1--GUILD', 'DELIBERATE ADOPTION', 'PROJECT COPIES', 'FOCUSED SESSION'],
'repositories.drawio': ['CORP V1 — ORGANIZATIONS, REPOSITORIES & DELIVERY', 'PROJECT ORGANIZATION', 'SKILLS ORGANIZATION', '7 adopted channel-skill repos', 'GITEA ACTIONS'],
})) {
const diagram = read(`docs/architecture-high-level/diagrams/${name}`);
diff --git a/sidebars/governance.ts b/sidebars/governance.ts
index 4a755ce..e125c81 100644
--- a/sidebars/governance.ts
+++ b/sidebars/governance.ts
@@ -4,6 +4,7 @@ const sidebars: SidebarsConfig = {
governanceSidebar: [
{type: 'doc', id: 'project-lifecycle', label: 'Project Lifecycle'},
{type: 'doc', id: 'decisions', label: 'Decision Log'},
+ {type: 'doc', id: 'decisions/corp-v1-guild-establishment', label: 'Corp v1 Guild Establishment'},
{type: 'doc', id: 'decisions/corp-v1-board-migration', label: 'Corp v1 Board Migration'},
],
};