Reader profile
B2CThe profile controls briefing cadence, language, privacy, and ranking context. Reader controls affect future briefings; admin controls below are operational review tools.
Personal briefing help
Reader flowWhat this app does
The B2C product creates a personal intelligence briefing for one reader. The reader workspace is limited to briefing output, profile controls, source preferences, muted topics, and feedback effects. Admin review, test runs, source registry inspection, and trend analysis live in the separate Admin operations workspace.
How a briefing is built
Collect sources
Eligible public and private-profile sources provide candidate items for the reader.
Rank and personalize
Items are scored against interests, novelty, source preference, fatigue, and feedback history.
Apply credibility
Domain trust and rumor/clickbait patterns downrank or park weak items before review.
Build the briefing
The selected items keep citations, reasons, learning effects, and source metadata together.
Optional editorial edit
A configured LLM editor may improve wording, but it cannot remove or add source links.
Preview and validate links
The preview lists all links and their validation state before send or review approval.
Review and learn
Readers give feedback; admins can include, pin, park, reject, or request rewrites with audit notes.
Core concepts
- Briefing instance
- The generated set of selected items for a profile and configuration version.
- Profile
- The reader's interests, language, tone, cadence, delivery settings, and privacy policy.
- Preferred source
- A source that remains eligible and receives ranking boost during item selection.
- Muted source or topic
- A ranking exclusion that removes candidates from future briefing instances.
- Citation
- The provenance record that explains why an item can be trusted.
- Learning effect
- The change a feedback action will make to future ranking or source mix.
Briefing output and source ranking
LoadingAdmin test lab
Construction and observability
LoadingB2C review queue
No pendingFeedback trends
0 eventsAdmin source registry
0 sourcesBriefing instance
No briefings| Item | Reason | Citation | Learning effect | Feedback | Status |
|---|---|---|---|---|---|
| No briefing instance generated yet. | |||||
B2C admin help
Operations flowWhat admins are responsible for
Admins operate the briefing system without becoming the reader. They inspect profiles that are explicitly admin-visible, generate test briefings, review risky output/configuration changes, inspect the source registry, and monitor feedback trends across experiments.
How an editor works the console
Generate a candidate
Use Test lab to build a reviewable briefing for the selected profile.
Shape items
Include, pin, park, reject, or request a rewrite on each item, with notes recorded in the audit log.
Check construction
Use Construction to inspect source health, link validation, credibility parking, and latest run metrics.
Approve or request changes
Review queue remains the approval gate for test runs and risky configuration changes.
Boundary rule
Reader controls change an individual profile. Admin controls validate system behavior and reviewed sends. The interface keeps them in separate workspaces so an admin can inspect operations without confusing those tools with the reader experience.