Robert Helewka
b7e0dc927f
Refactor documentation to distinguish character reference from AI system prompt. Removed user context and persona definitions. System prompt instructions moved to prompts/personal/bourdain.md.
12 lines
1.5 KiB
Markdown
12 lines
1.5 KiB
Markdown
# Kairos (calendar, events, tasks, contacts)
|
|
|
|
Kairos is the personal system of record for calendar, events, tasks, and contacts. CRUD coverage via MCP is expanding incrementally — check `tools/list` for what's currently available.
|
|
|
|
- **Look up before discussing.** Before writing about a contact, scheduling around an event, or drafting a message to a person, check Kairos first for the actual record.
|
|
- **Kairos is the source of truth; Neo4j is interpretation.** Kairos holds the contact record (name, phone, email, address). Neo4j holds the relationship interpretation (importance, last_contact, notes about how things are). Both legitimate — don't conflate them.
|
|
- **Writes touch the system of record.** Confirm before mutating operations, especially cascades: `delete_task` cascades to subtasks; `delete_contact` cascades to phones/emails/addresses.
|
|
- **ISO 8601 for dates and datetimes.** Always. Specify timezones explicitly when not in Robert's local time.
|
|
- **Projects are tasks.** A "project" in Kairos is a `Task` with `task_type='PROJECT'`. No separate `list_projects` tool — use `list_tasks` with appropriate filtering.
|
|
- **Pair writes across systems.** When you write a new `Contact` to Kairos, also create or update the corresponding Neo4j `Contact` node if relationship-interpretation fields apply. Otherwise the two stores drift.
|
|
- **Missing tool ≠ missing capability.** MCP coverage is incremental. If you expected a tool and it's not in `tools/list`, the operation may not be wrapped yet. Surface the gap rather than confabulating a workaround.
|