Skip to content
Spectral Codex
GitHub
Operations

Feedback Evolution

Generated

This page is generated from qa/operations/specs/feedback-evolution.md — the source of truth. Edit the spec, not this page.

Last run: not yet recorded (run the replay suite to populate status).

Overview

The Feedback & evolution surface is the fifth workspace tab inside a ruleset. It shows customer-flagged decisions aggregated into patterns — each pattern carries the loop signal → traced-to rule → fix (often a proposed rule already in the review queue), the flagged examples, and a suggested move. It is the cockpit end of the dashboard’s “Request a review”.

Flagged-decision patterns are produced asynchronously by the platform’s feedback-aggregation loop (customer feedback → (world, pattern) cluster → worlds evolution), not by any operator UI action. A freshly-created ruleset has no flags, so this spec drives the deterministically reachable state: the tab is reachable, the surface renders its heading + intro, and an un-flagged ruleset lands on the honest empty state. The spec also pins the “speak human” vocabulary (no internal “enshrine” / “world model” / “candidate” copy).

Preconditions

  • Signed in as the seeded operator (see OPS-AUTH-GATING scenario 2).
  • A ruleset exists (created via OPS-WORLDS-CRUD or seeded).

Scenarios

1. Reach the Feedback surface from the workspace tabs

  • Create (or open) a ruleset and open its workspace
  • Follow the “Feedback” workspace tab
  • Expected: The URL is the ruleset’s /feedback surface; the page heading reads “Feedback & evolution”; the Feedback tab is marked current.

2. An un-flagged ruleset shows the honest empty state

  • On a freshly-created ruleset’s Feedback surface
  • Expected: The empty state renders (“No flags right now” with the explanation that patterns appear once customers flag decisions); no pattern grid is shown.

3. The surface speaks human

  • On the Feedback surface
  • Expected: The visible copy uses the human vocabulary (“ruleset”, “review queue”, “proposed rule”) and never the internal terms “enshrine”, “world model”, “provenance tier”, “conformity”, or “distillation”.

4. The Feedback tab keeps the ruleset context

  • From the Feedback surface, move to another workspace tab and back
  • Expected: Each navigation stays within the same ruleset (the /worlds/{id}/... segment is preserved); the Feedback surface re-renders.

Test Data

LabelValueNotes
Existing ruleset(any active ruleset id)Reuse a created/seeded ruleset; a fresh one has no flags