Skip to content

docs: Regions & Signals Ribbon — draw-to-label UX spec#32

Merged
ozgesolidkey merged 1 commit into
mainfrom
docs/regions-signals-ribbon
Jul 2, 2026
Merged

docs: Regions & Signals Ribbon — draw-to-label UX spec#32
ozgesolidkey merged 1 commit into
mainfrom
docs/regions-signals-ribbon

Conversation

@ozgesolidkey

Copy link
Copy Markdown
Contributor

Design spec for the "draw an area on the log and label it" ribbon — the UX the user sketched, reviewed from UX-designer + log-analyst seats.

Resolves the review's three problems

  • Naming collision: Region (a labeled window of interest — what you draw / auto-detect) vs Signal (a numeric time-series — unchanged). One strip, both, honest names.
  • Draw-vs-navigate conflict: a bare drag navigates; drawing requires an explicit ✏️ Mark mode.
  • Precision gap: create precisely via viewer line-selection → Mark region; rough-draw on the ribbon then snap to event/gap + numeric fine-tune.

The two power moves (why it's worth building)

  • Compare two regions → reuse the baseline/diff engine (known-good vs bad window).
  • Promote region → rule → reuse the investigation-template engine — the manual→repeatable bridge to the test↔build CI gate.

Reuse, not rebuild: minimap canvas (backdrop), Signals time axis (x-axis), range-annotation model (kind:'region' storage + jump), logan_evidence_pack (auto regions), trend_show/Signals (charting), baseline/diff (compare), investigation-templates (promote). No new chart/persistence/scan engine.

Docs-only. Ties into GRANULARIZATION_DESIGN.md (the Auto row is the visual surface for the evidence pack) and the AI-logging-framework thread (promote-to-rule = teaching the gate from the analysis side).

🤖 Generated with Claude Code

A single horizontal strip under the viewer: draw a span and label it in one
gesture, beside the regions LOGAN auto-finds. Resolves the review's three
issues — the "signal" naming collision (Region = window of interest vs
Signal = numeric series), the draw-vs-navigate conflict (bare drag navigates;
drawing needs explicit Mark mode), and the precision gap (create precisely via
viewer line-selection; rough-draw on the ribbon then snap). Adds the two power
moves that make it an analyst tool: compare two regions (baseline/diff reuse)
and promote a region to a repeatable rule (investigation-template reuse) — the
manual-to-repeatable bridge to the CI gate. Thin surface over existing parts;
no new chart/persistence/scan engine.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ozgesolidkey
ozgesolidkey merged commit 3d00eb7 into main Jul 2, 2026
3 checks passed
@ozgesolidkey
ozgesolidkey deleted the docs/regions-signals-ribbon branch July 2, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant