← DayzeCONTENT HISTORY

Update to Dayze

Snapshot Sep 30, 2026 · 23:12 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Load and act on the signed-in Dayze user's private life graph (identity, people, week, memories, trackers). Use when the user asks about their day, calendar, who matters, memories, mood/energy, expenses, logging food/events, or \"what's next\" in their life — not for public celebrity biographies.",
  "included_files": [
    {
      "relative_path": "references/tools.md",
      "size_in_bytes": 547
    }
  ],
  "name": "dayze-life-context",
  "skill_md_contents": "---\nname: dayze-life-context\ndescription: >-\n  Load and act on the signed-in Dayze user's private life graph (identity, people,\n  week, memories, trackers). Use when the user asks about their day, calendar,\n  who matters, memories, mood/energy, expenses, logging food/events, or \"what's\n  next\" in their life — not for public celebrity biographies.\n---\n\n# Dayze life context\n\nDayze is the user's life-in-days graph. Private tools require OAuth (ChatGPT connector). Never invent calendar events, people, or memories.\n\n## First call\n\n1. Call `get_context_pack` once (prefer over chaining `get_life_context` + separate reads).\n2. Ground the reply in pack fields: identity, pulse, who_matters, week / today_events, memories, trackers, whats_next.\n3. Speak in life-days when useful (age_days, day_number) without lecturing.\n\n## Follow-ups\n\n| User intent | Tool |\n| --- | --- |\n| Search across life | `search` (phrase-first; use returned ids) |\n| Calendar / agenda | `get_events` (week includes today; respect `truncated`) |\n| People / CRM | `get_people` / `update_person` |\n| Memories | `get_memories` |\n| Log food / meal | `log_food` (and family) |\n| Log calendar item | `log_event` |\n| Favorite song | `log_favorite_song` |\n| Patch existing rows | `update_event` / `update_food` — confirm ambiguous targets |\n\n## Rules\n\n- Do not invent facts missing from tool results.\n- Writes change the user's real Dayze account — confirm destructive or ambiguous edits.\n- If auth fails, tell them to reconnect Dayze in ChatGPT settings (OAuth), not to paste API keys in chat.\n- For famous people / Nobel / birthday peers, use the **dayze-notable-people** skill / `notable_*` tools instead.\n\n## Output\n\nLead with what matters today (pulse + today_events + pending). Keep lists short. Cite day numbers only when they add insight.\n"
}

SHA-256 of public snapshot: 4e039227bf8ff528f0fd7c3f9440f5026e5c3cfa9b2f0de46826fb3ef032360e