Chronologue supports converting memory traces into .ics-compliant calendar events for integration with platforms like Google Calendar and Apple Calendar. This allows agents and users to schedule actions with temporal grounding and persistent reminders.

Each calendar event is derived from a structured memory trace and formatted as a VEVENT block.

​
Core Fields

FieldTypeRequiredDescription
titlestring✓Human-readable label for the event
timestampISO 8601✓Start time (UTC) of the event
duration_minutesint✓Duration in minutes
task_idstring✓Unique identifier of originating memory trace
uidstring✓UID used in .ics file

​
Optional & Contextual Fields

FieldTypeDescription
contentstringDetailed description of the event
tempo_tagstringTempo classification (e.g., @morning, 30min_block)
linked_event_uidstringUse this to sync memory to a previously created event
chat_urlstringLink to source conversation (if applicable)
locationstringPhysical or virtual location of the event
completion_statusstringOptional: completed, missed, or cancelled
trigger_conditionstringUsed for agent-triggered events (e.g. if room is clean)

​
Full Event Example

{
  "title": "Deep Work Block",
  "timestamp": "2025-05-12T09:00:00Z",
  "duration_minutes": 120,
  "task_id": "goal-2025-05-12-deep-work",
  "content": "Focus on writing and model evaluation.",
  "tempo_tag": "@morning 2hr_block",
  "chat_url": "https://chat.openai.com/share/example-link",
  "location": "Desk at home office",
  "linked_event_uid": "evt-20250512-deepwork"
}

​
.ics Mapping Logic

Chronologue uses a conversion utility like generate_ics_string() to produce a VEVENT block. Each field is safely escaped and formatted to comply with the iCalendar spec.

​
Sample Output:

BEGIN:VEVENT  
UID:evt-20250512-deepwork  
DTSTAMP:20250511T180000Z  
DTSTART:20250512T090000Z  
DTEND:20250512T110000Z  
SUMMARY:Deep Work Block  
DESCRIPTION:Focus on writing and model evaluation.\nChat log: https://chat.openai.com/share/example-link  
LOCATION:Desk at home office  
STATUS:CONFIRMED  
END:VEVENT

​
Validation Rules

  • timestamp must be in valid ISO 8601 format and converted to UTC
  • duration_minutes must be ≥ 1
  • title is escaped to prevent comma/semicolon injection
  • uid must be globally unique per event (use task_id + date)
  • description supports newline + chat reference for traceability

​
Integration Notes

Chronologue calendar events can be:

Use this schema as a foundation for task planning, temporal triggers, and multi-agent synchronization in real-world environments.

Calendar events are more than reminders — they are a programmable, editable interface for agents operating across time, context, and memory.