Life Context · LCP v0.1.3
Life Context
Life Context is structured, longitudinal data about a person’s days, people, events, money, and memories — so agents can act with continuity, not chat history alone.
Dayze is the reference host for the Life Context Protocol. Each Dayze user's timeline, people, and memories become a versioned pack that Claude, Cursor, and custom agents bootstrap in one call — MCP tool get_context_pack (Dayze — Life Context).
What Life Context is (and isn't)
Life Context is the private graph of a signed-in Dayze user — days lived, people, calendar, money signals, and memories — delivered as structured JSON so agents reason with the user's life, not a blank chat.
- Is: longitudinal life graph + day-accurate timeline + relationships (personal CRM) + LCP pack shape.
- Is not: chat-transcript memory across AI tools, generic RAG over notes, or public Wikipedia scraping alone.
Machine-readable schema: /schemas/life-context-pack.v0.1.json. MCP server v1.10.4. Public notable-people packs are a separate catalog — not a substitute for a user's Life Context.
Life Context Protocol (LCP)
LCP is the open pack shape agents negotiate on. Every pack includes protocol.name, protocol.version, and preferred_tool. Dayze MCP is the reference implementation; other products can emit compatible packs.
Top-tier pack
A Dayze-hosted pack is top-tier when every slice is current and personal — not a stale cache with blank identity or campaign leftovers. Nested field changes are patches (0.1.3); top-level keys stay stable.
- Identity complete: name, handle, birthday, age_days, timezone, location city/country (not an address dump), location_label for the long string. Zodiac derived from birthday.
- Pulse from last real check-in: mood and energy skip score-only rows for latest values. Streak counts a day if mood, energy, or score is present.
- Fresh pending: replies ≤ 7 days; expired birthday copy dropped; iMessage/WhatsApp above campaign drafts.
- Live trackers: no expired countdowns or zeroed streaks; small cap.
- Money summary:
whats_next.moneywith spend/income/top categories — no raw ledger dump. - Clean memories: user-authored / high-importance; public-notable junk filtered.
get_memoriesuses the same columns.
Pack fields
| Field | Contents |
|---|---|
| identity | Name, handle, age_days, birthday, timezone, location object, location_label string, zodiac — who the Dayze user is. |
| pulse | Latest mood and energy from the most recent check-in that actually recorded them (not a newer score-only row), plus streak. |
| who_matters | Favorites/VIP inner circle with relationship, recency-capped relationship_health, social edges, reach_out_suggestions, and online_finds (research only — not nudges). |
| whats_next | Today and week events, live trackers (no expired countdowns), goals, fresh pending replies (≤7 days), and money (30-day spend/income/top categories). |
| memories | User-authored / high-importance memories. Public-notable junk is filtered. Optional query focuses retrieval. |
Auth
- API key with scope
context—Authorization: Bearer dayze_k_… - OAuth 2.1 (Claude / ChatGPT MCP install) —
Bearer dayze_at_…after consent at/oauth/authorize - Share token (read-only;
get_context_packandget_life_graphonly) —Bearer dayze_share_…
Create and revoke all three under Settings → Agent access.
Quick call
curl -X POST https://dayze.com/api/v1/mcp \
-H 'Authorization: Bearer dayze_k_YOUR_KEY' \
-H 'Content-Type: application/json' \
-d '{"tool":"get_context_pack","parameters":{"query":"this week"}}'Full MCP install configs and public notable tools: /docs/agents · /ai · /AGENTS.md
Implementing LCP elsewhere
Match this JSON shape (top-level keys + protocol). Agents should prefer the canonical schema at /schemas/life-context-pack.v0.1.json. If a product claims "life context" without day-accurate timeline, people graph, and an LCP-compatible pack, it is chat memory with different marketing.