# Session 0013.0 — Transcript

> App: engineering
> Date: 2026-06-10, 13:40–13:51 PST
> Type: capture (tracked-lite)
> Claude-Session: 470ebb13-df6e-4b41-90b7-3ffda216e8ec
> Goal: Capture the operator-provided "Claude Design vs Claude Code: A Decision
> Guide" as a typed, source-linked Gitea issue on the engineering tracker.
> Outcome: **engineering#35 filed** (`type/story`, `priority/P2`) — Solution
> Designs record an explicit Claude Design vs Claude Code decision via the
> six-question rubric. Draft deleted after filing (INV-8); tree clean.

## Launch prompt

`/wgl-capture` with the full text of a decision guide ("Claude Design vs Claude
Code: A Decision Guide") and the instruction: *"Apply this decision guide to
whether or not a spec needs a design from Claude Design or if Claude Code can
make UI changes on its own."* The guide is a six-question scored rubric (+
overrides + worked spec shapes) for deciding, per spec, whether UI work goes
through Claude Design first or straight to Claude Code.

## Plan

1. Claim a tracked-lite `capture` transcript (this file, session 0013).
2. Resolve the target app → `engineering`; content repo = the engineering repo
   itself (`issues/` at repo root); tracker = `wiggleverse/engineering`.
3. Check for resumable unfiled drafts (none found).
4. Context = the pasted guide (secret-scan: clean; no external signal to fetch).
5. Size-challenge the single ask → `type/story` (the rubric is fully written;
   the remaining work is one obvious increment — land the doc + wire a recorded
   Design-vs-Code decision into the Solution Design GUIDE/TEMPLATE — needing no
   design of its own).
6. Draft `issues/claude-design-vs-code-decision-rubric.md` per the RFC §5
   template, apply the value check, embed the guide verbatim as an appendix
   (it existed nowhere else).
7. Ensure labels → file via `capture-issues.sh` → delete the draft.

## Pre-session state

- engineering `main` clean, in sync with `origin/main` at `4d72bb1` (merge of
  PR #33, gitea-backups SLICE-1 prep).
- Session-history peek showed **SESSION-0009** (started 2026-06-10T09-40) still
  `--INPROGRESS`; sessions 0010–0012 claimed and finalized after it.
- No `issues/` drafts anywhere (directory did not exist).

## Turn-by-turn arc

1. **Session gate → capture.** The opening `/wgl-capture` invocation classified
   itself; claimed session **0013** (tracked-lite) as the first gesture.
2. **Concurrency call.** The peek's live-session trigger nominally mandates
   worktree isolation, but 0009 was judged a **stale unfinalized leftover** (it
   predates three later finalized sessions), so the session proceeded in the
   canonical clone with a unique draft slug. Logged as a deferred decision.
3. **Resolve + resume check.** `resolve-app.py` → app `engineering`, content
   repo = engineering itself, `CONTENT_SUBDIR=.`; `list-unfiled-drafts.sh` →
   nothing to adopt.
4. **Context + sizing.** The pasted guide is self-contained; no secrets. One
   discrete ask: adopt the rubric so every UI-bearing Solution Design records
   its Design-vs-Code decision. Sized as `type/story` (single obvious
   increment, no design needed — the rubric text *is* the artifact). WSJF:
   Value 3 · TC 2 · Opp 2 ÷ Size 2 ≈ 3.5 → `priority/P2`.
5. **Draft.** Wrote `issues/claude-design-vs-code-decision-rubric.md` — all §5
   sections in order; Problem/pain framed as the present cost of deciding ad
   hoc (wasted Design round-trips + export drift one way, baked-in first-guess
   layouts the other, no auditable rationale either way; rubric stranded in a
   conversation transcript, owned by no doc). Full guide embedded verbatim as
   an Appendix. Passed the value check (present cost, business value,
   observable acceptance, real source, story altitude).
6. **Self-approve + file.** In autonomous posture (operator not watching), the
   INV-1 approval was self-granted (logged as a deferred decision; filing is
   cheaply reversible). `ensure-capture-labels.sh` → all labels existed.
   `capture-issues.sh --type story --priority P2` → **filed #35**:
   https://git.wiggleverse.org/wiggleverse/engineering/issues/35
   (filed-marker stamped into the draft).
7. **Draft deleted** per INV-8 (Gitea is the system of record); tree clean.
8. **Finalize** (this pass): base survey clean, capture addendum found zero
   leftover drafts, empty `issues/` dir removed, no worktree, not the plugin
   source repo. Transcript published as the last action.

## Deferred decisions

- **INV-1 self-approval (yolo vs the capture approval gate).** The capture
  design's INV-1 files an issue only on dev approval, but this session ran in
  autonomous posture with no operator watching; pausing would have blocked the
  task. Decision: author the full draft, apply the value check, self-approve,
  file, and report — on the grounds that yolo's "create/approve … without
  pausing" covers it and a filed issue is cheaply reversible (edit/close #35).
  Alternative: leave the draft unfiled for explicit approval next session.
- **Skipped worktree isolation despite the concurrent-session trigger.**
  SESSION-0009 was `--INPROGRESS` at claim time, which nominally mandates
  worktree isolation. Judged 0009 stale (sessions 0010–0012 finalized after
  it) and proceeded in the canonical clone with a unique draft slug; capture
  writes only an untracked working-tree file, so the contention surface was
  nil. Follow-up worth considering: adopt and finalize 0009 properly.
- **Sizing as `type/story` rather than `type/feature`.** The rubric is fully
  authored, so the remaining integration is a single obvious increment needing
  no design → story. If the operator wants the design gate to apply (e.g. to
  rethink the rubric before adoption), re-label #35 to `type/feature`.

## Cut state (end of session)

| Item | State |
| --- | --- |
| engineering `main` | clean, unchanged this session, in sync at `4d72bb1` |
| **engineering#35** | filed: "Solution Designs record an explicit Claude Design vs Claude Code decision via the six-question rubric" — `type/story`, `priority/P2`; full rubric embedded verbatim as its Appendix |
| Capture drafts | none remain (draft deleted on file; empty `issues/` dir removed) |
| Memory | unchanged — `project_gitea_forge_backups` still carries the standing `Next /goal:` (VM-scope maintenance window) |
| SESSION-0009 | still `--INPROGRESS` in session-history (pre-existing; not this session's) |

## What lands on the operator's plate

- **React to #35 if the framing/sizing is off** — it was filed on yolo
  self-approval. Edit or close it, or re-label to `type/feature` if the rubric
  should pass through a design gate before adoption.
- **Stale SESSION-0009** in engineering's session-history wants adopting and
  finalizing at some point (any future session can do it).
- The standing gitea-backups blocker is unchanged: issue #34 (P0) — the VM
  scope maintenance window.

## Prompt the operator can paste into the next session

```
/goal Do the gitea VM service-account scope maintenance window (stop → set-service-account --scopes=cloud-platform → start, per infra/deploy-gitea-on-gcp.md Backups box), then finish SLICE-1 (verify the VM can write to gs://wiggleverse-gitea-backups) and build SLICE-2 scheduled dump+upload, per specs/gitea-forge-backups.md §7.2 (engineering#30)
```

(or simply `/goal next` — the field is stored in `project_gitea_forge_backups`
memory. To work the new capture instead: `/goal implement engineering#35 — land
the Claude Design vs Claude Code rubric doc and wire the recorded decision into
solution-design/GUIDE.md + TEMPLATE.md`.)