Verified — Amma Koduku Dengudu Kathalu

| Goal | Why it matters | Success Metric | |------|----------------|----------------| | Provide a trusted library of traditional & contemporary mother‑child stories | Parents often worry about the authenticity, language, and moral values of online stories. | ≥ 90 % of users rate story trustworthiness ≥ 4‑star (5‑point scale) after 3 months. | | Increase user engagement & retention | A “verified” badge creates a sense of safety, encouraging longer reading sessions and repeat visits. | + 25 % monthly active users (MAU) on the verified collection within 6 months. | | Create a community‑driven moderation pipeline | Leverages existing parent‑author community to scale verification. | 80 % of verification decisions made by community moderators within 48 h of submission. | | Monetise via premium tier & sponsorships | High‑value curated content can be part of a subscription or brand‑sponsored series. | $ X M incremental revenue by end‑of‑year (target set by finance). |

| # | Requirement | Priority | Acceptance Criteria | |---|-------------|----------|----------------------| | FR‑01 | Verified Tab in the main story browsing UI. | Must | Visible on the homepage; loads only stories flagged as Verified. | | FR‑02 | Verification Badge (gold star + “Verified” label) on story cards and detail pages. | Must | Badge appears for all stories with status = verified. | | FR‑03 | Submission Flow for authors (web & mobile). | Must | Form accepts title, story text, illustrations, language, age‑group, cultural notes; creates a “Pending Verification” record. | | FR‑04 | Moderator Dashboard – list of pending stories, filter by language/region, bulk actions. | Must | Moderator can approve/reject with optional comment; status updates instantly. | | FR‑05 | Verification Criteria Engine – checklist: language quality, age‑appropriateness, cultural authenticity, moral tone, copyright compliance. | Should | System auto‑highlights missing checklist items; cannot approve until all mandatory items are checked. | | FR‑06 | Community Reporting – “Report Issue” button on verified stories. | Must | Report triggers admin review; reporter receives acknowledgement. | | FR‑07 | Versioning – keep previous versions of stories when edited after verification. | Should | Users see “Updated X days ago” note; older versions archived for audit. | | FR‑08 | Analytics Dashboard – reads, avg. session length, rating, drop‑off points per verified story. | Should | Data refreshed every 24 h; exportable CSV. | | FR‑09 | Premium Access Controls – optional gating of verified stories behind subscription tier. | Could | Toggle per story/collection; fallback to free “core” verified set. | | FR‑10 | Localization – support Telugu, Tamil, Kannada, Malayalam, Hindi, English UI. | Must | All UI strings, badge text, verification messages displayed in selected language. | amma koduku dengudu kathalu verified

| Persona | Key Pain Points | How the Feature Helps | |---------|----------------|-----------------------| | Maya – Mom, 30 y, first‑time parent | Unsure which stories are age‑appropriate; worries about cultural dilution. | “Verified” badge instantly signals safe, culturally accurate stories. | | Ravi – Grandparent, 62 y | Wants to share classic folk tales but doesn’t know if they’re still relevant. | Curated collection includes “classic‑verified” tags and modern retellings. | | Ananya – Children’s author | Wants a channel to get her stories vetted and showcased. | Submit to verification; get exposure on the front‑page “Verified” carousel. | | Sanjay – Product Manager (internal) | Needs reliable data on content quality and user sentiment. | Dashboard showing verification status, user ratings, and engagement per story. | | Goal | Why it matters | Success

Title: “Amma Koduku Dengudu Kathalu Verified”
Tagline: A curated, verified collection of mother‑to‑child stories (kathalu) that families can trust for quality, cultural relevance, and age‑appropriateness. | # | Requirement | Priority | Acceptance

| KPI | Target (6 months) | Measurement Tool | |-----|-------------------|------------------| | Verified Story Reach | ≥ 150 k unique reads | Analytics dashboard | | User Trust Rating | Avg. ≥ 4.5/5 on “trust” question (post‑read survey) | In‑app survey | | Verification Turn‑around | ≤ 48 h median for pending stories

| Entity | Key Fields | Relationships | |--------|------------|----------------| | Story | story_id, title, content, language, age_group, author_id, status (draft/pending/verified/rejected), badge_flag (bool), created_at, updated_at | belongs‑to Author; has‑many VerificationLog | | Author | author_id, name, email, profile_pic, is_verified_author (bool) | has‑many Story | | VerificationLog | log_id, story_id, moderator_id, action (approve/reject), comments, timestamp, criteria_passed (JSON) | belongs‑to Story, Moderator | | Moderator | moderator_id, name, email, role (admin/moderator) | has‑many VerificationLog | | Report | report_id, story_id, reporter_id, reason, status (open/closed), created_at | belongs‑to Story, User | | Analytics | story_id, reads, avg_time_sec, rating_avg, date | aggregated view |