01 · Positioning
How the product takes on the work
GroupBrief brings chat distillation, rankings, visual candidates, and archives into a reviewable local workspace.
Content is reviewed before send preparation, with a traceable path from source records to the final brief.
02 · Context
The problem and the people
Why it needs to exist
Conclusions, people, and follow-ups in busy group chats disappear under later messages, while editing and visual preparation repeat every cycle.
Who it is for
Community operators who regularly summarize conversations, prepare visuals, and preserve searchable archives.
03 · Core flow
Core workflow
Four key views trace the complete path from entering the product to handling the work and confirming the outcome.
- 01
Operations overview
Keep groups, briefs, pending work, and system state in one view.
- 02
Task center
Move source records through distillation, review, and send preparation.
- 03
AI image workspace
Compare visual candidates and choose explicitly instead of treating generation as approval.
- 04
Rankings and archive
Review active groups and return to completed briefs and their source records.
04 · Product views
Four views of how the product works
All four views stay visible in a masonry gallery. Open any card for a larger view and continue with the arrow keys.
Operations overview
Keep groups, briefs, pending work, and system state in one view.
Task center
Move source records through distillation, review, and send preparation.
AI image workspace
Compare visual candidates and choose explicitly instead of treating generation as approval.
Rankings and archive
Review active groups and return to completed briefs and their source records.
05 · Decisions
Three product decisions
- 01
Summaries return to sources
People, conclusions, and follow-ups retain source links so their context can be checked before publishing.
- 02
Visuals are selected before use
AI visuals enter a candidate workspace and require human selection before joining a brief.
- 03
Unknown delivery stops the flow
Page changes and timeouts are not delivery evidence; uncertain state prevents automatic resend.
06 · Current state
What is complete—and what is not
The main capabilities are implemented; current runtime status needs review and every real send remains human-approved.
What the product changes
Content is reviewed before send preparation, with a traceable path from source records to the final brief.
Source and implementation
Source links are listed above; public screens still use synthetic or redacted data only.
Portfolio boundary
This site shows redacted interfaces and product logic only. It never connects to source databases or performs real publishing, applications, sending, or payments.
Next