API Reference

Schedule

Dated events in a readable agenda — each with a date, title, optional time, owner, and tag.

A Schedule is dated events laid out as a readable agenda, grouped by day. Each event has a date, a title, and optionally a time, an owner, tags, and typed refs. Humans scan the agenda; the agent gets { kind:"schedule", events:[{ date, title, time, owner }] } with the date parsed to a range-queryable KDate — never a picture of a calendar to read.

Preview
Mon, Jun 15, 2026
  • 09:00
    Kickoff standup
    Krishnan
  • 14:00
    MCP demo
    demo
Wed, Jun 17, 2026

When to use it

Event schedules, meeting agendas, launch plans, on-call calendars — anything that is a list of dated things to attend or do. Because each date keeps its precision, "what's on the 15th?" is a date range query, not OCR over a grid.

Props

Schedule

PropTypeDefaultDescription
eventsScheduleEventInput[]The events, in display order
labelstring"Schedule"Accessible name for the schedule

ScheduleEventInput

FieldTypeDescription
datestring2026, 2026-Q3, 2026-06, or 2026-06-15
titlestringThe event title
timestringOptional time of day, e.g. 09:00
ownerstringOptional owner chip
tagsstring[]Chips
bodyReactNodeOptional detail
refs{ rel?, target, label? }[]Typed links

Consecutive events on the same date are grouped under one day heading.

What the agent sees

Dates are parsed to { iso, precision }, the time and owner are intact, and refs resolve as internal — so the agenda is data the agent can sort and range-query:

{
  "kind": "schedule",
  "id": "launch-week",
  "title": "Launch week",
  "events": [
    {
      "id": "kickoff-standup",
      "date": { "iso": "2026-06-15", "precision": "day" },
      "title": "Kickoff standup",
      "time": "09:00",
      "owner": "Krishnan"
    },
    {
      "id": "mcp-demo",
      "date": { "iso": "2026-06-15", "precision": "day" },
      "title": "MCP demo",
      "time": "14:00",
      "tags": ["demo"]
    },
    {
      "id": "ga-cutover",
      "date": { "iso": "2026-06-17", "precision": "day" },
      "title": "GA cutover",
      "owner": "Krishnan",
      "refs": [
        {
          "rel": "related",
          "target": "/docs/components/releases",
          "label": "Changelog",
          "internal": true
        }
      ]
    }
  ]
}

Same date model as Timeline

Schedule shares the KDate precision model with Timeline, so "everything dated in June" spans both — the corpus answers it once, across components.

On this page

Built withsuperlore