docs: reconcile canonical SKIC channel skill names
Validate skill / validate (pull_request) Successful in 5s
Validate skill / validate (push) Successful in 6s

This commit is contained in:
jarvis-at-skic committed 2026-10-21 17:56:54 +00:00
1 parent a767272a1b
commit 3b682a44dc
4 files changed
+27 -18

No files matched your search

+23 -14
View File
@@ -1,16 +1,16 @@
---
name: corp-v1-channel-architecture
name: channel-architecture-skic
description: "Use when operating or synchronizing a Corp v1 project's architecture channel. Maintains C4-based architecture documentation, Draw.io diagrams, architecture decisions, and requirements while correlating verified activity across the project's eight channels."
version: 1.10.0
version: 1.10.1
author: Hermes Agent
license: MIT
metadata:
hermes:
tags: [corp-v1, discord, channel, architecture, c4, adr, requirements]
related_skills: [corp-v1-main, home-v1-discord, diagrams-drawio, documentation-docusaurus, corp-v1-glossary]
related_skills: [channel-board-skic, home-v1-discord, diagrams-drawio, documentation-docusaurus, corp-v1-glossary]
---
# Corp v1 Architecture Channel
# SKIC Architecture Channel Reference
## Overview
@@ -38,7 +38,7 @@ Load the global `corp-v1-glossary` skill from `https://gitea.lego-cloud.eu/home-
## Shared Corp v1 System Login
When an authorized task requires login to a Corp v1 system being built or operated, follow the shared policy in `corp-v1-main` and use only the Bitwarden-injected runtime secrets named:
When an authorized task requires login to a Corp v1 system being built or operated, follow the shared policy in `channel-board-skic` and use only the Bitwarden-injected runtime secrets named:
```text
HL_V1_SSO_EMAIL
@@ -51,7 +51,7 @@ Secret availability is capability, not authorization. Verify the destination ori
Use this skill when:
- operating in `corp-v1-<code>-architecture`;
- operating in `<code>-architecture`;
- running its recurring synchronization job;
- designing or reviewing project architecture;
- maintaining C4 views and Draw.io sources;
@@ -76,14 +76,14 @@ Record approver identity, decision message or documentation reference, date, and
Inspect only:
```text
corp-v1-<code>-general
corp-v1-<code>-scope
corp-v1-<code>-architecture
corp-v1-<code>-ui-ux
corp-v1-<code>-kanban
corp-v1-<code>-delivery
corp-v1-<code>-uat
corp-v1-<code>-releases
<code>-general
<code>-scope
<code>-architecture
<code>-ui-ux
<code>-kanban
<code>-delivery
<code>-uat
<code>-releases
```
Use mapped-channel history to avoid duplicate work and new relevant activity from the other seven channels. Never inspect another project's channels.
@@ -357,3 +357,12 @@ Use RED-first repository contracts for delegated solution packages and task iden
- [ ] Proposed items remain visibly proposed.
- [ ] Documentation and diagram checks passed.
- [ ] Commit/message/run evidence is included.
## Canonical naming and compatibility
- Canonical installed and repository name: `channel-architecture-skic`.
- Source: `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/channel-architecture-skic`.
- Previous name: `corp-v1-channel-architecture`; retained locally only as a compatibility alias. New guidance and presentations use the canonical name.
- Naming-only migration authorized by RootAtSkic in [presentation message 1562523679223578705](https://discord.com/channels/1518726359512387766/1543922127898415154/1562523679223578705). Repository ID, history, support files, project authority and organization ownership are preserved.
- This is a reusable central reference, not a new shared Discord channel. Project adoptions use `channel-architecture-skic-<code>` and remain separately owned.
- Current project channel: `<code>-architecture` inside `skic-<code>`.