Product User Guide

What you can do

• Use Dashboard as the signed-in default continuation and recovery surface after public framing and auth entry.
• Review global status (channels, hits, library, quota) in one screen.
• Read a `Today Briefing` that points to the next best line to recover or continue.
• Use Dashboard as the recovery surface for your first strategy loop and as the daily operations entry after it starts running.

How to use

1. 1Open `/{locale}/dashboard` after sign-in.
2. 2Read `Today Briefing`, cards, and activity feed to decide which line deserves attention first.
3. 3Use `How to use` to jump to `/{locale}/help#dashboard` when you need the canonical recovery guide.
4. 4If the first strategy loop is still in progress, use Dashboard to recover it, then continue the next step in the guided flow, Channels, Rules, or export.

Notes

• Dashboard is a recovery and default continuation surface, but it stays read-first and does not complete guided steps by itself.
• Public discovery should frame the next move before sign-in; once users cross auth entry, Dashboard becomes the default recovery surface unless a more specific intent is preserved.
• `Today Briefing` helps you choose the next action, but it is not the execution surface.
• Generic public sign-in or sign-up without an explicit destination returns to dashboard first.
• Empty workspaces send you back toward Channels and guided-flow recovery instead of pretending Dashboard is already the execution surface.
• Admin/Ops viewers see a privileged notice instead of `Today Briefing`; access-overlay users without Ops access stay on the creator dashboard.

What you can do

• Build a long-term watchlist of external channels and keep following their latest video changes.
• Use overview, all videos, and insights together as one change-judgment workflow.
• Send promising signals into Rules, exports, and downstream accumulation work.

How to use

1. 1Open `/{locale}/channels` and add a channel worth following over time to your watchlist.
2. 2Use group, channel, and hits-window filters to judge which changes deserve a follow-up.
3. 3Use `How to use` to open `/{locale}/help#channels` and review the full watchlist workflow.

Notes

• Channels is a watchlist and change-judgment surface, not just a generic channel manager.
• The “High watch-rate new videos” card and related latest-video sort use a heuristic proxy: videos published in the last 24 hours with `views / subscriberCount * 100`, not a true 24h view-delta field.
• Channels CSV exports now keep the watch-rate column wording aligned with the active locale instead of falling back to hardcoded English headers.
• Rule-hit data is tied to rules configuration and selected hours window.
• Write actions still follow write-protection policy.

What you can do

• Run your validation-and-feedback loop with owned channels.
• Review publish outcomes, comment signals, and channel performance in one place.
• Feed feedback line signals back into your next tracking and idea decisions.

How to use

1. 1Open `/{locale}/my-channels` and add owned channels to start the feedback line.
2. 2Review outcomes in channel/video views and keep groups tidy for follow-up.
3. 3Use `How to use` to jump to `/{locale}/help#my-channels`.

Notes

• Read-only mode allows browsing but blocks writes.
• Empty overview usually means the feedback line has not started yet.

What you can do

• Turn recurring signals into an idea line and reusable content intelligence.
• Organize clues with groups/themes/status for ongoing judgment.
• Move signals through Kanban and export filtered sets for downstream creation.

How to use

1. 1Add clues from Channels or Add clue manually in `/{locale}/library`.
2. 2Use list filters, themes, and Kanban stages to progress idea-line decisions.
3. 3Open `/{locale}/help#ideas` for full idea-line guidance.

Notes

• Free tier can hit idea-count limits.
• The current Library truth uses status `active / planning / done / archived / deleted`, adaptation `pending / adapted`, and a two-column Kanban where blank `adapt_status` is treated as `pending`.
• Filtered list/export results now rely on the same truthful status/adaptation query semantics before row limiting, so large libraries do not silently lose matches just because they fall outside the first fetched batch.
• Rule hits and ideas serve different workflows (auto triage vs manual content-intelligence curation).

What you can do

• Turn tracked signals from Channels and Ideas into ongoing judgment rules.
• Review recent hits to decide what deserves follow-up next.
• Configure where confirmed reminders should be delivered and audit recent outcomes.

How to use

1. 1Open `/{locale}/rules` and define which signals should stay under follow-up.
2. 2Use `Hits` to review which monitored changes or saved ideas now deserve action.
3. 3Use `Notifications` and `History` to confirm reminders are reaching the right place.

Notes

• Rules is the judgment-and-reminders layer for signals that begin in Channels or Ideas.
• Email recipient follows account primary address for audit consistency.
• Desktop push availability depends on browser permission and VAPID setup.
• Creating the first rule is the fifth activation milestone in the final journey contract.

What you can do

• Analyze title patterns and generate rewrite candidates.
• Browse historical rewrites and export selected results.
• Reuse favorite rewrites for iteration.

How to use

1. 1Open `/{locale}/titles` and choose rewrite/history/gallery tab.
2. 2Submit source title/context and inspect generated suggestions.
3. 3Open `/{locale}/help#titles` for module quick guide.

Notes

• Generation quota and usage limits apply.
• Some history fields may follow legacy-compatible naming for parity.

What you can do

• Generate or refine thumbnail prompt ideas.
• Browse history and reusable prompt patterns.
• Export prompts for downstream creative workflows.

How to use

1. 1Open `/{locale}/thumbnails`.
2. 2Generate prompts and refine with filters/favorites.
3. 3Use `How to use` to jump to `/{locale}/help#thumbnails`.

Notes

• Prompt generation depends on available capacity and quota.
• Sync-related states can be asynchronous.

What you can do

• Use the signed-in compatibility hub for the AI enhancement layer.
• Jump into the three currently narrated AI-layer surfaces: Exports, Articles, and Comments.
• Keep discovery in one place without turning AI Tools into a new primary nav owner.

How to use

1. 1Open `/{locale}/ai-tools`.
2. 2Choose the card that matches the stage you need next: Exports for the compound bridge, Articles for create-stage drafting, or Comments for deconstruct-stage analysis.
3. 3Use `How to use` to jump to `/{locale}/help#ai-tools`.

Notes

• The hub is compatibility-first; detailed execution still happens in the owning surface.
• Export Center stays the compound bridge and system dispatch page; AI Tools does not take over export execution.
• Comments Analysis and Export Center keep their current sidebar/nav ownership; AI Tools remains entry-first.

What you can do

• Use AI-assisted drafting to turn signals and insight work into create-stage drafts.
• Track task status, edit resulting drafts, and prepare follow-up publishing/export steps.
• Keep article generation inside the same strategy loop instead of treating it as a standalone lab.

How to use

1. 1Open `/{locale}/ai-tools/articles`.
2. 2Submit generation task with topic and constraints.
3. 3Open `/{locale}/help#ai-tools-articles` for usage baseline.

Notes

• Articles is the AI enhancement layer's create surface.
• Draft quality depends on source material quality.
• Long-running tasks can finish asynchronously.

What you can do

• Use AI-assisted deconstruct work to break comment signals into usable judgment.
• Fetch video comments and review sentiment/topic summaries for the selected context.
• Export the resulting comment analysis for reporting or follow-up workflows.

How to use

1. 1Open `/{locale}/ai-tools/comments`.
2. 2Fetch comments by video and run analysis.
3. 3Use `How to use` to jump to `/{locale}/help#ai-tools-comments`.

Notes

• Comments Analysis is the AI enhancement layer's deconstruct surface.
• Comment fetches can be rate-limited by upstream services.
• Historical results may depend on cache retention policy.

What you can do

• Settings & Account is the system-layer control surface for configure, connect, and continue tasks.
• Manage preferences, integrations, export destinations, and account-level continuation tasks in one signed-in surface.
• Review write-related controls and environment readiness without turning Settings into a reminder inbox.
• Open Access & Billing as the signed-in system task surface after comparing plans when you need to continue payment, review current billing status, renewal or expiry timing, voucher status, or subscription actions.

How to use

1. 1Open `/{locale}/settings`.
2. 2Connect integrations, confirm authorization state, and set export destinations before downstream workflows consume them.
3. 3Use Access & Billing when the next step is a signed-in payment or subscription task.
4. 4Open `/{locale}/help#settings` for quick reference.

Notes

• Settings keeps the strategy system configurable, connected, and supportable, but it is not a separate object line or action stage.
• Some settings are read-only in restricted environments.
• Export destination validation should pass before use.
• Pricing stays the public compare surface. Access & Billing is the signed-in system task surface that follows after plan comparison.
• Integrations and export-destination config stay in Settings even when Rules, Ideas, or other workflows consume the downstream results.
• Notification boundary: Settings owns connection, authorization, and destination config. Rules owns reminder delivery and review.
• Access & Billing separates internal access privilege from real paid status. Admin or privileged access does not mean the account is on a paid plan.
• Free billing-state users see plan and interval choices plus the selected plan summary before payment, while paid or voucher users see current status and management actions first.
• When payment is unavailable, Access & Billing must explain whether billing is disabled for the current environment, whether billing actions are still guarded by a launch blocker, whether current Terms/Privacy acknowledgement is required, or whether the Paddle client token is missing instead of showing one generic unavailable message.
• If the current billing read path is temporarily unavailable, Access & Billing keeps the page shell visible and explains that current billing status cannot be loaded right now instead of dropping into an error page or pretending the account is free.

What you can do

• Use Pricing as the public compare surface that frames the commitment decision before users cross auth entry.
• Compare plan limits and capability differences before you sign in to act.
• Start upgrade flow and review billing impact.
• Check quota rationale for current usage.
• Sign in when you are ready to continue in Access & Billing.
• Review monthly/yearly plans and current intro-offer eligibility for Pro monthly.

How to use

1. 1Open `/{locale}/pricing`.
2. 2Compare Free/Pro/Team details.
3. 3Use `How to use` to jump to `/{locale}/help#pricing`.

Notes

• Pricing is the public compare surface. It should help users decide whether to pay before they leave the public shell.
• The handoff chain is `compare on Pricing -> preserve intent through sign-in -> continue in Access & Billing`.
• Displayed plan details should stay aligned with the account's real billing state; privileged internal access must not be treated as a paid plan.
• Generic public sign-in from public pages returns to `/{locale}/dashboard` unless a more specific destination is requested.
• After users compare plans, they should sign in and continue in Access & Billing for payment actions, plan changes, or subscription details; that page reuses pricing plan summaries so the currently selected plan remains understandable inside checkout.
• Checkout, portal access, and voucher redemption are part of the same billing action surface and should stay usable even when the rest of the product remains in global read-only mode.
• Team remains a public plan name for higher limits and priority support; it does not represent internal admin access.

What you can do

• Help & Legal is the system-layer reference and policy surface for reference, policy, and support handoff tasks.
• Explain the entry-and-handoff journey without becoming the destination owner for the next step.
• Access module TOC and anchor-based guidance without turning Help into a runtime dashboard.
• Use legal pages for privacy, terms, and compliance references.
• Share stable help anchors with onboarding, support, and QA.

How to use

1. 1Open `/{locale}/help` and use TOC to navigate anchors.
2. 2Verify each module link resolves to matching section.
3. 3Use `/{locale}/help#help-legal` for legal/help overview.

Notes

• TOC and anchor sections are maintained 1:1.
• Help & Legal stays the stable reference and policy surface for the system layer.
• Help explains how public shell, auth entry, dashboard, onboarding, and billing relate; it should not impersonate any of those execution surfaces.
• This page is a product usage reference, not a runtime status dashboard.
• Public help copy should focus on user goals such as comparing plans, signing in to continue, and getting help.
• Support handoff should happen through stable anchors, policy references, and clear next-step guidance instead of status-style operational copy.