# Mana Vaada: public screen exploration

This round turns the Street Index identity into a connected public journey. Open [`round-two.html`](round-two.html) for the coded screens. All editorial and business names, claims, source records and dates in the prototype are fixtures for design review. They are not publication data.

## Product navigation

Home, Explore, Updates and Stories are the four persistent destinations. Search and town selection are global utilities. Place, guide, comparison, update detail and story detail are reached from contextual cards and use a back link to the parent destination. A person never has to sign in or share device location to read public content.

| Screen | Job | First useful thing | Primary next action |
| --- | --- | --- | --- |
| Home | Orient a resident to their town | Practical update with source and date | Open update or guide |
| Explore | Find a place or activity | Search and category choices | Open category or place |
| Search | Match name/category within town | Typed query and grouped results | Open result |
| Category | Scan a selected category | Relevant place list and guide | Open place or comparison |
| Place | Decide whether to visit/contact | Why go, best for, facts, checked date | Call or directions when validated |
| Guide | Follow an editor's selection | Reasons for every included place | Open place or directions |
| Compare | Choose by situation | Side-by-side factual attributes | Open a place |
| Updates | Scan short practical briefs | Latest sourced update | Open update |
| Update detail | Act on a practical change | Summary, date, correction and source | Open source or related guide |
| Stories | Discover deeper local reporting | Lead human story | Open story |
| Story detail | Read an original feature | Headline, byline, image and body | Share or follow related content |
| Town picker | Select local context | Six launch-cohort towns | See selected town's available coverage |
| Suggest correction | Report a questionable place fact | Page context and clear report fields | Preview a submission without transmitting data |
| How we check | Explain editorial trust signals | Source, check date and correction rules | Inspect an example correction |

## Composition rules

**Home** is an editorial feed, not a grid of equal cards. A dominant practical update starts it; a horizontal category row, one image-led guide, an open-text story and a nearby place follow. Each item carries a distinct content type and clear route forward. The first screen includes town context and a useful action.

**Explore** is search-led. Category navigation is visible without scrolling on most phones; the place list starts immediately below a single featured guide. A text result is valid without imagery. The category page retains the same search context and gives a comparison link only where editor-authored facts exist.

**Updates** favors chronology and provenance. It uses compact rows and a single lead brief. Material corrections are inline and name what changed. A story does not masquerade as a short update.

**Stories** uses a calmer reading rhythm and a larger image. It stays inside the same navy/mist/coral identity. The index has one lead feature and a smaller list; the article gives the text room and shows original reporting/source notes.

## Variants for the next critique

The coded version favors quick local decisions. These are credible alternatives to test with residents and editors before production components are fixed:

| Area | Coded direction | Alternative worth testing | Trade-off to watch |
| --- | --- | --- | --- |
| Home | Practical update leads, followed by guide and story | Story-led edition with a compact update rail | More character, slower access to time-sensitive facts |
| Explore | Search and category chips above a text-first place list | Situation-led entry points such as “quick breakfast” or “with family” | More helpful prompts, more editorial upkeep |
| Explore map | Complete list with optional map in a guide | Coordinated map and list on wide screens | Needs verified coordinates, attribution and keyboard parity |
| Updates | Chronological briefs and explicit correction | Dense local bulletin with date groups | Faster scanning, less room for source context |
| Stories | Image-led feature with a quiet reading column | Text-led feature for reporting without a strong licensed image | Works with sparse imagery, less immediate visual draw |

The next design decision should be driven by a small task test: find a place for breakfast, understand a market change, and decide whether to read a feature. Record time to answer and which trust details people notice.

## Responsive behavior

- At 320 px: single-column content, 16 px gutters, 44 px minimum controls, wrapping Telugu titles, horizontal scroll for category chips only.
- At 390 px: same content order with wider images and less line wrapping.
- At 768 px: selective two-column cards and a wider reading measure.
- At 1024 px and above: a centered 12-column shell; Home and Stories can lead with asymmetric media, while Updates remains a readable column with a supporting rail.
- The viewer can switch among 320 px, 390 px and desktop frames. These are review views; the product CSS itself is responsive at intermediate widths.

## Content and trust behavior

- Editorial copy answers what happened, where it applies and why it matters. A brief links to its source record; a material correction displays the changed fact and date.
- Places show last-checked information. Unknown hours are written as unknown. Contact and route controls appear only after validation in production. Prototype controls announce that they are examples.
- The place fixture has no confirmed phone number or coordinates, so its profile offers the related guide instead of a nonworking call or route action. The comparison and place list link to distinct example profiles.
- A guide keeps its complete text list when map tiles fail, are disabled or have not loaded. The map is optional to the task.
- Verified, Sponsored and Merchant-managed remain separate states. The prototype places no fake verification badge on sample businesses.
- Empty search and unavailable town coverage explain what the visitor can do next. The viewer also offers a map-failure toggle to inspect resilience.
- Candidate records and merchant editing have distinct information architectures and are intentionally not mixed into these public discovery screens. Their requirements remain in the PRD for a later dedicated round.

## Visual asset rules

The street, breakfast and handloom images are generated concept imagery. They establish crop, color and subject direction only. They cannot identify a real business or person, and they need replacement by licensed, attributed imagery before publication. Place and update content must still work when there is no image.

## Review questions resolved by defaults

- **Default town:** Kadapa, because it has the most sample scenarios in the current brief and pilot.
- **Default language:** English, with a complete Telugu toggle for the coded screens.
- **Theme:** Light for this round. The earlier pilot tested a dark presentation canvas; product dark mode remains a separate launch decision.
- **Map:** Off the critical path. The guide starts with its list, with a map preview available as an enhancement.