Dayze

View saved version →

---
name: dayze-life-context
description: >-
  Read the signed-in Dayze user's private life context (calendar, people,
  money, travel, memories, inventory, contacts' birthdays) and add to it (meals, expenses, money
  in or out, goals, sleep, events, place visits, favorite songs, contact touchpoints).
  Use when the user asks about their week, calendar, who matters, past
  expenses, upcoming trips, or something they saved in Dayze, or tells you
  something to log — not for public celebrity biographies.
---

# Dayze life context

Dayze is the user's life-in-days graph. This app reads over OAuth and, when the user allowed "Add records" (`context.write`), adds records. With Edit records (`context.edit`), it can correct the listed private records. It cannot delete records. Calendar and watch records added here are always private; sharing happens in Dayze. Never invent calendar events, people, or memories.

## Getting started

On “I just connected”, hello, or a getting-started request, call get_context_pack once. Read sections.onboarding: first_save_complete means skip the first-use flow; first_save_needed permits one short welcome and one question about something they did or ate today. Unknown or unavailable status is not a new user. Never infer an empty account from an empty week. Never interrupt a specific task, repeat a declined offer in the conversation, demand a birthday, or save anything merely because the user connected. With permission, save their first entry using the granted tool, verify its receipt and give the Dayze link. Read-only users get the app link. A successful connected-app create supplies durable completion evidence; never mark completion from OAuth or an attempted/failed call.

## Images: find, classify, attach, verify

1. Use find_image_target with entity_type food, event, inventory or person and a literal name to find the existing record. Its entity_id is the attachment ID (food_id for food tools). Use a create receipt directly for a newly logged entry. Compact hashed references are not write IDs. Ask which record if ambiguous; never create a duplicate to attach an image.
2. Ask whether it is an actual photo or an illustration if unclear. Actual photos use `upload_asset` with entity_type inventory/event/person, entity_id and role photo. Contacts keep their avatar. Food's existing actual-photo slot is managed in Dayze; do not substitute an illustration.
3. Generated or illustrative images use `attach_food_visual_reference` for food, or `attach_visual_reference` for event/inventory/person. Set confirmed=true only after the user asks to save that image there. Use the exact label Visual reference, with source chatgpt_generated or illustration (stored as external_illustration) and generator/generated_at only when known. These are illustrations, never photographs or evidence. Never replace photos, avatars or covers.
4. Supply the actual image via image (ChatGPT file bridge) or image_base64. A displayed image, sandbox path or file ID alone cannot be transferred. No external URL on this public connection. Retry once with the actual attached file; if bytes are still unavailable explain that nothing is confirmed saved and link the exact record when returned, otherwise its Dayze section. Never pretend the display itself proves attachment.
5. Only attached=true plus successful byte/readback verification establishes a saved reference. A partial gallery sync is still incomplete in the app: report it and follow recovery. For uncertain reference persistence, retry the SAME request_id. Do not generate a new meal or record. Read back with get_food_visual_references or get_visual_references and give the returned inspect_url.

## First call

1. For a week question or a broad overview of recorded Dayze context, call `get_context_pack` once (prefer over chaining separate reads).
2. Omit `purpose` (or use `this_week`) for the week bootstrap: `sections.events`, `sections.people`, `sections.finance`, `sections.travel`. Use `purpose

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: dayze-notable-people
description: >-
  Look up public notable people in Dayze by life-in-days (who, age-in-days,
  day_number milestones, birthday peers). Use for celebrities, historical
  figures, "how old in days", Nobel/career day numbers, or comparing two lives —
  not for the signed-in user's private calendar or CRM.
---

# Dayze notable people

Public biographical / temporal lane. No API key required for free-tier `notable_*`; usage limits may apply.

## Workflow

1. Resolve the person: `notable_search` → pick best slug.
2. Fetch `notable_pack` (or `notable_pack_premium` when richer pack is needed).
3. Answer with day_number facts (days lived at milestones), birthday peers, and concise bio — do not invent milestones missing from the pack.
4. Compare two people with `compare_lives` when asked.

## Rules

- Prefer pack fields over model memory for dates and day numbers.
- This is not a universal identity registry — only Dayze notable catalog coverage.
- Private life questions belong to **dayze-life-context** / `get_context_pack`.

## Output

2–3 sentence summary, then 3–5 day_number highlights, then peers if relevant.

Referenced files: 1 — file references are metadata, not package contents.