Module demands 

What a task or an event asks of you, and what it gives back (docs/tasks.md, “What it asks, what it gives”; docs/capacity.md). Margins before and after it: getting there, getting ready, coming back; kept free in the plan, never counted as a pause. Rated by you from 0 to 10: what it costs, cognitively, emotionally, in anxiety, and to the body and senses (physical effort, standing, noise, crowds); and what it gives back to your well-being. Written in the task’s or the event’s own file (X-SIOUL-BEFORE, X-SIOUL-AFTER, X-SIOUL-COST, X-SIOUL-GAIN), so that it travels with it and other programs keep it.

How it went, said after the task, is kept apart (X-SIOUL-FELT-COST, X-SIOUL-FELT-GAIN, each dated): ratings given after are more accurate than forecasts, anxiety above all is over-predicted beforehand (Rachman 1994; docs/research/capacity-budget.md, criteria 6–7), so the plan uses them when they exist (capacity).

Structs

Demands

The four costs and the gain, each 0 to 10, as you rate them; none unsaid.

Felt

A rating said after the task, on a day.

Margins

Minutes kept before and after: getting there and back, getting ready.

Enums

Level

How heavy something is, as one word: from its highest cost when any is rated (Demands::level), else as you chose it (X-SIOUL-ENERGY).

Constants

AFTER

BEFORE

COST

COST_NAMES

The costs’ names as written, in the order of Demands::costs.

FELT_COST

The costs and the gain as felt, after the task; dated by FELT_ON.

FELT_GAIN

FELT_ON

The parameter that dates a felt rating: ;X-SIOUL-ON=20261006.

GAIN

Functions

felt_date

“20261006” → the date; anything else, None.

felt_of

The felt ratings of a file’s lines, as (name, date parameter, value): one per date, the costs and the gain of a date together; undated ones first, as the oldest, then by date.

minutes_of

Minutes, as a property’s value says them (“20”); at most a day.