# Translation Scout Wireframe Notes

Files:
- [translation-scout-wireframe.svg](/Users/sonfamily/Documents/SONALI/PALLAS-ANALYTICS/Website/assets/translation-scout-wireframe.svg)

## Intent

This wireframe shows the minimum credible demo surface for **Translation Scout**.

The goal is not to simulate a rights marketplace.
It is to show a disciplined editorial workspace that helps a scout or editor move from noisy foreign-market coverage to a shortlist of titles worth deeper attention.

## Core product promise

1. Ingest foreign title and coverage data
2. Bring in critic and market signals
3. Map overlap with trusted English-language taste
4. Rank titles by likely travel potential
5. Turn that signal into an editorial next step

## Layout logic

### 1. Left rail

The left rail should act as the scout's control surface.

It holds:

- active scouting lists
- markets or territories
- shortlist status
- saved editorial views

This keeps the page grounded in a real scouting workflow instead of a generic browse experience.

### 2. Main results table

The center workspace is the heart of the page.

It should show a ranked title list with columns such as:

- title
- author
- territory
- travel score
- critic overlap
- coverage strength
- recommendation status

This is where the product proves it is more than discovery. It is prioritization.

### 3. Right insight panel

The right panel should answer the editorial question:

"Why is this book worth my time?"

It should show:

- title summary
- overlap with trusted critics
- comparable English-language titles
- recent momentum signals
- recommendation and next step

### 4. Signal ribbon

A compact ribbon near the top can summarize:

- number of titles screened
- titles escalated
- strong overlap matches
- coverage spike alerts

This gives the page a fast read before the user engages with the detail.

## Labeling choices

Use editorial language, not marketplace language.

Prefer:

- `Travel fit`
- `Critic overlap`
- `Coverage strength`
- `Editorial recommendation`
- `Escalate for read`

Avoid:

- `Demand score`
- `Deal score`
- `Lead value`

## Visual principles

- quiet neutral palette
- one blue accent for selection and ranking state
- thin dividers and light grouping
- no dashboard theatrics
- hierarchy through spacing, alignment, and restraint

The system should feel like a serious editorial tool.

## What to prototype next

1. Switching between market lists
2. Selecting a title and updating the insight panel
3. Expanding critic overlap detail
4. Comparing two titles side by side
5. Saving a title to an editor shortlist