@walwal-harness/cli 7.1.9 → 7.1.10

package/HR-Resource/ceo/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: harness-ceo
-description: "CEO/Dispatcher. Owner-facing mission intake, CXX meeting orchestration, event routing, and final Owner reports. Trigger with /goal, /hot-fix, /ceo."
+description: "CEO/Dispatcher. Owner-facing mission intake, CXX meeting orchestration, event routing, and final Owner reports. Trigger with /goal, /submission, /hot-fix, /ceo."
 model: sonnet
 disable-model-invocation: false
 ---
@@ -12,7 +12,7 @@ You are the only direct conversation channel with the Owner.
 ## Mission Protocol
 
 1. Read the Owner request and decide whether brainstorming is needed or execution can start.
-2. Create or update `.harness/documents/{mission_name}/ceo.md`.
+2. Create or update `.harness/documents/{goal-or-child-mission}/ceo.md`.
 3. Ask each CXX only mission-relevant questions:
    - COO: planning, market/reference research, hypothesis validation, mission fit.
    - CDO: branding, UI/UX direction, mock selection, design review.
@@ -28,8 +28,8 @@ You are the only direct conversation channel with the Owner.
 - CXX agents do not execute specialist work directly. They only define scope, choose workers, review outputs, resolve blockers, and report decisions.
 - Every mission must use hired specialist workers for research, planning, design production, implementation, QA, ops checks, or any other domain deliverable. Small scope is not an exemption.
 - If a suitable hired worker is absent, invoke the `harness-hiring` skill before the CXX proceeds with that deliverable.
-- CEO must reject CXX reports that contain completed specialist deliverables without matching worker records under `.harness/documents/{mission_name}/workers/`.
-- Every CXX starts from fresh context and records decisions in `.harness/documents/{mission_name}/{cxx}.md`.
+- CEO must reject CXX reports that contain completed specialist deliverables without matching worker records under `.harness/documents/{goal-or-child-mission}/{owning-cxx}/workers/`.
+- Every CXX starts from fresh context and records decisions in `.harness/documents/{goal-or-child-mission}/{cxx}.md`.
 - Preserve DDD boundaries: domain decisions, application wiring, infrastructure, and quality policy are separate responsibilities.
 - Before CTO/CDO/OPS allocate runnable services, agree with the Owner on a `{xx}000` base port and write it to project `.env` as `HARNESS_BASE_PORT={xx}000`. Mentioning the value in `ceo.md` is not sufficient.
 - After writing `.env`, verify with `grep '^HARNESS_BASE_PORT=' .env` before routing service work.

package/HR-Resource/cqo/SKILL.md

@@ -12,7 +12,7 @@ Own quality, recurrence prevention, and archive eligibility.
 ## Workflow
 
 1. Read CEO and CTO mission context.
-2. Record decisions in `.harness/documents/{mission_name}/cqo.md`.
+2. Record decisions in `.harness/documents/{goal-or-child-mission}/cqo.md`.
 3. Break the CQO scope into worker tasks: e2e, backtest, visual, API, security, performance, regression, and operational verification.
 4. Use the `harness-resource-manager` skill to check available evaluators or reviewers for every task.
 5. Use the `harness-hiring` skill before assigning any task that has no hired worker. Do not complete that task yourself.
@@ -28,7 +28,7 @@ CQO must not directly execute QA, visual review, security review, performance te
 
 **CQO does not communicate with dev workers.** CQO only communicates with CEO and with its own evaluator/tester workers. If CQO needs clarification on implementation details, it routes the question back to CEO → CTO.
 
-Every evaluator/tester dispatched by CQO must write its report under `.harness/documents/{mission_name}/cqo/workers/{worker-name}.md`.
+Every evaluator/tester dispatched by CQO must write its report under `.harness/documents/{goal-or-child-mission}/cqo/workers/{worker-name}.md`.
 
 Required output sections in `cqo.md`:
 
@@ -40,7 +40,7 @@ Required output sections in `cqo.md`:
 
 ## Worker Report Note Requirement
 
-Every CQO evaluator/tester brief must require the worker to append this English block to the bottom of `.harness/documents/{mission_name}/cqo/workers/{worker-name}.md`:
+Every CQO evaluator/tester brief must require the worker to append this English block to the bottom of `.harness/documents/{goal-or-child-mission}/cqo/workers/{worker-name}.md`:
 
 ```
 ## Implementation Notes

package/HR-Resource/cto/SKILL.md

@@ -12,7 +12,7 @@ Own engineering execution for the mission.
 ## Workflow
 
 1. Read CEO, COO, and CDO mission documents.
-2. Record decisions in `.harness/documents/{mission_name}/cto.md`. **This file must be created before any worker is dispatched.**
+2. Record decisions in `.harness/documents/{goal-or-child-mission}/cto.md`. **This file must be created before any worker is dispatched.**
 3. Break the CTO scope into worker tasks: architecture review, backend, frontend, app, web, data, DevOps, integration, implementation, and technical QA.
 4. Use the `harness-resource-manager` skill to find hired workers for every task.
 5. Use the `harness-hiring` skill before assigning any missing specialty. Do not complete that task yourself.
@@ -26,9 +26,9 @@ Own engineering execution for the mission.
 
 CTO must not directly write code, create build scripts, choose detailed implementation content, run technical QA as the evaluator, or produce final implementation artifacts. CTO may only design boundaries, brief workers, coordinate ports/config, review worker outputs, and record accepted decisions with worker names and report paths.
 
-**cto.md is a prerequisite gate.** No worker may be dispatched before `cto.md` exists. A mission where workers appear in `.harness/documents/{mission_name}/workers/` but no `cto.md` exists is a protocol violation — CEO bypassed CTO.
+**cto.md is a prerequisite gate.** No worker may be dispatched before `cto.md` exists. A mission where workers appear in `.harness/documents/{goal-or-child-mission}/cto/workers/` but no `cto.md` exists is a protocol violation — CEO bypassed CTO.
 
-Every worker dispatched by CTO must be listed in the Worker Evidence Manifest section of `cto.md` with their report path and status. The report path must be `.harness/documents/{mission_name}/cto/workers/{worker-name}.md`. Workers not listed there are invisible to the harness and their output cannot be accepted.
+Every worker dispatched by CTO must be listed in the Worker Evidence Manifest section of `cto.md` with their report path and status. The report path must be `.harness/documents/{goal-or-child-mission}/cto/workers/{worker-name}.md`. Workers not listed there are invisible to the harness and their output cannot be accepted.
 
 Required output sections in `cto.md`:
 
@@ -41,7 +41,7 @@ Required output sections in `cto.md`:
 
 ## Worker Report Note Requirement
 
-Every CTO worker brief must require the worker to append this English block to the bottom of `.harness/documents/{mission_name}/cto/workers/{worker-name}.md`:
+Every CTO worker brief must require the worker to append this English block to the bottom of `.harness/documents/{goal-or-child-mission}/cto/workers/{worker-name}.md`:
 
 ```
 ## Implementation Notes

package/README.md

@@ -10,7 +10,7 @@ One project = one company. The Owner speaks only to the CEO. The CEO speaks only
 
 ```
 Owner
-  └─ /goal · /hot-fix
+  └─ /goal · /submission · /hot-fix
       └─ harness-ceo          orchestrator — Owner's only contact
           ├─ harness-coo      research, hypothesis, service direction
           ├─ harness-cdo      branding, UI/UX, design review
@@ -48,6 +48,7 @@ What `init` installs:
 | Path | Contents |
 |---|---|
 | `.claude/commands/goal.md` | `/goal` Owner command |
+| `.claude/commands/submission.md` | `/submission` Owner command |
 | `.claude/commands/hot-fix.md` | `/hot-fix` Owner command |
 | `.claude/skills/harness-{ceo,coo,cdo,cto,cqo,ops}/` | CXX agent skills |
 | `.harness/shared/HR-Resource/` | Hireable worker skill pool |
@@ -79,6 +80,16 @@ Owner /hot-fix → CEO → CTO → [dev workers] → CQO → [evaluator workers]
 
 **Complete when:** `cto.md` + `cqo.md` + at least one `.harness/gotchas/` or `.harness/conventions/` entry exist.
 
+### Submission
+
+```
+Owner /submission → CEO → [relevant CXX] → [workers] → [convention updates]
+```
+
+1. CEO locates the active `.harness/documents/goal-{index}-{name}/`.
+2. CEO creates `.harness/documents/goal-{index}-{name}/submission-{index}-{name}/`.
+3. Relevant CXX update `.harness/conventions/` when the new requirement changes durable project rules.
+
 ---
 
 ## Hard Rules
@@ -93,7 +104,7 @@ Owner /hot-fix → CEO → CTO → [dev workers] → CQO → [evaluator workers]
 | 6 | CEO routes only to CXX — never directly to workers |
 | 7 | No CXX self-execution — deliverables without matching worker records are rejected |
 | 8 | No verdict without worker evidence — CQO self-inspection is not valid |
-| 9 | Hierarchical worker ownership — worker reports live under `.harness/documents/{mission}/{owning-cxx}/workers/` |
+| 9 | Hierarchical worker ownership — worker reports live under `.harness/documents/{goal-or-child-mission}/{owning-cxx}/workers/` |
 | 10 | Implementation Notes required — `ceo.md`, every `{cxx}.md`, and every worker report must end with an English `## Implementation Notes` section |
 
 ### Implementation Notes Format
@@ -170,7 +181,7 @@ npx walwal-harness init --force --project-root /path/to/project
 Features:
 
 - **Org Tree** — live status of Owner → CEO → CXX → Workers hierarchy
-- **Mission Timeline** — clickable history of goal/hot-fix missions showing the full dispatch chain
+- **Mission Timeline** — clickable history of goal/submission/hot-fix missions showing the full dispatch chain
 - **Mission Flow tab** — per-mission flow: Owner prompt → CEO routing → CXX → worker files changed → CQO verdict
 - **History tab** — mission-specific Owner request (from CEO summary + closest progress.log match)
 - **Gotchas tab** — searchable `.harness/gotchas/*.md` knowledge base, click to read full markdown
@@ -182,8 +193,10 @@ Features:
 
 | Path | Role |
 |---|---|
-| `.harness/documents/{mission}/` | CXX decisions and worker reports per mission |
-| `.harness/documents/{mission}/{cxx}/workers/` | Worker reports owned by that CXX |
+| `.harness/documents/goal-{index}-{name}/` | Goal-level CXX decisions and worker reports |
+| `.harness/documents/goal-{index}-{name}/submission-{index}-{name}/` | Additional requirement under the active goal |
+| `.harness/documents/goal-{index}-{name}/hotfix-{index}-{name}/` | Emergency fix under the active goal |
+| `.harness/documents/{goal-or-child-mission}/{cxx}/workers/` | Worker reports owned by that CXX |
 | `.harness/conventions/` | Durable rules (CQO writes, survives missions) |
 | `.harness/gotchas/` | Recurrence-prevention records (CQO registers per hot-fix) |
 | `.harness/shared/HR-Resource/` | Hireable worker skill pool |

package/apps/harness-dashboard/components/MissionTimeline.tsx

@@ -153,7 +153,9 @@ export function MissionTimeline({
         const typeBadge =
           mission.type === "hotfix"
             ? "[🔥 hot-fix]"
-            : mission.type === "feature"
+            : mission.type === "submission"
+            ? "[+ submission]"
+            : mission.type === "goal" || mission.type === "feature"
             ? "[✦ goal]"
             : "[— unknown]";
         const shortId =
@@ -188,6 +190,8 @@ export function MissionTimeline({
                   className={`shrink-0 font-mono text-[9px] rounded px-1.5 py-0.5 border ${
                     mission.type === "hotfix"
                       ? "bg-rose-500/15 text-rose-300 border-rose-500/30"
+                      : mission.type === "submission"
+                      ? "bg-sky-500/15 text-sky-300 border-sky-500/30"
                       : "bg-emerald-500/15 text-emerald-300 border-emerald-500/30"
                   }`}
                 >

package/apps/harness-dashboard/components/OrgTree.tsx

@@ -129,7 +129,7 @@ export function OrgTree({ snapshot, activeNodeId, onNodeClick }: OrgTreeProps) {
     id: "owner",
     role: "owner",
     label: "Owner",
-    sublabel: "/goal · /hot-fix",
+    sublabel: "/goal · /submission · /hot-fix",
     status: "idle",
     activity: snapshot.ownerHistory?.[0]?.content.slice(0, 80) ?? null,
     agentIds: [],

package/apps/harness-dashboard/components/Scene.tsx

@@ -120,7 +120,7 @@ export function Scene({ snapshot: initial, lang = "ko" }: SceneProps) {
         <section className="mt-4">
           <div className="mb-2">
             <p className="font-mono text-[10px] uppercase tracking-[0.2em] text-cyan-300/60">Mission History</p>
-            <p className="text-[11px] text-gray-500 mt-0.5">goal · hot-fix 명령별 파생 작업 흐름</p>
+            <p className="text-[11px] text-gray-500 mt-0.5">goal · submission · hot-fix 명령별 파생 작업 흐름</p>
           </div>
           <MissionTimeline
             missions={snapshot.missions ?? []}

package/apps/harness-dashboard/components/drawer/MissionFlowTab.tsx

@@ -288,7 +288,8 @@ export function MissionFlowTab({ mission, ownerHistory }: Props) {
 
   const typeBadge =
     mission.type === "hotfix" ? "[🔥 hot-fix]"
-    : mission.type === "feature" ? "[✦ goal]"
+    : mission.type === "submission" ? "[+ submission]"
+    : mission.type === "goal" || mission.type === "feature" ? "[✦ goal]"
     : "[— unknown]";
 
   let dateStr = "—";
@@ -341,6 +342,8 @@ export function MissionFlowTab({ mission, ownerHistory }: Props) {
             className={`font-mono text-[9px] rounded border px-1.5 py-0.5 ${
               mission.type === "hotfix"
                 ? "bg-rose-500/15 text-rose-300 border-rose-500/30"
+                : mission.type === "submission"
+                ? "bg-sky-500/15 text-sky-300 border-sky-500/30"
                 : "bg-emerald-500/15 text-emerald-300 border-emerald-500/30"
             }`}
           >

package/apps/harness-dashboard/components/drawer/OwnerHistoryTab.tsx

@@ -92,6 +92,8 @@ export function OwnerHistoryTab({ ownerHistory, mission, onEntryClick }: Props)
                   className={`font-mono text-[9px] px-1.5 py-0.5 rounded ${
                     closestEntry.type === "goal"
                       ? "bg-emerald-500/15 text-emerald-300"
+                      : closestEntry.type === "submission"
+                      ? "bg-sky-500/15 text-sky-300"
                       : closestEntry.type === "hot-fix"
                       ? "bg-rose-500/15 text-rose-300"
                       : "bg-gray-500/15 text-gray-400"
@@ -140,6 +142,8 @@ export function OwnerHistoryTab({ ownerHistory, mission, onEntryClick }: Props)
               className={`font-mono text-[9px] px-1.5 py-0.5 rounded ${
                 entry.type === "goal"
                   ? "bg-emerald-500/15 text-emerald-300"
+                  : entry.type === "submission"
+                  ? "bg-sky-500/15 text-sky-300"
                   : entry.type === "hot-fix"
                   ? "bg-rose-500/15 text-rose-300"
                   : "bg-gray-500/15 text-gray-400"

package/apps/harness-dashboard/lib/harness-state.ts

@@ -957,15 +957,41 @@ function readMissions(rootDir: string, limit = 15): MissionDoc[] {
   const docsDir = path.join(rootDir, ".harness", "documents");
   if (!existsSync(docsDir)) return [];
 
-  let entries: Dirent[];
-  try {
-    entries = readdirSync(docsDir, { withFileTypes: true });
-  } catch { return []; }
+  const missionDirs: Array<{ rel: string; abs: string }> = [];
+  const cxxDocNames = new Set(["ceo.md", "cto.md", "cqo.md", "coo.md", "cdo.md", "ops.md"]);
+
+  const collectMissionDirs = (baseDir: string, relPrefix = "") => {
+    let entries: Dirent[];
+    try {
+      entries = readdirSync(baseDir, { withFileTypes: true });
+    } catch { return; }
+
+    const hasMissionDoc = entries.some((entry) => entry.isFile() && cxxDocNames.has(entry.name));
+    if (hasMissionDoc && relPrefix) {
+      missionDirs.push({ rel: relPrefix, abs: baseDir });
+    }
+
+    for (const entry of entries) {
+      if (!entry.isDirectory() || entry.name.startsWith(".")) continue;
+      if (["workers", "coo", "cdo", "cto", "cqo", "ops"].includes(entry.name)) continue;
+      const childRel = relPrefix ? `${relPrefix}/${entry.name}` : entry.name;
+      collectMissionDirs(path.join(baseDir, entry.name), childRel);
+    }
+  };
+
+  collectMissionDirs(docsDir);
+
+  const typeFromId = (id: string): MissionDoc["type"] => {
+    const base = id.split("/").pop() ?? id;
+    if (/^goal[-_]/i.test(base)) return "goal";
+    if (/^submission[-_]/i.test(base)) return "submission";
+    if (/^hot[-_]?fix[-_]/i.test(base) || /^hotfix[-_]/i.test(base)) return "hotfix";
+    if (/^F\d+/i.test(base)) return "feature";
+    return "unknown";
+  };
 
-  const missions = entries
-    .filter(d => d.isDirectory() && !d.name.startsWith("."))
-    .map(d => {
-      const missionPath = path.join(docsDir, d.name);
+  const missions = missionDirs
+    .map(({ rel, abs: missionPath }) => {
       let mtime: Date;
       try { mtime = statSync(missionPath).mtime; } catch { mtime = new Date(0); }
 
@@ -1004,12 +1030,13 @@ function readMissions(rootDir: string, limit = 15): MissionDoc[] {
       const cxxRoles = ["ceo", "cto", "cqo", "coo", "cdo", "ops"] as const;
       const cxxPresent = cxxRoles.filter(role => existsSync(path.join(missionPath, `${role}.md`)));
 
-      const id = d.name;
+      const id = rel;
+      const label = rel.split("/").pop() ?? rel;
       return {
         missionId: id,
         ts: mtime.toISOString(),
-        type: id.startsWith("hotfix") ? "hotfix" : id.match(/^F\d+/) ? "feature" : "unknown",
-        label: id,
+        type: typeFromId(id),
+        label,
         ceo: readMd("ceo.md"),
         cto: readMd("cto.md"),
         cqo: readMd("cqo.md"),
@@ -1039,11 +1066,15 @@ function readOwnerHistory(rootDir: string, limit = 30): OwnerPromptEntry[] {
     const parts = line.split(" | ");
     if (parts.length < 4) continue;
     const ts = parts[0]?.trim() ?? "";
+    const eventType = parts[2]?.trim() ?? "input";
     const content = parts.slice(3).join(" | ").trim();
     if (!content) continue;
     const lc = content.toLowerCase();
-    const type = content.startsWith("/goal") ? "goal" :
-                 (content.startsWith("/hot-fix") || lc.includes("/hot-fix")) ? "hot-fix" : "other";
+    const type =
+      eventType === "goal" || content.startsWith("/goal") ? "goal" :
+      eventType === "submission" || content.startsWith("/submission") || lc.includes("/submission") ? "submission" :
+      eventType === "hot-fix" || content.startsWith("/hot-fix") || lc.includes("/hot-fix") ? "hot-fix" :
+      "other";
     entries.push({ ts, content, type });
   }
   return entries.reverse().slice(0, limit);

package/apps/harness-dashboard/lib/types.ts

@@ -291,7 +291,7 @@ export interface WorkerDocEntry {
 export interface MissionDoc {
   missionId: string;
   ts: string;
-  type: "hotfix" | "feature" | "unknown";
+  type: "goal" | "submission" | "hotfix" | "feature" | "unknown";
   label: string;
   ceo: string | null;
   cto: string | null;
@@ -306,7 +306,7 @@ export interface MissionDoc {
 export interface OwnerPromptEntry {
   ts: string;
   content: string;
-  type: "goal" | "hot-fix" | "other";
+  type: "goal" | "submission" | "hot-fix" | "other";
 }
 
 export interface GotchaEntry {

package/assets/templates/AGENTS-ko.md.template

@@ -74,12 +74,13 @@
 
 ## 5. 진입점
 
-Owner가 회사에 접근하는 명령은 두 개뿐이다. 그 외의 경로는 없다.
+Owner가 회사에 접근하는 명령은 세 개뿐이다. 그 외의 경로는 없다.
 
 | 명령 | 사용 시점 |
 |---|---|
 | `/goal` | 미션 설정, 수정, 추가 |
-| `/hot-fix` | 활성 goal과 독립된 긴급 수정 |
+| `/submission` | 활성 goal 하위의 추가 요구사항 |
+| `/hot-fix` | 활성 goal 하위의 긴급 수정 |
 
 `/ceo`, `/cto`, `/cqo`, `/coo`, `/cdo`, `/ops`, `/hiring`은 slash command가 아니다.
 내부 라우팅은 agent/skill wiring으로만 처리한다.
@@ -88,7 +89,7 @@ Owner가 회사에 접근하는 명령은 두 개뿐이다. 그 외의 경로는
 
 ```
 Owner
-  └─ /goal 또는 /hot-fix
+  └─ /goal, /submission, 또는 /hot-fix
       └─ harness-ceo          오케스트레이터 — Owner의 유일한 접점
           ├─ harness-coo      리서치, 가설, 서비스 방향
           ├─ harness-cdo      브랜딩, UI/UX, 디자인 리뷰
@@ -99,7 +100,7 @@ Owner
 
 각 CXX는:
 - **독립된 fresh session 컨텍스트**에서 실행된다 — CEO 세션과 메모리를 공유하지 않는다
-- 결정을 `.harness/documents/{mission_name}/{cxx}.md`에 기록한다
+- 결정을 `.harness/documents/{goal-or-child-mission}/{cxx}.md`에 기록한다
 - 모든 전문 작업을 hired worker에게 위임한다 — 직접 실행하지 않는다
 - 필요한 worker가 없으면 `harness-hiring`을 먼저 호출한다
 
@@ -114,7 +115,17 @@ CEO는 worker 기록 없이 완료된 산출물을 포함한 CXX 보고서를
 3. 각 CXX가 worker를 고용하고, 위임하고, 결과를 수집하여 `{cxx}.md`에 기록한다.
 4. CEO가 CXX 산출물을 종합하여 다음 CXX에 라우팅하거나 Owner에게 보고한다.
 
-**완료 기준:** `.harness/documents/{mission_name}/ceo.md`에 최종 Owner 보고가 존재한다.
+**완료 기준:** `.harness/documents/goal-{index}-{name}/ceo.md`에 최종 Owner 보고가 존재한다.
+
+### Submission
+
+1. CEO가 활성 goal을 `.harness/documents/goal-{index}-{name}/`에서 찾는다.
+2. CEO가 `.harness/documents/goal-{index}-{name}/submission-{index}-{name}/ceo.md`를 만든다.
+3. CEO는 추가 요구사항에 필요한 CXX만 라우팅한다.
+4. 추가 요구사항이 지속 규칙을 바꾸면 관련 CXX가 `.harness/conventions/`를 갱신한다.
+5. Worker는 `{owning-cxx}/workers/` 아래에 보고하고, CXX는 선택과 위험을 `{cxx}.md`에 요약한다.
+
+**완료 기준:** submission 하위 디렉터리에 CEO/CXX 기록, 필요한 worker evidence, 필요한 convention 업데이트가 존재한다.
 
 ### Hot Fix
 
@@ -132,7 +143,9 @@ CEO는 worker 기록 없이 완료된 산출물을 포함한 CXX 보고서를
 
 | 경로 | 역할 |
 |---|---|
-| `.harness/documents/{mission}/` | 미션별 CXX 결정 기록 및 worker 보고서 |
+| `.harness/documents/goal-{index}-{name}/` | goal 레벨 CXX 결정 기록 및 worker 보고서 |
+| `.harness/documents/goal-{index}-{name}/submission-{index}-{name}/` | 활성 goal 하위의 추가 요구사항 |
+| `.harness/documents/goal-{index}-{name}/hotfix-{index}-{name}/` | 활성 goal 하위의 긴급 수정 |
 | `.harness/conventions/` | 지속 규칙 (CQO가 작성, 미션을 넘어 유지) |
 | `.harness/gotchas/` | 재발 방지 기록 (CQO가 hot-fix마다 작성) |
 | `.harness/memories/` | 장기 공유 컨텍스트 |

package/assets/templates/AGENTS.md.template

@@ -6,12 +6,13 @@
 
 ## 1. Entry Points
 
-Two Owner-facing commands. Nothing else reaches the company.
+Three Owner-facing commands. Nothing else reaches the company.
 
 | Command | When |
 |---|---|
 | `/goal` | Set, update, or extend a mission |
-| `/hot-fix` | Emergency fix independent of the active goal |
+| `/submission` | Add a requirement under the active goal |
+| `/hot-fix` | Emergency fix under the active goal |
 
 `/ceo`, `/cto`, `/cqo`, `/coo`, `/cdo`, `/ops`, `/hiring` are not slash commands.
 Internal routing uses agent/skill wiring only.
@@ -36,7 +37,7 @@ For goal: define verifiable success criteria before CEO routes to CXX.
 
 ```
 Owner
-  └─ /goal or /hot-fix
+  └─ /goal, /submission, or /hot-fix
       └─ harness-ceo          orchestrator — Owner's only contact
           ├─ harness-coo      research, hypothesis, service direction
           ├─ harness-cdo      branding, UI/UX, design review
@@ -47,7 +48,7 @@ Owner
 
 Each CXX:
 - Runs in a **fresh session context** — no shared memory with CEO's session
-- Records decisions in `.harness/documents/{mission_name}/{cxx}.md`
+- Records decisions in `.harness/documents/{goal-or-child-mission}/{cxx}.md`
 - Delegates all specialist work to hired workers — never executes directly
 - If a required worker is absent, invokes `harness-hiring` before assigning
 
@@ -64,7 +65,17 @@ CEO rejects any CXX report that contains completed deliverables without matching
 3. Each CXX hires workers, collects reports, records decisions in `{cxx}.md`.
 4. CEO aggregates CXX outputs, routes to next CXX or reports to Owner.
 
-**Complete when:** `.harness/documents/{mission_name}/ceo.md` contains a final Owner report.
+**Complete when:** `.harness/documents/goal-{index}-{name}/ceo.md` contains a final Owner report.
+
+### Submission
+
+1. CEO locates the active goal under `.harness/documents/goal-{index}-{name}/`.
+2. CEO creates `.harness/documents/goal-{index}-{name}/submission-{index}-{name}/ceo.md`.
+3. CEO routes only the CXX needed for the added requirement.
+4. Relevant CXX update `.harness/conventions/` when the new requirement changes durable project rules.
+5. Workers report under `{owning-cxx}/workers/`; CXX summarize choices in `{cxx}.md`.
+
+**Complete when:** the submission child directory has CEO/CXX records, required worker evidence, and any convention updates required by the new requirement.
 
 ### Hot Fix
 
@@ -84,7 +95,9 @@ Note: A docmeta skip decision on harness documents (ceo.md, cto.md, cqo.md, work
 
 | Path | Role |
 |---|---|
-| `.harness/documents/{mission}/` | CXX decisions and worker reports per mission |
+| `.harness/documents/goal-{index}-{name}/` | Goal-level CXX decisions and worker reports |
+| `.harness/documents/goal-{index}-{name}/submission-{index}-{name}/` | Additional requirement under the active goal |
+| `.harness/documents/goal-{index}-{name}/hotfix-{index}-{name}/` | Emergency fix under the active goal |
 | `.harness/conventions/` | Durable rules (CQO writes, survives missions) |
 | `.harness/gotchas/` | Recurrence-prevention records (CQO writes per hot-fix) |
 | `.harness/memories/` | Long-term shared context |
@@ -107,7 +120,7 @@ Note: A docmeta skip decision on harness documents (ceo.md, cto.md, cqo.md, work
 7. **CEO routes only to CXX — never to workers** — CEO must not dispatch, hire, or brief specialist workers directly. Implementation workers are hired by CTO. Evaluator/tester workers are hired by CQO.
 8. **No CXX self-execution** — CXX agents coordinate and manage only. A CXX that produces deliverables without matching worker records has violated its scope. CEO must reject such reports.
 9. **No verdict without worker evidence** — CQO cannot issue ACCEPTED/REJECTED without a Worker Evidence Manifest referencing at least one evaluator worker. Self-inspection by CQO is not valid evidence.
-10. **Hierarchical worker ownership** — Hired workers are installed under `.claude/skills/{owning-cxx}/{worker}/` and `.codex/skills/{owning-cxx}/{worker}/`; mission worker reports live under `.harness/documents/{mission}/{owning-cxx}/workers/`. Flat `{mission}/workers/` reports are legacy and signal an ownership violation unless explicitly migrated.
+10. **Hierarchical worker ownership** — Hired workers are installed under `.claude/skills/{owning-cxx}/{worker}/` and `.codex/skills/{owning-cxx}/{worker}/`; mission worker reports live under `.harness/documents/{goal-or-child-mission}/{owning-cxx}/workers/`. Flat `{mission}/workers/` reports are legacy and signal an ownership violation unless explicitly migrated.
 11. **Implementation Notes required** — `ceo.md`, every `{cxx}.md`, and every worker report must end with an English `## Implementation Notes` section containing `Design Decisions`, `Deviations`, `Tradeoffs`, and `Open Questions`. Use `None` for empty subsections.
 
 ---