diff --git a/docs/governance/decisions.md b/docs/governance/decisions.md index a6b283e..1cae1a8 100644 --- a/docs/governance/decisions.md +++ b/docs/governance/decisions.md @@ -8,6 +8,7 @@ sidebar_position: 2 | Date | Decision | Scope | Owner | Record | |---|---|---|---|---| +| 2026-08-27 | Separate each project's lifecycle channels into one dedicated Discord category | Corp v1 governance, AeroSim, Maze Next Gen, E-Shop v1 | RootAtSkic | [Dedicated Discord category per project](/governance/decisions/project-discord-category-separation/) | | 2026-08-27 | Establish the Corp v1 Guild improvement workspace, skill, Gitea source, and portal architecture representation | Corp v1 governance and operating-model improvement | RootAtSkic | [Corp v1 Guild establishment](/governance/decisions/corp-v1-guild-establishment/) | | 2026-08-26 | Authorize E-Shop v1 kickoff, toothbrush-commerce MVP, and bounded bootstrap autonomy | E-Shop v1 | RootAtSkic | [E-Shop v1 kickoff and bootstrap autonomy](/governance/decisions/eshopv1-kickoff-bootstrap-autonomy/) | | 2026-08-25 | Add Piotras to the Corp v1 Board and every active project | Corp v1 governance, AeroSim, Maze Next Gen | RootAtSkic | [Piotras Board and all-project membership](/governance/decisions/piotras-board-all-project-membership/) | diff --git a/docs/governance/decisions/project-discord-category-separation.md b/docs/governance/decisions/project-discord-category-separation.md new file mode 100644 index 0000000..98f5680 --- /dev/null +++ b/docs/governance/decisions/project-discord-category-separation.md @@ -0,0 +1,47 @@ +--- +title: Dedicated Discord category per project +--- + +# Dedicated Discord category per project — 2026-08-27 + +## Context + +All Corp v1 lifecycle channels previously shared the guild-level `corp-v1` category. As the pilot expanded across AeroSim, Maze Next Gen, and E-Shop v1, that flat topology made each project's working boundary harder to scan and increased the risk of mixing project-local channels with Board governance. + +## Decision + +RootAtSkic (`discord:1518725627845283888`) approved one dedicated top-level Discord category per Corp v1 project in Board message `1542625777495965836`. + +- Reserve `corp-v1` (`1537070242335821924`) for Board and shared governance channels. +- Name each project category `corp-v1-`. +- Keep exactly seven lifecycle channels inside each project category in this order: General, Scope, Architecture, UI/UX, Kanban, Delivery, Releases. +- Preserve existing channel IDs, history, topics, pins, webhooks, permission overwrites, and delivery targets during migration. +- Apply the same topology to future kickoffs and delete only an empty project category during an approved sunset. + +## Implementation + +The central [`corp-v1--main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main) skill was updated to version `4.3.0` and merged through PR [8](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/corp-v1--main/pulls/8) at `785e57d6381f60a0caacefdedec791aa3b1fe2fd`. + +Three categories were created with the existing approved permission-overwrite model: + +| Project | Category | Discord ID | +|---|---|---| +| AeroSim | `corp-v1-aerosim` | `1542627633123299359` | +| Maze Next Gen | `corp-v1-mazeng` | `1542627645441839174` | +| E-Shop v1 | `corp-v1-eshopv1` | `1542627655189270719` | + +The 21 existing lifecycle channels were moved by immutable channel ID. No project channel was recreated. + +## Verification + +A fresh full-guild readback confirmed: + +- every project category exists as a category and retains nine permission overwrites; +- all seven exact channels for each project have the expected `parent_id` and lifecycle order; +- all 21 channel IDs are unchanged and each channel retains nine permission overwrites; +- the guild-level `corp-v1` category now contains only `corp-v1-board` and `corp-v1-guild`; +- Hermes can still read recent history in every moved lifecycle channel. + +## Consequences + +Project navigation and the governance boundary are now explicit without losing history or changing channel-targeted integrations. Project records must include the dedicated category ID, and future provisioning must reject lifecycle channels placed directly under the governance category. diff --git a/docs/governance/project-lifecycle.md b/docs/governance/project-lifecycle.md index a92b7eb..8380a15 100644 --- a/docs/governance/project-lifecycle.md +++ b/docs/governance/project-lifecycle.md @@ -23,6 +23,10 @@ Obtain explicit Board approval. Record the approving Board member, decision evid Maintain current status, decisions, risks, milestones, and material scope changes. Project teams retain authority within their approved project boundaries; Board approval is still required for kickoff/closure and changes to `corp-v1--main`. +### Discord topology + +The guild-level `corp-v1` category is reserved for Board and shared governance channels. Every project uses one dedicated top-level category named `corp-v1-` containing exactly seven lifecycle channels in this order: General, Scope, Architecture, UI/UX, Kanban, Delivery, Releases. Existing channels are moved by immutable ID so history, pins, permission overwrites, webhooks, and delivery targets remain intact. + ### Project-channel skill changes A proposed change to a central project-channel reference skill (`corp-v1-channel-*`) must be presented to the Board before publication. After explicit Board approval and central publication, ask every affected project channel to review and synchronize its project-adopted channel skill (`corp-v1-channel-*--`). Synchronization must preserve project-specific decisions, report conflicts for Board review, update runtime copies, and verify attached channel jobs. diff --git a/docs/projects/aerosim.md b/docs/projects/aerosim.md index 3eb1e26..3d3cd43 100644 --- a/docs/projects/aerosim.md +++ b/docs/projects/aerosim.md @@ -54,16 +54,17 @@ A playable MVP covering a light trainer, commercial airliner, and fighter-style ## Discord -Exactly six same-project channels exist under category `corp-v1` (`1537070242335821924`): +Exactly seven same-project channels exist in dedicated category `corp-v1-aerosim` (`1542627633123299359`), in lifecycle order: - `corp-v1-aerosim-general` — `1537227679374508132` - `corp-v1-aerosim-scope` — `1537544173366943886` - `corp-v1-aerosim-architecture` — `1537227680590733383` +- `corp-v1-aerosim-ui-ux` — `1541722108072169562` - `corp-v1-aerosim-kanban` — `1537548579856580739` - `corp-v1-aerosim-delivery` — `1537227683191197807` - `corp-v1-aerosim-releases` — `1537388451501056081` -Hermes bot `1526860732917088266` successfully read and posted project guidance. The general introduction is pinned as message `1537227685657444484`; Scope purpose guidance is message `1537544176621715506`; Kanban purpose guidance is message `1537548582003933326`; Releases purpose guidance is message `1537388452658815077`. Effective access is verified for RootAtSkic (`1518725627845283888`), Panther Skeleton (`476287310627864587`), MartynasP (`773109855497093191`), and Eduard (`364383883778850827`) across all six project channels. +Hermes bot `1526860732917088266` successfully read and posted project guidance. The general introduction is pinned as message `1537227685657444484`; Scope purpose guidance is message `1537544176621715506`; Kanban purpose guidance is message `1537548582003933326`; Releases purpose guidance is message `1537388452658815077`. Effective read access was reverified across all seven project channels after the category migration; channel IDs and permission overwrites are unchanged. Six staggered recurring synchronization jobs are active. Every job runs each hour, monitors only the other five AeroSim channels, loads its mapped adopted channel skill, proactively performs useful safe work within that channel's purpose, and records durable work in project documentation: diff --git a/docs/projects/eshopv1.md b/docs/projects/eshopv1.md index dc5bc36..00e4af1 100644 --- a/docs/projects/eshopv1.md +++ b/docs/projects/eshopv1.md @@ -35,7 +35,7 @@ RootAtSkic (`discord:1518725627845283888`) approved kickoff and override `ESHOPV ## Discord lifecycle -Exactly seven ordered channels exist under `corp-v1`; Hermes view/history/send/pin behavior was verified in each: +Exactly seven ordered channels exist in dedicated category `corp-v1-eshopv1` (`1542627655189270719`); Hermes read access was reverified after migration, and channel IDs and permission overwrites are unchanged: 1. `corp-v1-eshopv1-general` — `1542281868269985912` 2. `corp-v1-eshopv1-scope` — `1542281871642198207` diff --git a/docs/projects/mazeng.md b/docs/projects/mazeng.md index e6eed33..36e84be 100644 --- a/docs/projects/mazeng.md +++ b/docs/projects/mazeng.md @@ -37,16 +37,17 @@ RootAtSkic (`discord:1518725627845283888`) explicitly approved the updated six-c ## Discord -Exactly six channels exist under category `corp-v1` (`1537070242335821924`): +Exactly seven channels exist in dedicated category `corp-v1-mazeng` (`1542627645441839174`), in lifecycle order: - `corp-v1-mazeng-general` — `1539019955738116096`; purpose `1539019957923483728`; pinned skills `1539021508326981683` - `corp-v1-mazeng-scope` — `1539019959135633580`; purpose `1539019961329000479`; pinned skills `1539021514379370546` - `corp-v1-mazeng-architecture` — `1539019963568758835`; purpose `1539019966857355416`; pinned skills `1539021520230162540` +- `corp-v1-mazeng-ui-ux` — `1541722112841089074` - `corp-v1-mazeng-kanban` — `1539019969323466883`; purpose `1539019971655372911`; pinned skills `1539021525657849896` - `corp-v1-mazeng-delivery` — `1539019973043683358`; purpose `1539019975203885068`; pinned skills `1539021530317463572` - `corp-v1-mazeng-releases` — `1539019976977948694`; purpose `1539019979590991963`; pinned skills `1539021536621756458` -General introduction `1539019982682325132` and all six skill-guidance messages are pinned. Hermes read/post/pin operations succeeded in all channels. Harbor request message: `1539020766203617390`. +General introduction `1539019982682325132` and the recorded skill-guidance messages are pinned. Hermes read access was reverified across all seven channels after the category migration; channel IDs and permission overwrites are unchanged. Harbor request message: `1539020766203617390`. ## Synchronization jobs diff --git a/docs/teams/aerosim.md b/docs/teams/aerosim.md index fb84923..25f8b47 100644 --- a/docs/teams/aerosim.md +++ b/docs/teams/aerosim.md @@ -33,4 +33,4 @@ Deliver the AeroSim browser flight-simulation platform, its documentation, and t ## Communication -Exactly six AeroSim channels exist under the `corp-v1` category: `general`, `scope`, `architecture`, `kanban`, `delivery`, and `releases`. RootAtSkic, Panther Skeleton, MartynasP, Eduard, and Hermes have verified effective access. Guidance messages, the pinned general introduction, and six isolated same-project hourly synchronization jobs are verified. +Exactly seven AeroSim channels exist in dedicated category `corp-v1-aerosim` (`1542627633123299359`): `general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, and `releases`. Channel IDs, permission overwrites, and history were preserved during migration; Hermes read access and lifecycle order were reverified. Existing purpose guidance, the pinned general introduction, and project automation records remain attached to the unchanged channel IDs. diff --git a/docs/teams/eshopv1.md b/docs/teams/eshopv1.md index 53cffc3..80c74fe 100644 --- a/docs/teams/eshopv1.md +++ b/docs/teams/eshopv1.md @@ -22,7 +22,7 @@ Deliver the governed E-Shop v1 toothbrush-commerce MVP, its source-evidence cata ## Communication and autonomy -Seven exact E-Shop v1 lifecycle channels and their pinned purpose/skill guidance are verified. One project-specific 30-minute General job is authorized under `ESHOPV1-BOOTSTRAP-AUTONOMY-20260826`; its authority ends at the first human-authored project-channel message. +Seven exact E-Shop v1 lifecycle channels exist in dedicated category `corp-v1-eshopv1` (`1542627655189270719`), with immutable channel IDs and permission overwrites preserved. Hermes read access and order were reverified after migration. One project-specific 30-minute General job is authorized under `ESHOPV1-BOOTSTRAP-AUTONOMY-20260826`; its authority ends at the first human-authored project-channel message. ## Remaining gates diff --git a/docs/teams/mazeng.md b/docs/teams/mazeng.md index 6103201..835ba22 100644 --- a/docs/teams/mazeng.md +++ b/docs/teams/mazeng.md @@ -22,7 +22,7 @@ Deliver the Maze Next Gen multi-cloud inventory and visualization platform, docu ## Communication -Six exact Maze channels, purpose messages, pinned guidance, and six isolated staggered hourly synchronization jobs are verified. +Seven exact Maze channels exist in dedicated category `corp-v1-mazeng` (`1542627645441839174`) in lifecycle order. Channel IDs, permission overwrites, history, purpose messages, and pinned guidance remain attached to the moved channels; Hermes read access was reverified after migration. ## Remaining gate