Prepared presenterNormal viewing
01
Approved before it reaches the audience.
The script and pre-made video can be reviewed before publication. Stories belong to a scheduled edition and retain their frozen version history.
Partner guide · Product foundation
The product foundationis built.The production servicecomes next.
TickerCue is built around approved prepared news videos for normal viewing, with a separate optional live analyst for subscribers that a customer deliberately starts.
Local foundationWorking + testedProduction service not launched
TickerCue / Core product modelLocal
01
Default experience
Prepared
presenter
- Pre-made news video
- Reviewable before publication
- Fixed, predictable playback
TopicPrivacyHandoff→
02
Optional feature
Live
analyst
- Separate AI personality
- Deliberately started
- Entitled + cost controlled
Watch first.
Ask only when you choose.
01 / The product
Two personalities.
One unmistakable boundary.
The prepared presenter carries the everyday editorial experience. The live analyst only appears after an intentional, visible handoff.
Live analystOptional follow-up
02
Live only after an explicit decision.
The separate analyst answers follow-up questions using an approved context snapshot, with finance-safety boundaries and live-session controls.
Before live
TopicPrivacyHandoff clipEntitlement
Then, and only then: live analyst
02 / Customer flow
A deliberate path from story to conversation.
Each stage tells the customer what mode they are in, what happens next, and when a paid live feature begins.
- 01
Normal viewing
Watch the prepared story
A reviewed script and pre-made presenter video deliver the normal news experience without starting a live session. - 02
Deliberate choice
Choose topic + privacy
Before anything live begins, the customer sees the topic and privacy screen and makes an explicit choice. - 03
Clear transition
See the handoff
A short prepared clip introduces the separate live analyst. The change of mode is visible, not implied. - 04
Optional live feature
Start the live analyst
An entitled customer deliberately starts a source-bounded follow-up session with active cost controls. - 05
Customer control
End, save, or clear
The interface supports clear history, sign out, and account deletion without blurring local foundations with complete provider deletion.
03 / Trust foundations
Built to know its boundaries.
Privacy, editorial history, finance safety, and cost control are product architecture—not footnotes added after the experience.
01
Account isolation
Row-level security foundations keep private records scoped to the correct account.
RLS · private records02
Encrypted history
Conversation-saving has an encrypted foundation, with clear-history and account controls already represented in the product.
Foundation built · recovery next03
Versioned truth
Stories, sources, editions, personas, contexts, forecasts, and renders retain versioned database records.
Corrections replace · never silently rewrite04
Bounded media
Prepared video supports fixed playback, handoff playback, and temporary signed media links.
Prepared · expiring access05
Finance safety
Topic rules and disclosures establish the local safety boundary for finance conversations.
Rules · disclosures · source context06
Cost-aware live
Entitlements and live-session controls help prevent passive paid sessions and unbounded live cost.
Deliberate start · active session controls07
Fail closed
Missing required information or configuration makes a feature unavailable instead of inventing a fallback.
Unavailable beats unsafe08
No pretend data
Fake production-facing quote values have been removed from the local product foundation.
Licensed market data remains next phase04 / Definition of done
A working foundation is not a live business service.
This is the boundary every partner presentation should preserve.
Done in the local code
Core product behavior, safeguards, and foundations are implemented and validated.
Product experience
- The core prepared-video and optional-live-analyst product flow.
- The pre-live topic and privacy screen.
- Separation between prepared presenter and live analyst.
- Fixed-video and handoff playback support.
- Prevention of passive paid live sessions.
Identity + privacy
- Account isolation.
- Encrypted conversation-saving foundation.
- Clear-history, sign-out, and account-delete interfaces.
Editorial + safety
- Finance-safety topic rules and disclosures.
- Versioned stories, sources, editions, personalities, contexts, forecasts, and renders in the database foundation.
- Removal of fake production-facing quote values.
Control + validation
- Live-session cost controls.
- Unit, build, database, and backend validation described above.
Not done as a live business service
External operations, production governance, and public launch work remain ahead.
Launch + distribution
- Production-service launch and distribution.
- App Store approval.
Content + data
- Production content and video library.
- Licensed market data.
- Public predictions and audited performance reporting.
Commercial + legal
- Subscription payments.
- Final legal clearance.
Operations + privacy
- Complete live moderation.
- Complete external-provider deletion.
- Complete cloud-history recovery.
05 / Founder decisions
Three questions to close before production.
These decisions remain open. The local foundation supports the direction, but it does not substitute for an operating policy or provider contract.
13
Open decision
Will cloud conversation history be restored across devices?
Not yet. The encrypted conversation-saving foundation is built locally; complete cloud-history recovery remains a next-phase service capability.
Next actionDefine recovery architecture, retention rules, and customer controls.
14
Open decision
What market-data provider and licence will be used?
Not selected in this foundation. Licensed market data is explicitly part of the next phase, and no fake production quote values remain in the product-facing flow.
Next actionSelect a provider and secure the correct production licence before launch.
15
Open decision
What human support and correction process will customers receive?
The final customer-support process is not yet defined. The editorial foundation already preserves story versions so a correction can create a replacement instead of silently changing history.
Next actionSet support ownership, response standards, escalation, and correction notice policy.
06 / Shared language
The TickerCue glossary.
Plain-language definitions for the product, editorial, privacy, and commercial foundations.
01Prepared presenter
The AI-generated personality in a pre-made news video. The script and video can be reviewed before publication.
02Live analyst
The separate AI personality that answers follow-up questions after the user deliberately starts a live session.
03Handoff clip
A short prepared video in which the presenter introduces the live analyst.
04Story version
A frozen edition of a story’s words and facts. Corrections create a replacement rather than silently changing history.
05Edition
A scheduled group of stories, similar to a television news bulletin.
06Context snapshot
The approved facts, sources, timing, personalities, and safety boundaries supplied to the live analyst for one story.
07Persona version
A historical version of a presenter’s or analyst’s style, biography, disclosure, instructions, avatar, and voice setup.
08Entitlement
The server’s record that a user is allowed to start a paid live feature, for example because they are a subscriber or approved beta tester.
09Signed media link
A temporary download link for a prepared video. It expires and cannot be used forever.
10RLS (row-level security)
Database rules that prevent one user from reading another user’s private records.
11Fail closed
If required information or configuration is missing, the feature becomes unavailable rather than guessing or using unsafe fallback data.
12StoreKit
Apple’s system for App Store subscriptions and in-app purchases.
13DPA (data processing agreement)
A contract explaining how an external provider may process, retain, protect, and delete customer data.
07 / The status to carry forward
The product foundation is built.The production service and its external operating controls are the next phase.
TickerCue now has a coherent architecture for prepared viewing, optional live analysis, explicit privacy choices, account-specific encrypted history, versioned editorial records, and meaningful cost and safety protections.
Return to the main site