docs: reconcile canonical SKIC channel skill names

This commit is contained in:
jarvis-at-skic committed 2026-10-21 17:56:52 +00:00
1 parent 3ac7c7b38f
commit 7a998cde08
3 files changed
+28 -19

No files matched your search

+24 -15
View File
@@ -1,16 +1,16 @@
---
name: corp-v1-channel-scope
name: channel-scope-skic
description: "Use when operating or synchronizing a Corp v1 project's Scope channel. Owns Roadmap, Epics, Features, and Ideas; correlates all eight same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design."
version: 1.8.0
version: 1.8.1
author: Hermes Agent
license: MIT
metadata:
hermes:
tags: [corp-v1, discord, channel, scope, roadmap, epics, features, discovery]
related_skills: [corp-v1-main, home-v1-discord, documentation-docusaurus, corp-v1-glossary]
related_skills: [channel-board-skic, home-v1-discord, documentation-docusaurus, corp-v1-glossary]
---
# Corp v1 Scope Channel
# SKIC Scope Channel Reference
## Overview
@@ -28,7 +28,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
@@ -41,7 +41,7 @@ Secret availability is capability, not authorization. Verify the destination ori
Use this skill when:
- operating in `corp-v1-<code>-scope`;
- operating in `<code>-scope`;
- running its recurring synchronization job;
- maintaining Overview, Roadmap, Epics, Features, canonical Task reader pages, Ideas, or Questions;
- discovering user/project problems and opportunities;
@@ -53,19 +53,19 @@ Do not use it to design architecture, approve solution entry, approve implementa
## Approved Information Boundary
Follow the eight-channel topology in `corp-v1-main`, approved by Board message `1552966246591365123`; include UAT between Delivery and Releases. Verify mapped IDs and effective access before reading.
Follow the eight-channel topology in `channel-board-skic`, approved by Board message `1552966246591365123`; include UAT between Delivery and Releases. Verify mapped IDs and effective access before reading.
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
```
Read enough Scope history to avoid duplicates and only relevant new activity from the other seven channels. Never inspect or correlate another project's channels.
@@ -393,3 +393,12 @@ Source comparison and exclusions: [AeroSim lessons review](references/aerosim-le
- [ ] A successful unrequested completion report contains only substantive changes and documentation links; technical delivery evidence appears only on request or for an actionable exception.
- [ ] When React Flow is used, its graph and semantic table share one canonical-YAML selector and pass accessibility, build, browser, and remote exact-head checks.
- [ ] Completed work includes exact message, path, commit, URL, or run evidence.
## Canonical naming and compatibility
- Canonical installed and repository name: `channel-scope-skic`.
- Source: `https://gitea.lego-cloud.eu/home-v1-skills-code-agent/channel-scope-skic`.
- Previous name: `corp-v1-channel-scope`; 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-scope-skic-<code>` and remain separately owned.
- Current project channel: `<code>-scope` inside `skic-<code>`.