Computed views

A computed view is a fenced okf-view block in a page. Instead of a list you maintain by hand, it declares what to list, and Isomorphic computes it on every read. Add a customer page and every view that should include it does, with nobody updating an index.

```okf-view
kind: pages
under: customers/
filter: { stage: active }
as: table
columns: [title, owner, renewal]
sort: renewal
```

You rarely write one by hand. Ask Claude for “a table of active customers with owner and renewal date” and it writes the block.

How it renders

In Claude and the app, the view is always computed live from the brain’s index.
In the file, Isomorphic also writes a snapshot of the result below the block, between okf-view:snapshot comments, so github.com, Obsidian and other plain-markdown readers still see a real table. The snapshot refreshes whenever the page is saved through Isomorphic, and can go stale in between. Do not edit inside it; it is regenerated on save.
A malformed block renders a visible note saying what is wrong. A view never blocks a read or a save.

Reference

Every view picks a source with kind and a rendering with as.

Key	Applies to	Meaning
`kind`	all	`backlinks`: pages linking to a page. `pages`: content pages. `folders`: the direct sub-folders of `under`. `count` is shorthand for `backlinks` with `as: count`.
`of`	`backlinks`	The target page. Defaults to the page holding the view.
`under`	`pages`, `folders`	A path prefix such as `customers/`, from the brain root or `./`-relative to this page. For `pages` the default is the whole brain; for `folders`, this page’s own folder.
`filter`	all	Frontmatter conditions, all of which must hold. See Filters.
`as`	all	`list` (the default), `table`, or `count`.
`columns`	`table`	`title` (linked) plus any frontmatter keys: `title, owner` or `[title, owner]`.
`describe`	`list`	A frontmatter key shown beside each item.
`group-by`	all	A frontmatter key. Lists and tables get a section per value; a count gets a tally per value. Groups are alphabetical, with “(none)” last, unless the filter lists the key’s values, which then set the order.
`sort`	`list`, `table`	`title` (the default) or any frontmatter key. Numbers sort as numbers.
`order`	`list`, `table`	`asc` (the default) or `desc`.
`label`	`count`	Text after the number, such as `tracked contacts`.

Filters

filter takes an inline map (filter: { type: Contact }) or one indented level. A value is a match unless it starts with an operator:

Value	Matches pages where the key
`Contact`	equals `Contact`, ignoring case
`[lead, active]`	equals any of the listed values
`"< today"`, `"<= -30d"`	is a date before today, or at least 30 days ago
`">= 10000"`	is a number of at least 10,000
`"!= lost"`	is anything but `lost`

<, <=, > and >= compare numbers and YYYY-MM-DD dates. Besides a number or a date, they take today or a day offset such as -30d or +7d (in UTC). != also takes text. A page missing the key, or holding a value that is not a number or date, never matches an operator, != included. List-valued frontmatter matches if any element does.

```okf-view
kind: pages
under: deals/
filter:
  stage: [lead, qualified, proposal]
  value: ">= 10000"
as: table
columns: title, stage, value, next_step_due
group-by: stage
```

Filters, grouping and columns read flat frontmatter keys only. Nested frontmatter is not indexed, so a view cannot see inside it.

Readable tables

Column headers and group headings are made readable, so next_step_due shows as “Next step due”. In Claude and the app, a YYYY-MM-DD date shows relative to today (“Oct 16 · in 12 days”), and under a key named due or ending in _due or _due_date, a past date shows as “N days overdue”. The snapshot written to the file keeps the raw date, so a saved page does not change from one day to the next.

Examples

What is overdue. Tasks past their due date:

```okf-view
kind: pages
under: tasks/
filter: { due: "< today" }
as: table
columns: title, owner, due
sort: due
```

How many pages link here. On a person’s page, the number of meetings that mention them:

```okf-view
kind: count
filter: { type: Meeting Note }
label: meetings
```

Everything that links here, as a table. On a project page:

```okf-view
kind: backlinks
as: table
columns: [title, type, updated]
sort: updated
order: desc
```

A directory, grouped. On people/index.md:

```okf-view
kind: pages
under: people/
group-by: team
describe: role
```

A count per value. Customers per stage:

```okf-view
kind: pages
under: customers/
as: count
group-by: stage
label: customers
```

Sub-folders. On a folder note, one entry per sub-folder, linked through its own folder note:

```okf-view
kind: folders
```

Get started

Using your brain

Reference

Running it

Project

How it renders

Reference

Filters

Readable tables

Examples

​How it renders

​Reference

​Filters

​Readable tables

​Examples

How it renders

Reference

Filters

Readable tables

Examples