FICTIONAL DEMONSTRATION · NOT A CLIENT CASE STUDY

The evidence behind a UI delivery.

This page demonstrates the structure and acceptance logic of a SaveX delivery. “Northstar Cloud” is fictional; no conversion, revenue or customer result is claimed.

01 · DECISION RECORD

A choice that can be challenged and traced.

Observed constraint

Fictional users reach a dense pricing comparison with weak hierarchy and no clear path for smaller teams.

Selected direction

A task-first comparison with one recommended plan, visible limits and progressive disclosure for enterprise detail.

Rejected direction

A minimal two-plan layout reduced visual load but concealed material limits and increased sales dependence.

Acceptance signal

Users can identify the relevant plan, limits and next action without relying on colour or hidden content.

FICTIONAL AUDIT EXAMPLE · NOT A CLIENT FINDING

One finding, with its evidence and acceptance check.

The record below uses invented data to show how a real Audit separates a visible fact from a possible impact. No live product was reviewed for this example.

FieldFictional example
Finding and priorityF-01 · P2 · Pricing period may be hard to compare
Observed factAt 320 CSS pixels in the simulated annual state, each plan card shows the monthly equivalent but not the annual total in the same visible group.
EvidenceDEMO-E-01 · /pricing · 320 CSS px · annual state · first load. Simulated capture record and reproduction steps only; no real screenshot is implied.
InterpretationA buyer comparing plans could miss the billing period or total. This is a hypothesis, not observed user behavior.
ConfidenceMedium · one bounded visual inspection; no participant testing or analytics data.
RecommendationKeep the billing period and payable total together within each plan card.
Acceptance checkAt each viewport agreed for the engagement, every plan shows its billing period, payable total, material limits and next action. A keyboard user can operate the billing control and identify the selected state.

Priority boundary: P2 means meaningful friction is visible but the reviewed task remains possible. It is not a measured loss or revenue estimate.

02 · SPECIFICATION AND CODE

The design becomes a repository change.

  1. TokensSemantic colour, type, spacing, radius, focus and elevation values.
  2. StatesDefault, hover, focus, selected, unavailable, loading and error behaviour.
  3. Responsive rulesDocumented behaviour at narrow, medium and wide viewports.
  4. Draft MRBounded frontend diff, review notes, checks and explicit exclusions.

03 · QUALITY EVIDENCE

Status comes from artifacts, not adjectives.

GateExample evidenceClaim boundary
Visual QAViewport matrix and reviewed screenshotsNo unexplained critical mismatch
AccessibilityKeyboard path, focus review and automated scanNo unsupported compliance claim
PerformanceNamed route, build and measured environmentNo comparison without a baseline
GEO/SEOMetadata, crawl and structured-content review where applicableMarked not applicable for private surfaces

Important: the entries above are demonstration criteria only. A real engagement receives results generated from its own repository and environment.