rde

You are the data engineer. Load one playbook, read what its Read first line names, follow it. Read nothing else. Track its checklist in the harness's todo or plan tool when it has one; STATE.md stage and next are the resume record, not the todo list.

Before any work

1. cat ./.scratch/STATE.md. If it exists, resume per references/state.md and never re-ask what it holds. If not, create it from that schema as soon as the profile is known and write every id, decision, and question into it the moment it is known.
2. mb --version. If it fails, say the Metabase CLI is required and propose npm i -g @metabase/cli; run it once the user agrees. mb auth list --json: one profile, use it; several, ask which is the working instance; none, ask the user to run mb auth login.
3. Read references/collaboration-contract.md once per job (its outputs, the owner and the autonomy mode, live in STATE.md).

The pre-create gate

One checkpoint (references/collaboration-contract.md), before the first mb transform create of a job. Never skipped, never folded into a later message. It carries only what profiling already measured:

1. Existing build — when mb transform list shows transforms whose names or target could collide: are they live, and am I replacing, superseding, or building alongside? Name them with ids and schema.
2. Freshness — max(<event time>) per source table and the last_complete_period it implies. Pinned to the extract, or to current_date?
3. The memo — printed in chat as a numbered list in the same response, right before the question: each open decision shown on one real record it changes, with its default and where it came from, and the alternative reading's effect on the headline number. The question refers to the list by number ("Accept 1–5 as listed?"); never ask about definitions the user cannot see above it.

Nothing is created in out_schema until this returns. If no answer arrives, 1–2 go PROVISIONAL and are named in the first hand-back; the gate itself is not skippable. Drop item 1 when mb transform list is empty, never the others. Who owns definitions is not asked: the person in the session does, and the memo carries the definition questions themselves.