← ClaudeAtlas

business-attr-uxlisted

Tiered confidence-table UX, confidence thresholds, and conflict-resolution protocol for confirming inferred service identity and business attributes. Use from /otel-business-attrs.
radra23/otel-as-code-plugin · ★ 1 · Web & Frontend · score 70
Install: claude install-skill radra23/otel-as-code-plugin
# Business Attribute Inference UX ## Confidence Tiers ### Tier 1 — Auto-write (confidence ≥ 0.9) Write immediately. Show a collapsed "✓ Auto-applied" block so the user can see what was written without being asked to confirm it. Example sources that reach Tier 1: - `service.name` from `package.json#name` → confidence 0.97 - `service.version` from `package.json#version` → confidence 0.97 - `service.name` from `pyproject.toml [project].name` → confidence 0.97 ### Tier 2 — Confirm (0.5–0.9) Show in an approval table. Each row shows: attribute | proposed value | confidence | source. Each row has three actions: **[A]pprove / [E]dit / [R]emove**. User must explicitly approve before any Tier 2 value is written. Example sources that reach Tier 2: - `service.namespace` from directory structure → confidence 0.71 - `service.team` from CODEOWNERS → confidence 0.63 (CODEOWNERS may be stale) - `deployment.environment.name` from CI config → confidence 0.55 ### Tier 3 — Propose (confidence < 0.5) Show as flagged proposals. NEVER write without explicit user action. User must promote to Tier 2 by typing the row number (this acts as immediate approval — no second confirmation needed) or reject by typing 'r <number>'. Example sources that reach Tier 3: - Business transaction name inferred from route analysis → confidence 0.35–0.45 - Domain inferred from git remote URL → confidence 0.40 ### Business Attributes — Always Confirm Any candidate business metric or business attribute is ALWAYS p