docs: establish Corp v1 Guild architecture

2026-08-27 18:19:03 +00:00
parent fdc366c7dc
commit 6c9b399043
9 changed files with 155 additions and 60 deletions
@@ -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 scheduler job is created for `corp-v1-guild`; project automation retains its separately recorded authority and is not changed by this decision.