Skill Examples (3)

## §7 Per-Skill Examples

### 7.1 task-postflight

**Current behavior:** Evidence written to `/tmp/postflight-/` (when it exists at all). Outcome is terminal output only. Brief (the AC list) exists only in the MC description, not alongside the output.

**After Phase 2:**

```
~/projects/alai/task-postflight/2026-05-05-99292-a1b2c3/
 brief.md # AC list copied from mc.js show at invocation start
 outcome.md # Final pass/fail report with per-AC verdicts
 evidence/ # Raw command outputs, curl responses, screenshots
 01-curl-health.txt
 02-grep-section.txt
 .provenance.json # {mc_id, agent, model, timestamp, skill, client, run_id}
```

**Replaces:** `/tmp/postflight-/` and terminal-only reporting.

**Brief source:** `node ~/system/tools/mc.js show ` description field, written verbatim at run start.

### 7.2 codecraft build / design task

**Current behavior:** Evidence written to `/tmp/-evidence/` (codecraft convention). Brief (the Mehanik-cleared BUILD-BLUEPRINT excerpt) is in the orchestrator's dispatch prompt only — not persisted alongside output. Code diffs, if produced, go to terminal or arbitrary file locations.

**After Phase 2:**

```
~/projects//mc-/evidence/
 brief.md # BUILD-BLUEPRINT section relevant to this MC
 diff.patch # git diff of changes made (if applicable)
 outcome.md # Sub-agent final report (the CODECRAFT SUB-AGENT REPORT block)
 evidence/
 01-build-output.txt
 02-test-results.txt
 .provenance.json
```

**Replaces:** `/tmp/-evidence/` and scattered diff files.

**Brief source:** MC description + BUILD-BLUEPRINT section passed in the dispatch prompt, written to `brief.md` before any tool calls begin.

### 7.3 proveo validation

**Current behavior:** Validation reports go to terminal. Evidence written to `/tmp/proveo--*.txt` (flat files, no directory). Result summary is in the MC outcome field (text string) only. No machine-readable result file.

**After Phase 2:**

```
~/projects//mc-/evidence/
 brief.md # AC list + source-of-truth directory stated at invocation
 outcome.md # Human-readable pass/fail report with per-AC verdicts
 result.json # Machine-readable: {mc_id, pass_count, fail_count, acs: [...]}
 evidence/
 01-ac1-curl.txt
 02-ac2-grep.txt
 03-ac3-wc.txt
 .provenance.json
```

**Replaces:** `/tmp/proveo--*.txt` flat files and terminal-only reporting.

**Brief source:** AC list from `mc.js show ` + any source-of-truth paths stated in the MC description.

---