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

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

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-04 12:55:03 +00:00
parent 666b6a8d25
commit fe228108af
22 changed files with 129 additions and 129 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture-high-level/overview-channels.mdx
+3 -3
View File
@@ -17,14 +17,14 @@ Corp v1 uses **two central portfolio workspaces** and **seven purpose-specific c
`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).
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`
`corp-v1-board` exists once for the whole Corp v1 pilot. It is the authoritative Discord workspace for decisions that change the portfolio operating model:
- approve project kickoffs, closures, and membership changes;
- approve changes to the global `corp-v1--main` governance skill;
- approve changes to the global `corp-v1-main` governance skill;
- approve central `corp-v1-channel-*` reference-skill changes;
- resolve conflicts that cannot be decided inside one project;
- review portfolio-level evidence and remaining gates.
@@ -51,7 +51,7 @@ The same Hermes agent operates across the pilot, but each Discord channel has it
1. **Shared identity and governance** — one agent follows the same Board-approved operating model.
2. **Focused context** — Scope discussion does not become Delivery execution, and one project's decisions do not silently become another project's decisions.
3. **Specialised behavior** — the mapped `corp-v1-channel-<channel>--<code>` skill defines the channel's responsibilities, approvals, evidence, and handoffs.
3. **Specialised behavior** — the mapped `corp-v1-channel-<channel>-<code>` skill defines the channel's responsibilities, approvals, evidence, and handoffs.
4. **Engineering depth on demand** — relevant project engineering skills are loaded alongside the channel skill for documentation, branching, monorepo work, CI/CD, GitOps, scripts, and templates.
5. **Durable evidence** — decisions and current state are written to Discord, Gitea, project documentation, and the Board portal rather than existing only in an agent session.