field-notes.mdmarkdown · editor view
---
title: "Okibi — field notes"
tags: [okibi, theme]
rev: 1.7
draft: false
---
# Field notes 燠火
A theme is an **attention budget** — every mark spends it. This page shows *every standard element* in the register: the sigils recede, the writing carries. The old draft is ~~struck through~~, identifiers sit in `inline code`, sources link out to [the thesis](https://…) or across the vault via [[dynamic highlighting]], and the one warm mark in prose is a ==yamabuki highlight==. Tagged #okibi.
## Why calm wins
Luminance leads and hue is rationed[^1]. Under fifteen percent of any view carries colour at rest — so the little that does still means something.
> Colour is earned, never decorative. The floor cost of looking must stay low —
> a screen you stare at for hours has no business shouting.
> [!note] Callouts stay quiet too
> The type glyph takes the info hue; the body stays prose. No filled banners.
### Lists, in every flavour
- sigils are furniture — --n7 ghosts
- content is what you see
- nesting just indents; no new colours
1. ordered markers recede the same way
2. numbers here are prose, not data
- [x] port the resting register
- [ ] dial dwell values in a real editor
#### Reference table
| token | role | hue |
| ------ | ------------- | ---:|
| ember | focus · action | 38 |
| sora | links · calls | 252 |
| wakaba | strings | 146 |
## Code, fenced
Code blocks carry the full band-1 register — note the literal 1 resting receded in code, while JSON numbers below take clay, because there the values *are* the content.
```ts
// the resting register: calls carry, keywords recede
export async function resolve(name: string, scale = 1) {
const theme = registry.get(name);
if (theme.dirty === true) throw new Error("stale: " + name);
return theme;
}
```
```json
{ "ground": "okibi", "rev": 1.7, "banked": true, "hues": [38, 252, 146] }
```
Images embed as text until rendered: 
---
[^1]: Hierarchy rides lightness and weight; hue marks a few nominal categories.