UX3 — Pulse/run catalog browser (master-detail) (E1)

[jack-champagne]

Part of the seam UX-prototype track (Krishna interview). Sequencing: comprehensive — after the basics (UX1/UX2).

What

The pulse/run catalog browser — master-detail: a left list of pulses (name · tag · 6-char hash) with QILC runs and Results sections; click a row → detail pane (metadata + pulse plot + high-level metrics). Addresses his #1 pain: "annoying to look at file struct."

Krishna's signal (interview 2026-06-30, p2 + p4)

• master-detail sketch (p4): a pulses list with (i)/edit/✓ row affordances → detail pane; QILC runs + Results sections
• pulse identity: tags → timestamps → 6-char hashes (p2)
• his open structure question: flat vs per-system/per-gate — he leaned flat ("iterations w/ flat structure give good history")

Seam-prototype approach

List + detail webview fed by a fake set of run.toml / result.toml / catalog-entry fixtures (grounded in @amicode/schema). No RunsManager/CatalogStore. Build both a flat and a per-system/gate arrangement so we can A/B them in front of Krishna.

Feedback questions for Krishna / Andrew

1. Flat vs per-system/per-gate? — his own open question; this prototype is the experiment that answers it.
2. What identifiers/columns make a pulse findable at a glance (tag, hash, date, fidelity, gate)?

Lanes

• Kate — list+detail layout, both structures (media/)
• Raghav — webview shell + contract test + fixture loader
• Jack — columns/sections + the flat-vs-nested call after feedback

Refs: spec-20260529-amicode-architecture (CatalogStore per-lab, RunInspector), plan-20260603-124231-amicode-phased-build (Phase 3). Phase-3 surface, prototyped early to de-risk the catalog data model.

[jack-champagne]

On the flat-vs-per-system/gate question (Krishna's open Q): the workflow-frames spec §5 answers it — content-addressing resolves it in favor of flat. A pulse_hash catalog key + system_hash/formulation_hash gives you flat-with-good-history AND the two comparison axes (robustness / reformulation), without a rigid per-system/gate tree. So the A/B in this prototype should be flat backed by hashes + tags, not raw nesting vs raw flat. See #64.