T-511U-sdf-adopt-sections-checks

State: planning/draft · Impact: medium · Complexity: large

Goal

Build adopt sections 3 (deterministic checks), 4 (judgement checks) and 5 (hook points).

Today

The shell stubs all three sections; no checks fixtures exist.

Proposed

Deterministic checks render as a DTable with row toggles and DBadge kinds; hook chains as a DTree; judgement checks as a DCard list with the calibration drill-down. Sections are props-in, emit-out (update:value); only useAdoption() writes the draft. Controls map from sectionRender in docs/planning/strategy/wizard-prototype.html: text to DFieldRow+DInput; packs and posture to DChipChoice; enums and toggles to DSettingRow+DSelect.

Approach

1. Add components/adopt/sections/{Checks,Judgement,Hooks}Section.vue.
2. Add fixtures ChecksCatalog, JudgementCheck and HookPoint under fixtures/adopt/. Gotcha: chain order is semantic, and ids must be stable.
3. Build the calibration drill-down for a judgement check.
4. Add stories Empty and Filled per section.

Areas

Area	Note
solutions/ontological/desktop/src-nuxt/app/components/adopt/sections/	three section components
solutions/ontological/desktop/src-nuxt/app/fixtures/adopt/checks.ts	checks, judgement and hook fixtures
solutions/ontological/desktop/src-nuxt/app/types/adopt.ts	extend draft types

Acceptance criteria

• AC-1: Toggling a check row emits update:value and reordering a hook chain preserves ids and order.
• AC-2: The calibration drill-down opens from a judgement card.
• AC-3: All three sections have Empty and Filled stories.
• AC-4: moon run sdf:check and moon run sdf:test pass, run detached one at a time; nuxi typecheck and vue-tsc are never run locally (CI typechecks).
• AC-5: Every new story renders at the tauriMedium viewport in light and dark, and a screenshot pair is committed under docs/screenshots/sdf-adopt-sections-checks/{light,dark}.png and embedded in the PR body.
• AC-6: Only --d-* tokens, no raw colors; D* components come from @determined/ui; app/generated/*, app.vue, nuxt.config.ts and package.json are untouched unless this task says so.
• AC-7: Fixture timestamps are constants; any force layout has a deterministic seed and a cooldown.

Out of scope

• Autonomy posture (section 7, separate task) and backend enforcement and verify modes.

Dependencies

• Depends on T-XC1D.

Discovery context

• Plan: /Users/sksizer/.claude/plans/toasty-soaring-ullman.md (the adoption wizard and operator screens, built in SDF) and N-6DUQ.
• Control spec: docs/planning/strategy/wizard-prototype.html; strategy: N-HETB-adopting-a-project.
• Rules every agent follows are in the plan and the shared acceptance criteria above; the derive step later replaces fixtures with generated transport.

Depends on

T-XC1D

---

← Back to Tasks