Create an assistant briefing from email, calendar, and messages

# Brief like an assistant by combining mail, calendar, and messengers

## What to make
- Collect data from multiple sources such as mail, calendar, KakaoTalk, Instagram, meeting minutes, notes, and Slack
- Show the last sync time per source
- Immediately notify of collection failures or expired permissions
- Merge duplicate events (calendar invites, mail, messages) into one
- Automatic meeting minutes processing: distinguish decisions from discussion
- Track action items as completed/incomplete, show incomplete items first at the next meeting
- When there are no meeting minutes, infer from other sources while stating the inference process and suggesting that the minutes be supplemented
- Preserve original meeting minutes
- Notifications are not simple alerts but come with an action plan and previous context
- Pre-meeting briefing: counterpart profile (title, affiliation, relationship history), last contact (when, what, tone), decisions from the previous meeting, incomplete action items, counterpart's unanswered items, what I haven't received, 2-3 things that must be confirmed in this meeting
- The action plan is a judgment that combines plans, market conditions, and relationships, presented together with the basis for the judgment
- Visually separate predictions from facts
- Prevent notification overload: classify by importance, low-importance ones in a once-daily digest
- Q&A: investigate and synthesize all relevant context
- State the criteria for judging context relevance (same person, same project, same period, causal link, explicit reference)
- No including unrelated context through simple keyword matching
- Show the referenced sources and intentional exclusions in each answer
- If there is no basis, state 'not in the records'; do not fill it in with plausible guesses
- For partial information, answer by separating what is known from what is unknown
- Suggest related nodes so the scope can be narrowed with follow-up questions

## Fixed: what does not change
- Notification form → send a notification via KakaoTalk 10 minutes before an event

## Evaluation criteria
- Data collection & sources: Combine mail, calendar, KakaoTalk, Instagram, meeting minutes, notes, Slack, etc. into one, and tell me my schedule and remind me like an assistant
- Always show the last sync time per source. Do not make judgments on stale data
- Do not pass over collection failures or expired permissions quietly; tell me immediately
- Merge duplicate events (calendar invite + mail confirmation + KakaoTalk mention) into a single event
- Distinguish decisions from discussion in the automatic meeting minutes processing. "It came up" and "it was decided" are completely different
- Track action items as completed/incomplete, and show incomplete items first at the next meeting
- For meetings with no minutes, infer from the calendar, mail, and messages, but state that it is an inference and suggest that the user supplement the minutes
- Always preserve the original meeting minutes separately from the summary
- Notifications & briefing: give an action plan + previous context together, not simple alerts
- Pre-meeting briefing composition: the counterpart's profile (title, affiliation, relationship history); last contact: when, what, in what tone; decisions and incomplete action items from the immediately preceding meeting; things the counterpart requested that I haven't answered yet / things I requested that I haven't received; 2–3 things that must be confirmed in this meeting
- Write the action plan not at the level of "it will probably be like this" but as a judgment that combines plans, market conditions, and relationships. However, present the basis for the judgment together so that I can verify it
- Visually separate predictions or guesses from facts
- Preventing notification overload: set importance criteria, and bundle low-importance ones into a once-daily digest
- Q&A
- When asked something, investigate all relevant context and answer with a synthesis
- The richer the context, the better, but never include irrelevant context
- Set explicit relevance criteria: same person / same project / same period / causal link / explicit reference. Do not pull something in simply because keywords overlap
- With each answer, briefly show which sources were referenced and what was intentionally excluded
- If there is no basis even after searching, say "not in the records". Filling it in plausibly is the worst
- When only partially known, answer by separating the known part from the unknown part
- Suggest related nodes together so the scope can be narrowed with follow-up questions

## Original text written by the client
> You need to make it work like an assistant by combining mail, calendar, KakaoTalk records, Instagram records, etc. Using an LLM wiki, combine the conversation content up to now and produce a report on the future action plan. Like gbrain. Combine the schedules and send notifications 10 minutes before through KakaoTalk's chat with myself. Here, "schedules" means all my context and records combined.