marvin

To automate a daily briefing at session start, the system reads state and session files to load current priorities, open threads, and progress metrics into a coherent summary. It evaluates goals and follow-up data to surface proactive alerts for immediate user action.

Context loading during session resumption works by reading today's session file first, then falling back to yesterday's file for continuity. It aggregates state, goals, and log data to reconstruct open threads and progress metrics into a single daily briefing.

Yes, you can track open threads and follow-up alerts using markdown state files. The system reads current state, goals, and log markdown files to surface proactive alerts, assess progress, and deliver upcoming follow-ups directly within the daily briefing.

The best way to review progress metrics and goals for a daily briefing is to read from dedicated state and log markdown files. The system evaluates goals against progress logs to produce a coherent summary with top priorities, next steps, and proactive alerts.

Yes, you need specific markdown files including state/current.md, sessions/{TODAY}.md, state/goals.md, and content/log.md to initialize the session. These files provide the priorities, goals, and progress metrics required to generate the daily briefing.

Your daily briefing may not show open threads and proactive alerts if the required state, goals, or log markdown files are missing or empty. The system relies on reading these specific files to extract follow-up data and assess progress before surfacing alerts.