May 17, 2026, 11:40 PM
This commit is contained in:
Paweł Domański
@@ -0,0 +1,323 @@
|
||||
# Procedura implementacji systemu Mission Management w OpenClaw
|
||||
|
||||
*(profil defaultowy, org‑mode only)*
|
||||
|
||||
***
|
||||
|
||||
## KROK 0 — Wymagania wstępne (5 minut)
|
||||
|
||||
### 0.1 Sprawdź, że OpenClaw działa
|
||||
|
||||
```bash
|
||||
openclaw gateway status
|
||||
```
|
||||
|
||||
Jeśli gateway nie działa:
|
||||
|
||||
```bash
|
||||
openclaw gateway start
|
||||
```
|
||||
|
||||
**Warunek przejścia dalej:**
|
||||
Gateway działa i nie zgłasza błędów.
|
||||
|
||||
***
|
||||
|
||||
### 0.2 Sprawdź sandbox i dostęp do filesystemu
|
||||
|
||||
```bash
|
||||
openclaw sandbox explain
|
||||
```
|
||||
|
||||
Upewnij się, że OpenClaw **może pisać do katalogu domowego**, w szczególności:
|
||||
|
||||
~/.openclaw/workspace/missions
|
||||
|
||||
> Jeśli sandbox nie ma dostępu do `$HOME`, **nie idź dalej** — zmień konfigurację sandboxa
|
||||
> albo ustaw katalog wewnątrz workspace OpenClaw.
|
||||
|
||||
***
|
||||
|
||||
## KROK 1 — Uruchom deterministyczny bootstrap systemu
|
||||
|
||||
### 1.1 Wykonaj JEDNĄ komendę bootstrapującą
|
||||
|
||||
Uruchom dokładnie **tę komendę**, bez modyfikacji:
|
||||
|
||||
```bash
|
||||
openclaw agent --message "$(cat <<'EOF'
|
||||
You are a DETERMINISTIC SYSTEM BOOTSTRAPPER.
|
||||
You MUST write files EXACTLY as provided.
|
||||
You MUST NOT paraphrase, summarize, or infer.
|
||||
UTF-8. Overwrite if exists.
|
||||
Org-mode ONLY. No Markdown.
|
||||
|
||||
ROOT=~/.openclaw/workspace/missions
|
||||
|
||||
############################################
|
||||
# 1. CREATE DIRECTORY STRUCTURE
|
||||
############################################
|
||||
Create directories:
|
||||
- ~/.openclaw/workspace/missions/_MCC
|
||||
- ~/.openclaw/workspace/missions/APOLLO/
|
||||
- ~/.openclaw/workspace/missions/APOLLO/99_archive
|
||||
- ~/.openclaw/workspace/missions/HUBBLE/
|
||||
- ~/.openclaw/workspace/missions/HUBBLE/99_archive
|
||||
- ~/.openclaw/workspace/missions/ARTEMIS/
|
||||
- ~/.openclaw/workspace/missions/ARTEMIS/99_archive
|
||||
|
||||
############################################
|
||||
# 2. WRITE MCC OPERATING FILES (ORG)
|
||||
############################################
|
||||
|
||||
BEGIN_FILE: ~/.openclaw/workspace/missions/_MCC/00_operating-manual.org
|
||||
#+TITLE: Operating Manual — Mission Management System
|
||||
|
||||
* Roles
|
||||
- PROGRAM LEAD :: strategy, priorities, P0/P1 decisions
|
||||
- MISSION CONTROL :: routing, WIP, SIM/FLIGHT, closure
|
||||
|
||||
* Missions
|
||||
- APOLLO :: Flight Systems
|
||||
- HUBBLE :: Mission Story
|
||||
- ARTEMIS :: Mission Outcomes
|
||||
|
||||
* Core Rules
|
||||
- One mission per packet
|
||||
- One packet per task
|
||||
- SIM by default
|
||||
- FLIGHT requires GO
|
||||
- Every packet MUST end with a decision
|
||||
- No work outside packets
|
||||
|
||||
* Packet Standard
|
||||
Each packet directory MUST contain:
|
||||
- 00_brief.org
|
||||
- 10_worklog.org
|
||||
- 20_artifacts/
|
||||
- 30_results.org
|
||||
- 40_decision.org
|
||||
- 90_links.org
|
||||
END_FILE
|
||||
|
||||
BEGIN_FILE: ~/.openclaw/workspace/missions/_MCC/10_backlog.org
|
||||
#+TITLE: MCC Backlog
|
||||
END_FILE
|
||||
|
||||
BEGIN_FILE: ~/.openclaw/workspace/missions/_MCC/20_active-missions.org
|
||||
#+TITLE: Active Missions
|
||||
END_FILE
|
||||
|
||||
BEGIN_FILE: ~/.openclaw/workspace/missions/_MCC/30_decisions.org
|
||||
#+TITLE: Decisions Log
|
||||
END_FILE
|
||||
|
||||
BEGIN_FILE: ~/.openclaw/workspace/missions/_MCC/90_archive-index.org
|
||||
#+TITLE: Archive Index
|
||||
END_FILE
|
||||
|
||||
############################################
|
||||
# 3. WRITE CHEATSHEET (ORG)
|
||||
############################################
|
||||
|
||||
BEGIN_FILE: ~/.openclaw/workspace/missions/_MCC/cheatsheet.org
|
||||
#+TITLE: Mission Management System — Cheatsheet
|
||||
#+OPTIONS: toc:nil num:nil
|
||||
|
||||
* TL;DR
|
||||
- PROGRAM LEAD decides what and why
|
||||
- MCC decides how and when closed
|
||||
- One task = one packet
|
||||
- One mission per packet
|
||||
- SIM default, FLIGHT gated
|
||||
END_FILE
|
||||
|
||||
############################################
|
||||
# 4. SYSTEM CONTRACT
|
||||
############################################
|
||||
|
||||
BEGIN_FILE: ~/.openclaw/workspace/missions/_MCC/system-contract.org
|
||||
#+TITLE: System Contract — Enforcement Rules
|
||||
|
||||
* Authority
|
||||
- PROGRAM LEAD owns strategy and P0/P1 GO
|
||||
- MCC owns routing, WIP, SIM/FLIGHT, closure
|
||||
- Missions execute only within scope
|
||||
|
||||
* FLIGHT Gate
|
||||
FLIGHT allowed ONLY IF:
|
||||
- 30_results.org exists
|
||||
- 40_decision.org exists
|
||||
- Decision is PROCEED
|
||||
- MCC GO exists
|
||||
- PROGRAM LEAD GO exists for P0/P1
|
||||
- APOLLO-VERIFY GO exists for technical FLIGHT
|
||||
END_FILE
|
||||
|
||||
############################################
|
||||
# 5. FINAL OUTPUT
|
||||
############################################
|
||||
|
||||
After completion, output:
|
||||
- OK
|
||||
- List of created directories
|
||||
- List of written files
|
||||
- Any errors encountered
|
||||
EOF
|
||||
)"
|
||||
```
|
||||
|
||||
***
|
||||
|
||||
### 1.2 Zweryfikuj wynik bootstrapu
|
||||
|
||||
```bash
|
||||
tree ~/.openclaw/workspace/missions
|
||||
```
|
||||
|
||||
Powinieneś zobaczyć:
|
||||
|
||||
* `_MCC/` z plikami `.org`
|
||||
* katalogi APOLLO / HUBBLE / ARTEMIS
|
||||
* brak **jakichkolwiek** plików `.md`
|
||||
|
||||
**Warunek przejścia dalej:**
|
||||
Struktura istnieje, pliki `.org` są zapisane.
|
||||
|
||||
***
|
||||
|
||||
## KROK 2 — Ustal tryb pracy OpenClaw (runtime rules)
|
||||
|
||||
### 2.1 Kontrakt operacyjny
|
||||
|
||||
Od tej chwili OpenClaw:
|
||||
|
||||
* ✅ **czyta** pliki `.org`
|
||||
* ✅ **pisze** tylko do:
|
||||
* `20_artifacts/`
|
||||
* `30_results.org`
|
||||
* ❌ **nigdy nie pisze**:
|
||||
* `40_decision.org`
|
||||
* `_MCC/*` (poza backlogiem, jeśli jawnie polecone)
|
||||
|
||||
Decyzje końcowe należą **wyłącznie do MCC / PROGRAM LEAD**.
|
||||
|
||||
***
|
||||
|
||||
### 2.2 Standard komunikatu do OpenClaw
|
||||
|
||||
Każde polecenie do OpenClaw **musi wyglądać tak**:
|
||||
|
||||
```text
|
||||
[MCC][ARTEMIS-TLM]
|
||||
Packet: 2026-02-24__ARTEMIS-TLM__retention-drop-7d
|
||||
Action: Analyze telemetry and update 30_results.org
|
||||
Mode: SIM
|
||||
```
|
||||
|
||||
Jeśli komunikat **nie zawiera CALLSIGN + Packet**, traktuj go jako **niepoprawny**.
|
||||
|
||||
***
|
||||
|
||||
## KROK 3 — Utworzenie pierwszego Mission Packet (ręcznie)
|
||||
|
||||
### 3.1 Utwórz katalog packetu
|
||||
|
||||
Przykład:
|
||||
|
||||
```bash
|
||||
mkdir -p ~/.openclaw/workspace/missions/ARTEMIS/TLM/missions/2026-02-24__ARTEMIS-TLM__system-check
|
||||
cd ~/.openclaw/workspace/missions/ARTEMIS/TLM/missions/2026-02-24__ARTEMIS-TLM__system-check
|
||||
mkdir 20_artifacts
|
||||
touch 00_brief.org 10_worklog.org 30_results.org 40_decision.org 90_links.org
|
||||
```
|
||||
|
||||
### 3.2 Wypełnij `00_brief.org`
|
||||
|
||||
To jest **kontrakt wejściowy** dla agenta.
|
||||
|
||||
***
|
||||
|
||||
## KROK 4 — Wykonanie pracy przez OpenClaw (SIM)
|
||||
|
||||
### 4.1 Zleć pracę
|
||||
|
||||
```bash
|
||||
openclaw agent --message "
|
||||
[MCC][ARTEMIS-TLM]
|
||||
Packet: 2026-02-24__ARTEMIS-TLM__system-check
|
||||
Action: Verify system structure and write findings to 30_results.org
|
||||
Mode: SIM
|
||||
"
|
||||
```
|
||||
|
||||
### 4.2 Sprawdź wyniki
|
||||
|
||||
* `30_results.org` → wypełniony
|
||||
* `20_artifacts/` → opcjonalne pliki
|
||||
* `40_decision.org` → **nadal puste** (tak ma być)
|
||||
|
||||
***
|
||||
|
||||
## KROK 5 — Decyzja MCC (closure)
|
||||
|
||||
### 5.1 MCC podejmuje decyzję
|
||||
|
||||
Ręcznie edytuj:
|
||||
|
||||
```org
|
||||
#+TITLE: Decision — system-check
|
||||
|
||||
* Decision
|
||||
- PROCEED
|
||||
|
||||
* Owner
|
||||
- MCC
|
||||
|
||||
* Rationale
|
||||
System poprawnie zainicjalizowany.
|
||||
|
||||
* Follow-up
|
||||
- [ ] Utworzyć pierwszy realny packet
|
||||
```
|
||||
|
||||
***
|
||||
|
||||
## KROK 6 — (Opcjonalnie) FLIGHT
|
||||
|
||||
Jeśli packet wymaga FLIGHT:
|
||||
|
||||
1. Sprawdź:
|
||||
* `30_results.org` istnieje
|
||||
* `40_decision.org` = PROCEED
|
||||
2. Jeśli P0/P1 → PROGRAM LEAD dopisuje GO
|
||||
3. Jeśli techniczne → APOLLO-VERIFY GO
|
||||
4. Dopiero wtedy **zlecasz FLIGHT OpenClaw**
|
||||
|
||||
***
|
||||
|
||||
## KROK 7 — Archiwizacja
|
||||
|
||||
```bash
|
||||
mv ~/.openclaw/workspace/missions/ARTEMIS/TLM/missions/2026-02-24__ARTEMIS-TLM__system-check \
|
||||
~/.openclaw/workspace/missions/ARTEMIS/99_archive/
|
||||
```
|
||||
|
||||
Dopisz wpis do:
|
||||
|
||||
~/.openclaw/workspace/missions/_MCC/90_archive-index.org
|
||||
|
||||
***
|
||||
|
||||
## ✅ Stan końcowy po implementacji
|
||||
|
||||
Masz:
|
||||
|
||||
* ✅ działający system Mission Management
|
||||
* ✅ org‑mode jako jedyne źródło prawdy
|
||||
* ✅ OpenClaw jako egzekutora
|
||||
* ✅ MCC jako realny gatekeeper
|
||||
* ✅ SIM / FLIGHT jako twardą bramkę decyzyjną
|
||||
|
||||
To jest **kompletna procedura wdrożeniowa**.
|
||||
Od tego momentu **każde nowe zadanie** to tylko nowy Mission Packet — bez zmian w systemie.
|
||||
Reference in New Issue
Block a user