fix: update Corp v1 skill references
Build and publish Corp v1 Board portal / build (push) Successful in 39s

This commit is contained in:
2026-09-04 12:55:03 +00:00
parent 666b6a8d25
commit fe228108af
22 changed files with 129 additions and 129 deletions
@@ -11,21 +11,21 @@ On 2026-08-27, RootAtSkic (`discord:1518725627845283888`) established `corp-v1-g
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`;
- 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.
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;
- 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.