Skip to content

System fields

System fields are the fields every entry has, in every collection. You never add or remove them.

Example: “Morning run” has the Title “Morning run”, the Icon 🏃, the Entry date 27 Oct 2026, 07:00–07:45, Created at 27 Oct 07:50, Updated at 27 Oct 08:10, and the Parent “Running plan”.

The fields

Field What it is You can edit it Empty?
Title the entry’s name; one per entry yes not decided yet
Icon an emoji or picture shown with the title; one per entry yes yes
Entry date when it happened, with an optional end; the log is ordered by it yes never
Created at when the entry was made never no
Updated at when it last changed; set by the app no no
Parent the one entry this entry sits inside yes yes (most entries)

Every entry also has an id and belongs to exactly one collection. The collection shows as a chip on the right of the top bar.

Rules

  • Title is built in. It is not a property, and there is one per entry.
  • A default title. A collection can give each new entry a title: a fixed text (“Workout”), or a formula that runs once when the entry is made, at the entry’s own date (“Diary” and the date). A title you type always wins.
  • Entry date is never empty. It can have an end: a run from 7:00 to 7:45, a holiday from 1 to 14 Aug. It keeps the time zone where it happened.
  • Created at never changes.
  • Parent: at most one. No loops. A child of a deleted parent becomes a top-level entry. The tree and the breadcrumb come from it. See Notes and the tree.
  • More dates are ordinary Date properties.

Their names

System fields have names that start with @, so they never clash with a property: @title and @date (the Entry date). The names for the other fields are not decided yet.

In the folder

---
title: Morning run
parent: [[Notes/Running plan]]
---

The Title is also the file name (Morning run.md; Morning run 7f3a.md if the name is taken; a locked entry has no title in its name). How the Icon, Entry date, Created at and Updated at are written in the file is not decided yet.