# Dokumentacja Projektu NASA (Mission Management System) ```mermaid %%{init: { 'theme': 'base', 'themeVariables': { 'primaryColor': '#0b1220', 'primaryTextColor': '#e5e7eb', 'lineColor': '#475569', 'fontFamily': 'Inter, ui-sans-serif, system-ui', 'fontSize': '14px' }, 'flowchart': { 'curve': 'basis', 'nodeSpacing': 55, 'rankSpacing': 65 } }}%% flowchart LR %% ========================================================= %% BASE STYLES (dark UI) %% ========================================================= classDef top fill:#111827,stroke:#f59e0b,stroke-width:2.5px,color:#ffffff,rx:16,ry:16; classDef control fill:#0b2a4a,stroke:#22c55e,stroke-width:2.5px,color:#e0f2fe,rx:16,ry:16; classDef section fill:#0b1220,stroke:#1f2937,stroke-width:1.2px,color:#cbd5e1,rx:12,ry:12; classDef agent fill:#020617,stroke:#475569,stroke-width:1.2px,color:#e5e7eb,rx:10,ry:10; %% ========================================================= %% MISSION COLOR SYSTEM %% ========================================================= %% Apollo (blue) classDef missionApollo fill:#0b2a4a,stroke:#38bdf8,stroke-width:3px,color:#e0f2fe,rx:16,ry:16,font-weight:bold; classDef apSection fill:#061a2f,stroke:#38bdf8,stroke-width:1.8px,color:#e0f2fe,rx:12,ry:12; classDef apAgent fill:#020617,stroke:#38bdf8,stroke-width:1.6px,color:#e0f2fe,rx:10,ry:10; %% Hubble (amber) classDef missionHubble fill:#2a1606,stroke:#f59e0b,stroke-width:3px,color:#ffedd5,rx:16,ry:16,font-weight:bold; classDef hbSection fill:#1b0f06,stroke:#f59e0b,stroke-width:1.8px,color:#ffedd5,rx:12,ry:12; classDef hbAgent fill:#020617,stroke:#f59e0b,stroke-width:1.6px,color:#ffedd5,rx:10,ry:10; %% Artemis (green) classDef missionArtemis fill:#052e1a,stroke:#22c55e,stroke-width:3px,color:#dcfce7,rx:16,ry:16,font-weight:bold; classDef arSection fill:#041f12,stroke:#22c55e,stroke-width:1.8px,color:#dcfce7,rx:12,ry:12; classDef arAgent fill:#020617,stroke:#22c55e,stroke-width:1.6px,color:#dcfce7,rx:10,ry:10; %% ========================================================= %% COLUMN 1: PROGRAM LEAD %% ========================================================= PROGRAM_LEAD["🧭 [NASA-HQ]
PROGRAM LEAD
Vision · Strategy · Final Decisions"]:::top %% ========================================================= %% COLUMN 2: MISSION CONTROL %% ========================================================= MISSION_CONTROL["🎛️ [MCC]
MISSION CONTROL
Research · Delegation · Execution · Orchestration"]:::control PROGRAM_LEAD --> MISSION_CONTROL %% ========================================================= %% COLUMN 3: PILLARS / MISSIONS (stacked) %% ========================================================= subgraph PILLARS[" "] direction TB FLIGHT_SYSTEMS["🚀 [APOLLO]
FLIGHT SYSTEMS
Engineering · Infrastructure · Reliability"]:::missionApollo MISSION_STORY["🔭 [HUBBLE]
MISSION STORY
Content · Creative · Distribution"]:::missionHubble MISSION_OUTCOMES["🌙 [ARTEMIS]
MISSION OUTCOMES
Product · Growth · Community"]:::missionArtemis end MISSION_CONTROL --> FLIGHT_SYSTEMS MISSION_CONTROL --> MISSION_STORY MISSION_CONTROL --> MISSION_OUTCOMES %% ========================================================= %% APOLLO DETAILS (Flight Systems) %% ========================================================= subgraph FS_DETAILS[" "] direction TB FS_S1["🧱 [APOLLO-CORE]
Core Tech"]:::apSection FS_S2["💻 [APOLLO-CODE]
Flight Code"]:::apSection FS_S3["✅ [APOLLO-VERIFY]
Verification"]:::apSection Anvil["🧰 APOLLO-CORE / Anvil
Systems Engineer"]:::apAgent Cipher["🛡️ APOLLO-CORE / Cipher
Security Engineer"]:::apAgent Pixel["🧩 APOLLO-CODE / Pixel
Frontend Engineer"]:::apAgent Sentry["🛰️ APOLLO-CODE / Sentry
DevOps & Infra"]:::apAgent Inspector["🔍 APOLLO-VERIFY / Inspector
QA & Reliability"]:::apAgent FS_S1 --> Anvil FS_S1 --> Cipher FS_S2 --> Pixel FS_S2 --> Sentry FS_S3 --> Inspector end FLIGHT_SYSTEMS --> FS_S1 FLIGHT_SYSTEMS --> FS_S2 FLIGHT_SYSTEMS --> FS_S3 %% ========================================================= %% HUBBLE DETAILS (Mission Story) %% ========================================================= subgraph MS_DETAILS[" "] direction TB MS_S1["📝 [HUBBLE-CONTENT]
Mission Content"]:::hbSection MS_S2["🎨 [HUBBLE-CREATIVE]
Creative Studio"]:::hbSection Rex["🎬 HUBBLE-CONTENT / Rex
Script Writer"]:::hbAgent Sage["📚 HUBBLE-CONTENT / Sage
Research & Analysis"]:::hbAgent Echo["📰 HUBBLE-CONTENT / Echo
Newsletter Engine"]:::hbAgent Clip["🎞️ HUBBLE-CONTENT / Clip
Short-form Video"]:::hbAgent Nebula["🧑‍🎨 HUBBLE-CREATIVE / Nebula
Visual Design"]:::hbAgent Nova["🎥 HUBBLE-CREATIVE / Nova
Video Production"]:::hbAgent MS_S1 --> Rex MS_S1 --> Sage MS_S1 --> Echo MS_S1 --> Clip MS_S2 --> Nebula MS_S2 --> Nova end MISSION_STORY --> MS_S1 MISSION_STORY --> MS_S2 %% ========================================================= %% ARTEMIS DETAILS (Mission Outcomes) %% ========================================================= subgraph MO_DETAILS[" "] direction TB MO_S1["🧪 [ARTEMIS-EXP]
Experiments"]:::arSection MO_S2["📡 [ARTEMIS-TLM]
Telemetry"]:::arSection MO_S3["🤝 [ARTEMIS-GROUND]
Ground Crew"]:::arSection Scout["🧭 ARTEMIS-EXP / Scout
Product Intelligence"]:::arAgent Herald["📣 ARTEMIS-EXP / Herald
Launch & Announcements"]:::arAgent Forge["🧲 ARTEMIS-TLM / Forge
Optimization"]:::arAgent Pulse["📈 ARTEMIS-TLM / Pulse
Telemetry & Analytics"]:::arAgent Beacon["🧰 ARTEMIS-GROUND / Beacon
Support & Onboarding"]:::arAgent Link["🗨️ ARTEMIS-GROUND / Link
Community Ops"]:::arAgent Vibe["✨ ARTEMIS-GROUND / Vibe
Engagement"]:::arAgent MO_S1 --> Scout MO_S1 --> Herald MO_S2 --> Forge MO_S2 --> Pulse MO_S3 --> Beacon MO_S3 --> Link MO_S3 --> Vibe end MISSION_OUTCOMES --> MO_S1 MISSION_OUTCOMES --> MO_S2 MISSION_OUTCOMES --> MO_S3 ``` ## Spis Treści 1. **Koncepcja i Architektura** * Opis systemu zarządzania misjami * Wyjaśnienie ról (PROGRAM LEAD vs MISSION CONTROL) * Pliki sterujące systemem (NASA-HQ) * Pliki dla Mission Control (MCC) 2. **Misje i Agenci** * Misja APOLLO (Flight Systems) * Sub-agenci APOLLO * Misja HUBBLE (Mission Story) * Sub-agenci HUBBLE * Misja ARTEMIS (Mission Outcomes) * Sub-agenci ARTEMIS 3. **Implementacja i Bootstrap** * Struktura folderów * Plik konfiguracyjny `openclaw.missions.json` * Główny skrypt bootstrap * Szablony pakietów misji --- # CZĘŚĆ 1: KONCEPCJA I ARCHITEKTURA ## 1. Opis systemu (Koncepcja) ### Co to za system (w jednym zdaniu) To jest **operacyjny system zarządzania pracą**, w którym: * **PROGRAM LEAD** ustala kierunek i priorytety, * **MISSION CONTROL** zamienia priorytety na zadania i orkiestruje wykonanie, * a trzy „misje” (**APOLLO / HUBBLE / ARTEMIS**) są **stałymi strumieniami pracy** (workstreams) z własnym słownikiem, sekcjami i agentami. To nie jest tylko „ładny org chart”. To jest: ✅ **routing zadań**, ✅ **standard nazewnictwa**, ✅ **wspólna nawigacja**, ✅ **a docelowo także logika dostępu i audytu**. ### Warstwy odpowiedzialności (governance) #### PROGRAM LEAD — warstwa decyzji **Rola:** “dlaczego i po co?” **Odpowiada za:** * wizję i zasady gry, * finalne decyzje (trade‑offs), * priorytety (co jest ważniejsze), * definicję “co znaczy sukces”. **W praktyce:** PROGRAM LEAD nie schodzi do agentów. PROGRAM LEAD steruje przez *MISSION CONTROL*. #### MISSION CONTROL — warstwa operacji **Rola:** “co robimy teraz i jak to dowieźć?” **Odpowiada za:** * przyjmowanie zleceń/priorytetów, * rozbijanie na konkretne zadania, * delegowanie do misji i sekcji, * pilnowanie wykonania i domykanie wątków. MISSION CONTROL jest Twoim “dispatcherem”: * kontroluje backlog, * kontroluje WIP, * kontroluje jakość wejścia/wyjścia. ### Misje NASA jako system nawigacji Zamiast klasycznych działów typu “Engineering/Marketing/Sales”, masz trzy **misje**, które są: * **łatwe do zapamiętania**, * **rozłączne semantycznie** (mniej chaosu), * **idealne do tagowania** (OpenClaw, logi, foldery, eventy). Każda misja ma cel, zakres, sekcje, agentów i prefiks (call‑sign). #### 🚀 [APOLLO] — FLIGHT SYSTEMS **Slogan:** “Sprawność, stabilność, niezawodność” **Po co istnieje:** utrzymuje i rozwija fundament techniczny. * **[APOLLO-CORE] Core Tech**: fundamenty, bezpieczeństwo, platforma. * **[APOLLO-CODE] Flight Code**: kod produktu, implementacja, UI. * **[APOLLO-VERIFY] Verification**: testy, jakość, niezawodność. #### 🔭 [HUBBLE] — MISSION STORY **Slogan:** “Misja musi być widoczna i zrozumiała” **Po co istnieje:** produkuje i dystrybuuje treści. * **[HUBBLE-CONTENT] Mission Content**: pisanie, research. * **[HUBBLE-CREATIVE] Creative Studio**: grafika, wideo. #### 🌙 [ARTEMIS] — MISSION OUTCOMES **Slogan:** “Efekt misji: produkt, wzrost, społeczność” **Po co istnieje:** dowozi wartość, mierzy ją i zamienia feedback na iteracje. * **[ARTEMIS-EXP] Experiments**: nowe inicjatywy, launch. * **[ARTEMIS-TLM] Telemetry**: pomiary, analityka. * **[ARTEMIS-GROUND] Ground Crew**: społeczność, wsparcie. --- ## 2. Role i Decyzje (Governance) ### Decision Rights (kto może / musi / nie może decydować) #### NASA-HQ (PROGRAM LEAD = CEO) * **Może decydować o:** kierunku, priorytetach, politykach i “co jest sukcesem”. * **Musi decydować o:** P0/P1, zmianach strategii, kosztach/ryzyku systemowym. * **Nie powinien decydować o:** szczegółach implementacji i mikro‑wyborach w taskach. #### MISSION CONTROL (MCC = COO / Ops) * **Może decydować o:** routingu, WIP, strukturze pakietów, jakości wejścia/wyjścia, “czy to jest done operacyjnie”. * **Musi decydować o:** triage, podziale na pakiety, bramkach SIM/FLIGHT, domknięciu (`PROCEED/ITERATE/HOLD/SCRUB`). * **Nie może decydować o:** strategicznej zmianie celu (CEO territory) oraz o FLIGHT dla P0/P1 bez GO od NASA-HQ. #### Misje (APOLLO / HUBBLE / ARTEMIS = “mission owners”) * **Może decydować o:** *jak* wykonać zadanie w ramach swojej domeny, jakie artefakty i jak je ułożyć, jakie rekomendacje zaproponować. * **Musi decydować o:** standardach jakości wewnątrz misji, kompletności artefaktów, rekomendacji decyzji (dla MCC). * **Nie może decydować o:** zmianie routingu, przekierowaniu misji, zatwierdzaniu FLIGHT (bez MCC), ani o celach strategicznych. ### Decision Matrix (skrót) * **Strategia / priorytety P0/P1:** **PL decyduje**, MCC rekomenduje * **Routing / pakiety / WIP:** **MCC decyduje** * **Standardy operacyjne:** **MCC decyduje**, PL zatwierdza tylko zmiany “filozofii” * **Wykonanie w domenie:** **misja decyduje jak**, MCC decyduje czy “done” * **FLIGHT:** **MCC gatekeeper**, **PL GO dla P0/P1**, **Inspector NO‑GO dla technicznego** * **Closure:** **MCC decyduje**, misja rekomenduje, PL tylko przy P0/P1/sporach ### RACI — diagram odpowiedzialności ```mermaid %%{init: { 'theme': 'base', 'themeVariables': { 'primaryColor': '#0b1220', 'primaryTextColor': '#e5e7eb', 'lineColor': '#475569', 'fontFamily': 'Inter, ui-sans-serif, system-ui', 'fontSize': '14px' }, 'flowchart': { 'curve': 'basis', 'nodeSpacing': 40, 'rankSpacing': 55 } }}%% flowchart LR %% Styles classDef role fill:#111827,stroke:#334155,stroke-width:1.5px,color:#e5e7eb,rx:12,ry:12,font-weight:bold; classDef proc fill:#0f172a,stroke:#64748b,stroke-width:1.2px,color:#e5e7eb,rx:10,ry:10; classDef raciR fill:#052e1a,stroke:#22c55e,stroke-width:2px,color:#dcfce7,rx:10,ry:10; classDef raciA fill:#2a1606,stroke:#f59e0b,stroke-width:2px,color:#ffedd5,rx:10,ry:10; classDef raciC fill:#1e1b4b,stroke:#818cf8,stroke-width:2px,color:#e0eaff,rx:10,ry:10; classDef raciI fill:#0b1220,stroke:#475569,stroke-width:1.2px,color:#cbd5e1,rx:10,ry:10; %% Roles (columns) subgraph ROLES["ROLES"] direction TB PL["🧭 NASA‑HQ\nPROGRAM LEAD (CEO)"]:::role MCC["🎛️ MISSION CONTROL\n(MCC / COO)"]:::role AP["🚀 APOLLO\nFlight Systems"]:::role HU["🔭 HUBBLE\nMission Story"]:::role AR["🌙 ARTEMIS\nMission Outcomes"]:::role VFY["✅ APOLLO‑VERIFY\n(Inspector)"]:::role end %% Processes (rows) subgraph PROCESSES["PROCESSES"] direction TB P1["1) Intake / Triage"]:::proc P2["2) Routing (Mission + Call‑sign)"]:::proc P3["3) Packet Creation (folder + brief)"]:::proc P4["4) Execution (produce artifacts)"]:::proc P5["5) Status / Telemetry updates"]:::proc P6["6) SIM→FLIGHT Checklist prepared"]:::proc P7["7) FLIGHT GO/NO‑GO"]:::proc P8["8) Close Packet (PROCEED/ITERATE/HOLD/SCRUB)"]:::proc P9["9) Archive + Index update"]:::proc end %% RACI links: each process points to roles with R/A/C/I tags P1 -->|"A"| MCC:::raciA; P1 -->|"I"| PL:::raciI; P1 -->|"C"| AP:::raciC; P1 -->|"C"| HU:::raciC; P1 -->|"C"| AR:::raciC P2 -->|"A"| MCC:::raciA; P2 -->|"I"| PL:::raciI; P2 -->|"C"| AP:::raciC; P2 -->|"C"| HU:::raciC; P2 -->|"C"| AR:::raciC P3 -->|"R/A"| MCC:::raciA; P3 -->|"C"| AP:::raciC; P3 -->|"C"| HU:::raciC; P3 -->|"C"| AR:::raciC; P3 -->|"I"| PL:::raciI P4 -->|"I"| MCC:::raciI; P4 -->|"R/A"| AP:::raciR; P4 -->|"R/A"| HU:::raciR; P4 -->|"R/A"| AR:::raciR; P4 -->|"I"| PL:::raciI P5 -->|"A"| MCC:::raciA; P5 -->|"R"| AP:::raciR; P5 -->|"R"| HU:::raciR; P5 -->|"R"| AR:::raciR; P5 -->|"I"| PL:::raciI P6 -->|"A"| MCC:::raciA; P6 -->|"R"| AP:::raciR; P6 -->|"R"| HU:::raciR; P6 -->|"R"| AR:::raciR; P6 -->|"C"| VFY:::raciC; P6 -->|"C"| PL:::raciC P7 -->|"A"| MCC:::raciA; P7 -->|"C"| VFY:::raciC; P7 -->|"C"| AP:::raciC; P7 -->|"C"| HU:::raciC; P7 -->|"C"| AR:::raciC; P7 -->|"A (P0/P1)"| PL:::raciA P8 -->|"A"| MCC:::raciA; P8 -->|"C"| AP:::raciC; P8 -->|"C"| HU:::raciC; P8 -->|"C"| AR:::raciC; P8 -->|"C (P0/P1 or dispute)"| PL:::raciC P9 -->|"R/A"| MCC:::raciA; P9 -->|"I"| PL:::raciI; P9 -->|"I"| AP:::raciI; P9 -->|"I"| HU:::raciI; P9 -->|"I"| AR:::raciI ``` --- ## 3. Pliki sterujące NASA-HQ ### `IDENTITY.md` ```md Name: NASA-HQ Role: Program Lead & Mission Control System: Mission Management System (OpenClaw) NASA-HQ is the executive and operational control layer of the system. It does not execute tasks directly. It defines intent, routes work, enforces structure, and closes missions. ``` ### `SOUL.md` ```md NASA-HQ operates with discipline, clarity, and restraint. Core principles: - Structure over improvisation - Routing before execution - Decisions over endless work - Fewer missions, better outcomes ``` ### `TOOLS.md` ```md NASA-HQ uses tools only to: - create and manage mission structure - write and update documentation - maintain routing and indices - inspect system state Rule of thumb: If a tool changes reality → it must go through a Mission Packet and FLIGHT gate. ``` --- ## 4. Pliki sterujące MISSION CONTROL (MCC) ### `IDENTITY.md` ```md Name: MISSION CONTROL Alias: MCC Role: Operational Command & Routing Layer MISSION CONTROL is the dispatcher and quality gate of the entire system. It converts strategic intent into executable mission packets, routes work by call-sign, maintains WIP limits, enforces SIM/FLIGHT gates, and closes missions with decisions. ``` ### `RULES.md` ```md 1) Every task must have exactly one call-sign (or MCC-TRIAGE). 2) Never mix missions inside one packet. 3) If work spans missions: create a parent MCC packet + child packets per mission. 4) SIM is default. FLIGHT requires checklist. 5) Every packet must end with a decision: PROCEED | ITERATE | HOLD | SCRUB. ``` ### `HEARTBEAT.md` ```md 1) Review active packets (MCC active index). 2) Enforce WIP (stop intake if limit exceeded). 3) Check SIM/FLIGHT hygiene. 4) Closure sweep (packets done but undecided). 5) Archive hygiene. ``` --- # CZĘŚĆ 2: MISJE I AGENCI ## 1. Misja APOLLO (Flight Systems) ### `IDENTITY.md` ```md Name: APOLLO Role: Mission Owner — FLIGHT SYSTEMS Domain: Engineering · Infrastructure · Reliability APOLLO owns the technical flight layer: - Core Tech (APOLLO-CORE) - Flight Code (APOLLO-CODE) - Verification (APOLLO-VERIFY) ``` ### `SOUL.md` ```md APOLLO is reliability-first and safety-gated. Core principles: - Stability over speed - Explicit changes over hidden magic - Small, reversible steps over big rewrites - Verification before confidence ``` ### Sub-agenci APOLLO * **Anvil (APOLLO-CORE)**: Systems Engineer. Platform foundations, architecture constraints. * **Cipher (APOLLO-CORE)**: Security Engineer. Security posture, secrets, hardening. * **Pixel (APOLLO-CODE)**: Frontend Engineer. UI code, integration glue. * **Sentry (APOLLO-CODE)**: DevOps & Infra. Pipelines, runtime, automation. * **Inspector (APOLLO-VERIFY)**: QA & Reliability. Verification evidence, regression checks. --- ## 2. Misja HUBBLE (Mission Story) ### `IDENTITY.md` ```md Name: HUBBLE Role: Mission Owner — MISSION STORY Domain: Content · Creative · Distribution HUBBLE owns the story layer: - Mission Content (HUBBLE-CONTENT) - Creative Studio (HUBBLE-CREATIVE) ``` ### `SOUL.md` ```md HUBBLE is clarity-first, audience-aware, and production-minded. Core principles: - Clarity beats cleverness - Consistency beats variety - Shipping beats endless polishing ``` ### Sub-agenci HUBBLE * **Rex (HUBBLE-CONTENT)**: Script Writer. Scripts, hooks, outlines. * **Sage (HUBBLE-CONTENT)**: Research & Analysis. Evidence, sources, insights. * **Echo (HUBBLE-CONTENT)**: Newsletter Engine. Newsletter drafts, editorial structure. * **Clip (HUBBLE-CONTENT)**: Short-form Video. Scripts for Reels/Shorts. * **Nebula (HUBBLE-CREATIVE)**: Visual Design. Visual assets, layouts, thumbnails. * **Nova (HUBBLE-CREATIVE)**: Video Production. Storyboards, edit plans. --- ## 3. Misja ARTEMIS (Mission Outcomes) ### `IDENTITY.md` ```md Name: ARTEMIS Role: Mission Owner — MISSION OUTCOMES Domain: Product · Growth · Community ARTEMIS owns the outcomes layer: - Experiments (ARTEMIS-EXP) - Telemetry (ARTEMIS-TLM) - Ground Crew (ARTEMIS-GROUND) ``` ### `SOUL.md` ```md ARTEMIS is outcome-driven and evidence-first. Core principles: - Outcomes over activity - Evidence over opinion - Small experiments over big rewrites - Telemetry before conclusions ``` ### Sub-agenci ARTEMIS * **Scout (ARTEMIS-EXP)**: Product Intelligence. Opportunities, hypotheses. * **Herald (ARTEMIS-EXP)**: Launch & Announcements. Launch plans, rollout messaging. * **Pulse (ARTEMIS-TLM)**: Telemetry & Analytics. Dashboards, KPI definitions. * **Forge (ARTEMIS-TLM)**: Optimization. Optimization proposals, experiment variants. * **Beacon (ARTEMIS-GROUND)**: Support & Onboarding. Onboarding playbooks, support workflows. * **Link (ARTEMIS-GROUND)**: Community Ops. Operations, moderation, structure. * **Vibe (ARTEMIS-GROUND)**: Engagement. Engagement loops, prompts. --- # CZĘŚĆ 3: IMPLEMENTACJA I BOOTSTRAP ## 1. Struktura folderów ```text /missions ├── _MCC/ # MISSION CONTROL (operacje) │ ├── 00_operating-manual.md │ ├── 10_backlog.md │ ├── 20_active-missions.md │ ├── 30_decisions.md │ ├── 40_routing-rules.md │ ├── 50_templates/ │ │ ├── task-brief.md │ │ ├── sim-flight-checklist.md │ │ ├── post-mission-report.md │ │ └── decision-record.md │ └── 90_archive-index.md │ ├── APOLLO/ # 🚀 FLIGHT SYSTEMS │ ├── CORE_TECH/ # [APOLLO-CORE] │ │ └── missions/ │ ├── FLIGHT_CODE/ # [APOLLO-CODE] │ │ └── missions/ │ ├── VERIFICATION/ # [APOLLO-VERIFY] │ │ └── missions/ │ └── 99_archive/ │ ├── HUBBLE/ # 🔭 MISSION STORY │ ├── CONTENT/ # [HUBBLE-CONTENT] │ │ └── missions/ │ ├── CREATIVE/ # [HUBBLE-CREATIVE] │ │ └── missions/ │ └── 99_archive/ │ └── ARTEMIS/ # 🌙 MISSION OUTCOMES ├── EXPERIMENTS/ # [ARTEMIS-EXP] │ └── missions/ ├── TELEMETRY/ # [ARTEMIS-TLM] │ └── missions/ ├── GROUND_CREW/ # [ARTEMIS-GROUND] │ └── missions/ └── 99_archive/ ``` ## 2. Plik konfiguracyjny `openclaw.missions.json` Ten plik jest sercem mapowania systemu. Powinien zostać umieszczony w `{ROOT_PATH}/_MCC/openclaw.missions.json`. ```json { "root_path": "{{ROOT_PATH}}", "wip_limit": 5, "modes": { "default": "SIM", "flight_requires_checklist": true, "flight_requires_program_lead_for_priority": ["P0", "P1"] }, "missions": { "APOLLO": { "label": "FLIGHT SYSTEMS", "sections": { "APOLLO-CORE": { "folder": "APOLLO/CORE_TECH", "agents": ["Anvil", "Cipher"] }, "APOLLO-CODE": { "folder": "APOLLO/FLIGHT_CODE", "agents": ["Pixel", "Sentry"] }, "APOLLO-VERIFY": { "folder": "APOLLO/VERIFICATION", "agents": ["Inspector"] } } }, "HUBBLE": { "label": "MISSION STORY", "sections": { "HUBBLE-CONTENT": { "folder": "HUBBLE/CONTENT", "agents": ["Rex", "Sage", "Echo", "Clip"] }, "HUBBLE-CREATIVE": { "folder": "HUBBLE/CREATIVE", "agents": ["Nebula", "Nova"] } } }, "ARTEMIS": { "label": "MISSION OUTCOMES", "sections": { "ARTEMIS-EXP": { "folder": "ARTEMIS/EXPERIMENTS", "agents": ["Scout", "Herald"] }, "ARTEMIS-TLM": { "folder": "ARTEMIS/TELEMETRY", "agents": ["Forge", "Pulse"] }, "ARTEMIS-GROUND": { "folder": "ARTEMIS/GROUND_CREW", "agents": ["Beacon", "Link", "Vibe"] } } } }, "packet": { "name_format": "YYYY-MM-DD__CALLSIGN__slug", "required_files": [ "00_brief.md", "10_worklog.md", "30_results.md", "40_decision.md", "90_links.md" ], "artifact_dir": "20_artifacts" } } ``` ## 3. Główny skrypt bootstrap Poniższy skrypt jest główną metodą tworzenia całej struktury systemu za pomocą jednego polecenia agenta `openclaw`. ### Wersja dla Linux/macOS/WSL (bash) ```bash export ROOT_PATH="$HOME/.openclaw/workspace/missions" openclaw --profile missionctl agent --message " Jesteś MISSION CONTROL bootstrapper. Masz utworzyć strukturę systemu zarządzania MISJAMI w katalogu ROOT_PATH=$ROOT_PATH. Wykonaj dokładnie: 1) Utwórz katalogi: - $ROOT_PATH/_MCC/50_templates - $ROOT_PATH/APOLLO/CORE_TECH/missions - $ROOT_PATH/APOLLO/FLIGHT_CODE/missions - $ROOT_PATH/APOLLO/VERIFICATION/missions - $ROOT_PATH/APOLLO/99_archive - $ROOT_PATH/HUBBLE/CONTENT/missions - $ROOT_PATH/HUBBLE/CREATIVE/missions - $ROOT_PATH/HUBBLE/99_archive - $ROOT_PATH/ARTEMIS/EXPERIMENTS/missions - $ROOT_PATH/ARTEMIS/TELEMETRY/missions - $ROOT_PATH/ARTEMIS/GROUND_CREW/missions - $ROOT_PATH/ARTEMIS/99_archive 2) Zapisz pliki startowe (nadpisz jeśli istnieją): A) $ROOT_PATH/_MCC/00_operating-manual.md Treść: # Operating Manual — Mission System ## Governance - PROGRAM LEAD: vision, strategy, final decisions - MISSION CONTROL (MCC): triage, routing, execution, WIP, closure ## Missions - APOLLO: Flight Systems (Core Tech, Flight Code, Verification) - HUBBLE: Mission Story (Mission Content, Creative Studio) - ARTEMIS: Mission Outcomes (Experiments, Telemetry, Ground Crew) ## Packet standard Each packet contains: 00_brief.md, 10_worklog.md, 20_artifacts/, 30_results.md, 40_decision.md, 90_links.md ## Modes SIM (default) vs FLIGHT (requires SIM→FLIGHT checklist) ## Closure PROCEED | ITERATE | HOLD | SCRUB B) $ROOT_PATH/_MCC/40_routing-rules.md Treść: # Routing Rules (MCC) ## Call-signs → folders APOLLO-CORE → APOLLO/CORE_TECH APOLLO-CODE → APOLLO/FLIGHT_CODE APOLLO-VERIFY → APOLLO/VERIFICATION HUBBLE-CONTENT → HUBBLE/CONTENT HUBBLE-CREATIVE → HUBBLE/CREATIVE ARTEMIS-EXP → ARTEMIS/EXPERIMENTS ARTEMIS-TLM → ARTEMIS/TELEMETRY ARTEMIS-GROUND → ARTEMIS/GROUND_CREW ## Default mode SIM is default. FLIGHT requires checklist + approvals. C) Puste indeksy: - $ROOT_PATH/_MCC/10_backlog.md (\"# Backlog (MCC)\") - $ROOT_PATH/_MCC/20_active-missions.md (\"# Active Missions (MCC)\") - $ROOT_PATH/_MCC/30_decisions.md (\"# Decisions (MCC)\") - $ROOT_PATH/_MCC/90_archive-index.md (\"# Archive Index (MCC)\") 3) Zapisz templates: - $ROOT_PATH/_MCC/50_templates/task-brief.md - $ROOT_PATH/_MCC/50_templates/sim-flight-checklist.md - $ROOT_PATH/_MCC/50_templates/post-mission-report.md - $ROOT_PATH/_MCC/50_templates/decision-record.md 4) Zapisz plik mapowania `openclaw.missions.json` z sekcji 3.2. 5) Na koniec zwróć krótkie podsumowanie: co utworzyłeś i gdzie. " ``` ### Wersja dla Windows PowerShell ```powershell $ROOT_PATH = "$env:USERPROFILE\.openclaw\workspace\missions" openclaw --profile missionctl agent --message @" Utwórz strukturę systemu zarządzania MISJAMI w ROOT_PATH=$ROOT_PATH zgodnie z instrukcjami (katalogi, pliki MCC, template’y i openclaw.missions.json) analogicznie jak w wersji bash. "@ ``` ## 4. Szablony Pakietów Misji Poniżej znajdują się szablony, które powinny być umieszczone w `_MCC/50_templates/`. ### `task-brief.md` ```md # [CALLSIGN] Task Brief — **Routing:** [CALLSIGN] **Owner (Agent):** <AgentName> **Mode:** SIM | FLIGHT **Priority:** P0 | P1 | P2 **Start:** YYYY-MM-DD **Due:** YYYY-MM-DD (optional) ## Context Dlaczego to robimy? Jaki problem/okazja? ## Goal (1–2 zdania) Co ma być osiągnięte? ## Output / Deliverables - [ ] Artefakt 1 (np. raport / plik / PRD / skrypt / wideo) - [ ] Artefakt 2 ## Constraints - deadline, format, ograniczenia techniczne, polityki ## Acceptance Criteria (Definition of Done) - Warunek A - Warunek B - Metryka/obserwacja C (jeśli dotyczy) ## Risks / Unknowns - ryzyko 1 + plan mitigacji ``` ### `sim-flight-checklist.md` ```md # SIM → FLIGHT Checklist ## Quality Gate - [ ] Acceptance criteria spełnione - [ ] Ryzyka opisane + mitigacja - [ ] Artefakty gotowe i podlinkowane ## Verification Gate (jeśli dotyczy) - [ ] APOLLO-VERIFY: testy/audyt wykonane - [ ] Rollback/undo plan istnieje ## Telemetry Gate (jeśli dotyczy) - [ ] ARTEMIS-TLM: metryki do obserwacji zdefiniowane - [ ] Kiedy i jak mierzymy efekt? ## Approval - [ ] MISSION CONTROL: GO - [ ] PROGRAM LEAD: GO (dla P0/P1) ``` ### `post-mission-report.md` ```md # Post-Mission Report — <title> **Packet:** YYYY-MM-DD__CALLSIGN__slug **Decision:** PROCEED | ITERATE | HOLD | SCRUB **Owner:** MISSION CONTROL / PROGRAM LEAD **Date:** YYYY-MM-DD ## Summary 1–3 zdania: co zrobiono i po co. ## Artifacts - linki/ścieżki ## Measurements / Evidence - metryki, screeny, logi, testy ## Learnings - co zadziałało - co nie zadziałało ## Next Steps - 1–5 kroków ``` ### `decision-record.md` ```md # Decision Record — <title> **Decision:** PROCEED | ITERATE | HOLD | SCRUB **Date:** YYYY-MM-DD **Owner:** PROGRAM LEAD / MISSION CONTROL ## Rationale Dlaczego taka decyzja? ## Trade-offs Co świadomie poświęcamy? ## Follow-up - [ ] zadanie 1 - [ ] zadanie 2 ```