fix: update Corp v1 skill references
Build and publish Corp v1 Board portal / build (push) Successful in 39s
Build and publish Corp v1 Board portal / build (push) Successful in 39s
This commit is contained in:
@@ -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.
|
||||
|
||||
|
||||
@@ -30,7 +30,7 @@ The corresponding skills team grants access to:
|
||||
- seven adopted engineering-skill repositories;
|
||||
- their complete supporting assets, scripts, templates, references, and preserved adoption history.
|
||||
|
||||
The global `drawio-main` and `corp-v1--glossary` remain shared references unless an explicit project decision adopts a local copy.
|
||||
The global `drawio-main` and `corp-v1-glossary` remain shared references unless an explicit project decision adopts a local copy.
|
||||
|
||||
## Delivery evidence
|
||||
|
||||
|
||||
@@ -19,9 +19,9 @@ 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-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. |
|
||||
| [`corp-v1-channel-architecture`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1-channel-architecture) | Requirements, ADRs, interfaces, constraints, system design, and implementation Tasks. |
|
||||
@@ -34,12 +34,12 @@ The central sources live in [`home-v1-skills-code-agent`](https://gitea.lego-clo
|
||||
|
||||
Every project owns fourteen adopted repositories in `corp-v1-<code>-skills-code-agent`:
|
||||
|
||||
- seven channel skills named `corp-v1-channel-<channel>--<code>`;
|
||||
- seven engineering skills named `<source-skill>--<code>`.
|
||||
- seven channel skills named `corp-v1-channel-<channel>-<code>`;
|
||||
- seven engineering skills named `<source-skill>-<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.
|
||||
`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.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user