# Channel Wiki: Eldorado / storm-v1 Dedicated to Discord channel `1555510466904727622` (`storm-v1`). - `artifacts/`: requested deliverables. - `research/`: evidence, brainstorming notes, and open questions. - `repositories/eldorado-storm-v1/`: remote-backed operating skill checkout. Skill: `eldorado-storm-v1`. Strategy presentation preference: diagram-first storytelling, minimal cognitive load; text enriches rather than leads. Detailed contracts/formulas remain in secondary references or collapsed detail, not the main reading path. User correction: https://discord.com/channels/1518726359512387766/1555510466904727622/1556269523701727353. Kanban board: **Eldorado - Storm**, slug `eldorado-storm`. This channel's task operations explicitly select this board, never the globally active AeroSim board. User direction: messages `1556256406511026199` and subsequent stop/move correction. Existing AI-adoption task graph migrated preserving task IDs/history; work resumes only on this board. Runtime: `/opt/data/skills/productivity/eldorado-storm-v1/SKILL.md`. Skill repository: https://gitea.lego-cloud.eu/eldorado-v1-skills/eldorado-storm-v1 Project organization: https://gitea.lego-cloud.eu/eldorado-v1 Both organizations and the skill repository are private. Route source: `/opt/data/scripts/channel-wiki-sync.py`. Wiki: `/opt/data/wiki/channels/1555510466904727622.md`. Source request: https://discord.com/channels/1518726359512387766/1555510466904727622/1555510805997289494 Keep future channel material here. No existing files were migrated. ## Source anchor - Latest processed human message: `1556269523701727353` (2026-10-04 11:39 UTC; diagram-first strategy storytelling and reduced reading/cognitive load). - Daily sync 2026-10-05 read 11 new human messages through authenticated live Discord REST. Existing layout, navigation and board decisions were reconciled; deployment and task-migration claims remain inherited channel-workflow evidence, not independently revalidated. - Daily sync 2026-10-04 verified both new human messages through live Discord REST. The allocation resolves the prior up-to-seven ambiguity; team names and documentation implementation remain channel-workflow evidence, not independently deployed or verified by this scan. - Daily sync 2026-10-03 independently read all 13 human messages available in this channel. Decisions below were already recorded by the channel workflow; repository and deployment claims were not revalidated by this scan. - Open research request: identify Eldorado's CEO and other known C-level leaders (messages `1555614889748336653`, `1555615046128631888`); names are not established by these human messages. ## Documentation foundation - Private source repository: https://gitea.lego-cloud.eu/eldorado-v1/documentation - Local checkout: `/opt/data/channels/eldorado-storm-v1/repositories/documentation/`. - Pages destination: https://pages.apps.lego-cloud.eu/eldorado-v1/documentation/ - Docusaurus with pnpm; Gitea Actions validates pull requests and publishes main through the persistent Pages mount, following `corp-v1/portal`. - Title: **Eldorado Powered By AI**. Purpose: strategy and direction for an AI-powered Eldorado. Initial strategy focus is now skills governance (2026-10-04); implementation ownership, dates and final roadmap remain unconfirmed. - AI-adoption strategy request (`1556250667344207893`): research a multi-page strategy applied to the defined organization, with a long-term TO-BE SDLC governed by one AI agent while people retain laptop code-agent workflows (Copilot, Claude, Cline or similar). First focus: aligned skills governance, quality, adoption, practical KPI calculation and maintenance. This is a requested target/research direction, not evidence of a deployed single-agent system. - Contribution landing page should be titled Overview and explain contribution guidelines for the portal and potentially other organizational areas (`1556249678985822281`). - Full-screen diagram exit should use only a cross icon, without the word Close (`1556268936407023667`); retain accessible labeling and keyboard behavior. Strategy should tell its story through diagrams first, with text as enrichment (`1556269523701727353`). - Direction source: https://discord.com/channels/1518726359512387766/1555510466904727622/1555521770361192521 - Visual reference: https://www.eldorado.gg/ — Lato, gold, charcoal header, light content panels. Original documentation icon/artwork; no marketplace claims. - Navigation: Organization, Strategy, Contribution, each with an independent sidebar. Organization opens at `organization/structure/`. - Archify diagrams use the upstream vendored Node renderer (`vendor/archify/`), editable typed JSON in `diagrams/`, and sandboxed local standalone viewers generated during CI. Contribution → Archify diagrams documents supported types and authoring. - User wants Structure to read as normal organizational documentation: leadership, departments, teams, responsibilities and reporting structure. Public page and diagrams omit assumption/evidence labels, vacancies and source citations. Internet research supports authoring rather than being the reader-facing deliverable. The page is framed as an organizational operating model; staffing is not independently certified. - Background provenance remains outside published docs in `research/organization/sources.json` and `reconstruction-snapshot.mdx`. Do not reintroduce research-report language into the operating-model page. Editorial direction: https://discord.com/channels/1518726359512387766/1555510466904727622/1555601045022052535 - Product and Technology teams are NOT shared. User specified exactly two teams in Product and five in Technology. Documentation uses Product Management and Product Design; Technology uses Product Engineering, Platform & IT, Architecture & Security, Quality Engineering, and Data & AI. Count/allocation decision: https://discord.com/channels/1518726359512387766/1555510466904727622/1555831136339628163 (refers to preceding human message). Separate-team correction: https://discord.com/channels/1518726359512387766/1555510466904727622/1555632617322193017 - All six departments sit on one horizontal row in the overview. Operations, Marketing, Finance & Accounting, and HR & Administration each have one departmental squad, with existing responsibilities retained as workstreams; Product retains two teams and Technology five. Decision: https://discord.com/channels/1518726359512387766/1555510466904727622/1556225726041038849. Published through PR #10; exact-main CI and deployed source/page readback passed, with live modal alignment checked at desktop and mobile widths. - Connector/layout refinement: Management enters department top edges; squad connectors enter from the left. Squad boxes are narrower and vertically stacked with right edges aligned to their department. Decision: https://discord.com/channels/1518726359512387766/1555510466904727622/1556236112807067709. Published via PR #11 with exact-main CI, deployment readback and desktop/mobile alignment checks. - Organization navigation: Structure, Collaboration, SDLC. Collaboration owns “How the departments work together”; SDLC — Software Delivery Life Cycle owns the leadership/delivery diagram and explanation. Pages cross-link; Structure no longer duplicates those sections. Requests: `1556248896932421663`, `1556249200423997562`; published via PR #12 with deployed desktop/mobile verification. - UI preferences: every portal diagram uses only an accessible top-right expand icon, with no JSON source link or published JSON download. SDLC uses a compact desktop preview. No homepage “Explore the documentation” button. Diagram expand opens a same-page full-screen modal, not a new tab; Close/Escape returns focus to the opener. - Diagram integration source: https://discord.com/channels/1518726359512387766/1555510466904727622/1555523538377768971 - Source request: https://discord.com/channels/1518726359512387766/1555510466904727622/1555517987111305256