# Specyfikacja Konfiguracji OpenClaw: System Zarządzania Misjami

Na podstawie analizy dostarczonych plików, przygotowałem specyfikację do ustawienia systemu zarządzania misjami w OpenClaw. System ten opiera się na hierarchicznej strukturze folderów, pliku konfiguracyjnym `openclaw.missions.json` oraz zestawie szablonów.

## 1. Konfiguracja Rdzenia Systemu (`openclaw.missions.json`)

Sercem systemu jest plik konfiguracyjny, który mapuje misje, sekcje i agentów. Należy go umieścić w `{ROOT_PATH}/_MCC/openclaw.missions.json`.

**Zawartość `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"]
  },
  "governance": {
    "program_lead": {
      "name": "PROGRAM LEAD",
      "responsibilities": ["Vision", "Strategy", "Final Decisions"]
    },
    "mission_control": {
      "name": "MISSION CONTROL",
      "alias": "MCC",
      "responsibilities": ["Research", "Delegation", "Execution", "Orchestration"]
    }
  },
  "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"
  }
}
```

## 2. Struktura Katalogów

System wymaga następującej struktury katalogów, którą można utworzyć za pomocą poniższych poleceń. `ROOT_PATH` to główny katalog systemu (np. `~/.openclaw/workspace/missions`).

```text
ROOT/
  _MCC/
    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
    openclaw.missions.json
    90_archive-index.md

  APOLLO/
    CORE_TECH/missions/
    FLIGHT_CODE/missions/
    VERIFICATION/missions/
    99_archive/

  HUBBLE/
    CONTENT/missions/
    CREATIVE/missions/
    99_archive/

  ARTEMIS/
    EXPERIMENTS/missions/
    TELEMETRY/missions/
    GROUND_CREW/missions/
    99_archive/
```

## 3. Procedura Ustawieniowa (Bootstrap)

Poniższa procedura wykorzystuje klienta `openclaw` w środowisku Linux/WSL do automatycznego utworzenia całej struktury.

### Krok 1: Ustawienie zmiennej `ROOT_PATH`

Zdefiniuj ścieżkę do głównego katalogu systemu. Zalecane jest umieszczenie go w przestrzeni roboczej OpenClaw.
```bash
export ROOT_PATH="$HOME/.openclaw/workspace/missions"
```

### Krok 2: Uruchomienie Gateway w osobnym profilu

Dla izolacji konfiguracji, użyj dedykowanego profilu `missionctl`.
```bash
openclaw --profile missionctl gateway start
openclaw --profile missionctl gateway status
```

### Krok 3: Weryfikacja dostępu (Sandbox)

Upewnij się, że agent OpenClaw ma uprawnienia do zapisu w `ROOT_PATH`.
```bash
openclaw --profile missionctl sandbox explain
```

### Krok 4: Ustawienie profilu narzędzi (opcjonalnie)

Aby zapewnić dostęp do operacji na plikach, możesz ustawić profil `coding`.
```bash
openclaw --profile missionctl config set tools.profile '"coding"'
```

### Krok 5: Główna komenda bootstrap

To pojedyncze polecenie instruuje agenta OpenClaw, aby utworzył całą strukturę katalogów, pliki konfiguracyjne i szablony.

```bash
openclaw --profile missionctl agent --message "
BOOTSTRAP Mission Management System.

ROOT_PATH=$ROOT_PATH

1) Create directories:
- $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) Write MCC files (overwrite if exist):
A) $ROOT_PATH/_MCC/00_operating-manual.md
# 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
# 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) Empty indices:
- $ROOT_PATH/_MCC/10_backlog.md with '# Backlog (MCC)'
- $ROOT_PATH/_MCC/20_active-missions.md with '# Active Missions (MCC)'
- $ROOT_PATH/_MCC/30_decisions.md with '# Decisions (MCC)'
- $ROOT_PATH/_MCC/90_archive-index.md with '# Archive Index (MCC)'

3) Write 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

Contents:

(task-brief.md)
# [CALLSIGN] Task Brief — <title>
Routing: [CALLSIGN]
Agent: <AgentName>
Mode: SIM | FLIGHT
Priority: P0 | P1 | P2
## Context
## Goal
## Deliverables
## Constraints
## Acceptance Criteria
## Risks

(sim-flight-checklist.md)
# SIM → FLIGHT Checklist
- Acceptance criteria met
- Artifacts linked in 90_links.md
- Risks reviewed
- Verification done (if needed)
- Telemetry plan ready (if needed)
- MCC GO
- PROGRAM LEAD GO (P0/P1)

(post-mission-report.md)
# Post-Mission Report — <title>
Packet:
Decision:
Summary:
Artifacts:
Measurements:
Learnings:
Next Steps:

(decision-record.md)
# Decision Record — <title>
Decision: PROCEED | ITERATE | HOLD | SCRUB
Date:
Owner:
Rationale:
Trade-offs:
Follow-up:

4) Write mapping config:
$ROOT_PATH/_MCC/openclaw.missions.json
Use this exact JSON, but with root_path = ROOT_PATH:

{
  "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"
  }
}

5) After completion, print a short summary of what you created and where.
"
```

## 4. Weryfikacja i Diagnostyka

Po wykonaniu skryptu bootstrap, możesz zweryfikować poprawność instalacji.

### Podgląd logów
```bash
openclaw --profile missionctl logs --follow
```

### Pełny status systemu
```bash
openclaw --profile missionctl status --deep
```

## 5. (Bonus) Utworzenie Pierwszego Pakietu Misji

Aby przetestować działanie systemu, możesz utworzyć pierwszy pakiet misji.
```bash
openclaw --profile missionctl agent --message "
Utwórz Mission Packet w $ROOT_PATH dla:
CALLSIGN: ARTEMIS-TLM
Owner: Pulse
Mode: SIM
Slug: system-check

Folder: YYYY-MM-DD__ARTEMIS-TLM__system-check w ARTEMIS/TELEMETry/missions/
W środku: 00_brief.md, 10_worklog.md, 20_artifacts/, 30_results.md, 40_decision.md, 90_links.md
Dopisz wpis do $ROOT_PATH/_MCC/20_active-missions.md ze statusem IN_PROGRESS.
"
```