Back to the notebook

TECHNICAL NOTES / SAMPLE DRAFT

What should an event record remember?

A sample technical note exploring sources, changes and the shape of an event record.

A small schema experiment

Sample draft content. This illustrative note is not a production architecture or a published account of Peter’s implementation.

An extracted value is easier to evaluate when its source travels with it. A record might separate the event identity from observations about it.

type Observation = {
  sourceUrl: string;
  observedAt: string;
  field: string;
  value: string;
};

Questions left open

How should conflicting observations be represented? When does a newer observation supersede an older one? What evidence should a person see before deciding to trust the result?

These questions matter more than committing to the example shape above.

CONVERSATIONS FROM THE FIELD

OFF THE CALENDAR

Research on community calendars, event aggregation, event APIs, and the infrastructure behind trustworthy event data.

The story behind the conversations
Listen on Apple Podcasts