Update to Dayze

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,40 +1,77 @@
 ---
 name: dayze-life-context
 description: >-
-  Read the signed-in Dayze user's private life context (identity, people,
-  week, memories, trackers). Use when the user asks about their day, calendar,
-  who matters, memories, mood/energy, expenses, or "what's next" in their
-  life — not for public celebrity biographies.
+  Read the signed-in Dayze user's private life context (calendar, people,
+  money, travel, memories, inventory) 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 is read-only over OAuth (ChatGPT connector). Never invent calendar events, people, or memories.
+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. It cannot edit or delete existing records. New calendar events are private by default; create friends-visible or public events only when the user explicitly asks. Never invent calendar events, people, or memories.
 
 ## First call
 
-1. Call `get_context_pack` once (prefer over chaining separate reads).
-2. Ground the reply in pack fields: identity, pulse, who_matters, week / today_events, memories, trackers, whats_next.
-3. Speak in life-days when useful (age_days, day_number) without lecturing.
+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` `memories` or `inventory` for those single sections.
+3. Ground the reply in the returned `sections` (each has `status`, `items`, `has_more`, `inspect_url`) and in `account_timezone`. The first `limitations` entry names the Dayze account. A record-specific source URL may appear in the item's `why_included`; items do not have an `inspect_url` field.
 
-## Follow-ups
+## Follow-ups (reads)
 
 | User intent | Tool |
 | --- | --- |
-| Search across life | `search_dayze` (phrase-first; use returned ids) |
-| Calendar / agenda | `get_events` (week includes today; respect `truncated`) |
-| People | `get_people_context` |
-| Money | `get_finance_context` |
-| Travel | `get_travel_context` |
+| Find a saved contact, event, merchant, item or memory by keyword | `search_dayze` (`search` = literal keyword, not the whole question) |
+| Recorded calendar in an explicit date window | `get_events` |
+| A person or saved relationship facts in Dayze Contacts | `get_people_context` |
+| A contact's photos as inline images | `get_person_photos` |
+| Recorded spending or merchant in an explicit date window | `get_finance_context` |
+| Recorded upcoming trips in an explicit date window | `get_travel_context` |
+| Cite a Dayze event, contact, or finance record in Sources | `search` then `fetch` |
+
+Every read takes `query` (the user's question) except `fetch`, which takes the opaque `id` from `search`, and `get_person_photos`, which takes the exact contact name or `person_id`. Every context tool except `get_context_pack` and the citation tools (`search`, `fetch`) also needs `purpose`. `get_events`, `get_finance_context` and `get_travel_context` need `from` and `to` as `YYYY-MM-DD` civil dates in the account timezone (at most 93 days apart); turn "this week" or "last month" into explicit dates using `account_timezone` from the pack. If a section is `partial` or `has_more` is true, say the list is incomplete.
+
+## Adding records (writes)
+
+| User says | Tool |
+| --- | --- |
+| A goal they want to track | `create_goal` (life goal; numeric goals need target_value and target_unit) |
+| What they ate or drank | `log_food` (Food Diary; `dish_items` for several dishes, `with` for companions) |
+| A plan, appointment or event | `log_event` (always private; sharing happens in the Dayze app) |
+| Money in or out (a transfer, a bill, money sent or received) | `log_transaction` |
+| Money lent or repaid, or an IOU | Not on this connection: tell the user to record it in the Dayze app |
+| Something they paid for | `log_expense` |
+| How they slept | `log_sleep` (`started_at`/`ended_at` with timezone) |
+| A song they love | `log_favorite_song` |
+| A place they went | `log_place_visit` |
+| They called, messaged or met a contact | `log_interaction` (always private) |
+| A past story or memory | `log_moment` (always private; plans go to `log_event`) |
+| Someone new to remember | `create_person` (an existing match is returned unchanged) |
+| Money they received | `log_income` (plain income; loans and IOUs are recorded in the Dayze app) |
+| Something they own | `add_inventory_item` |
+| A trip, or a city they lived in | `log_travel` (`city` + `start_date`) |
+
+Rules for every write:
+
+- Pass a new `request_id` (a UUID) on every write. Reuse the same `request_id` only to retry the same write; never for a second record.
+- One thing is saved once. Confirm what you are about to add when the prompt is ambiguous (which day, which contact, which currency); never guess a date for a task with no deadline, ask.
+- Use the account timezone for dates and times. Keep the currency the user said; never convert.
+- Writes land only on the connected Dayze account. Never pass another user's id or handle; the server refuses it.
+- The result carries `provenance` (source `chatgpt`, the connected `account.handle`) and a Dayze link. Say which account the record was added to and give the link. The record is attributed to ChatGPT in the user's change history.
+- This app cannot edit, delete, archive, move money, book, buy, post or send. If asked, say so plainly and point to the Dayze app; do not call a read tool to "plan" a change.
+- A write refused with `INSUFFICIENT_SCOPE` means the connection was granted without "Add records": say nothing was saved and ask the user to reconnect Dayze in ChatGPT settings allowing it. `request_id_required` means a `request_id` was missing; retry with one.
 
 ## Rules
 
 - Do not invent facts missing from tool results; partial or no_data answers are honest answers.
-- This app cannot change the user's Dayze account. If they ask ChatGPT to add, edit or delete something, point them to the Dayze app.
-- Cite a record's `inspect_url` when you use it; never build a URL from an id. Say which Dayze account the data is from.
+- Do not use private Dayze tools for public biography, weather, Gmail, live location, booking, buying, messaging or reminders. If “Who is Maya?” does not say whether the user means public knowledge or Dayze Contacts, clarify before reading private data.
+- Use explicit civil dates in the account timezone for event, finance and travel windows. Bounded rows are not complete calendar or ledger totals; preserve native currencies and never sum different currencies.
+- Cite the `Source: https://dayze.com/...` URL in an item's `why_included` when present; otherwise cite the section's `inspect_url`. Never build a URL from an id. Say which Dayze account the data is from.
 - If auth fails, tell them to reconnect Dayze in ChatGPT settings (OAuth), not to paste API keys in chat.
-- For famous people / Nobel / birthday peers, use the **dayze-notable-people** skill / `notable_*` tools instead.
+- These twenty-three tools are the documented base catalog. A feature-gated read may also be available; use only tools actually exposed by the connection. It has no public celebrity or web lookup. For famous people, answer without Dayze and do not call these tools for them.
 
 ## Output
 
-Lead with what matters today (pulse + today_events + pending). Keep lists short. Cite day numbers only when they add insight.
+Lead with what matters this week (upcoming events, then people). Keep lists short. Give dates in the account timezone. After a write, one line: what was added, to which account, with its link.