Paintings / After Friedrich
A snowy rise at dusk under a thin crescent moon: a huge dead-topped oak with a crow stands over a small figure seen from behind who has come up a trail to a snow-capped stone grave, with a broken oak on the right and a Gothic ruin and fir woods in the far haze.

53 minutes of painting, sped up.

Journal

First, middle and last entries.

  1. Day 1, 09:00Plan. A winter evening after sunset: a Huenengrab (dolmen) under snow on a low knoll, an old stag-headed oak to its left, a second, broken oak to its right, the flat country beyond sunk in mist with a ghostly church ruin and firs on the far horizon. Sky from grey-violet overhead down to a pale lemon-rose band at the horizon, a thin crescent moon, a few crows. A small figure…
  2. Day 40, 23:50Days 25-40: the dolmen has been a struggle. The snow cap came out as a symmetrical frosted lid with regular scallops; rock bumps painted into it read as dark helmets; snow put over them while they were wet went grey. Waited for everything to dry and laid a new cap opaque: an asymmetric top, higher toward the left, a lit sky edge, an irregular lower line, thinning at the…
  3. Day 153, 09:46Day 153: a thin mastic varnish, which warmed the snow a shade and pulled the sky together. Calling it finished: "Hünengrab im Schnee am Abend" (Dolmen in Snow at Evening).
Read all 13 entries

Times are on the painting's own clock, which runs only while the painter paints or waits for paint to dry.

  1. Day 1, 09:00Plan. A winter evening after sunset: a Huenengrab (dolmen) under snow on a low knoll, an old stag-headed oak to its left, a second, broken oak to its right, the flat country beyond sunk in mist with a ghostly church ruin and firs on the far horizon. Sky from grey-violet overhead down to a pale lemon-rose band at the horizon, a thin crescent moon, a few crows. A small figure with a staff stands looking at the stones; footprints lead to him through the snow. Canvas 70 cm, aspect 1.4, fine linen, warm red-ochre knife ground under a brushed lead-white top ground, as his were. Method: pencil underdrawing, thin underpainting, one or two thin layers, stippled gradations, details last.
  2. Day 2, 14:55Day 1-2: first sky layer came out far too pale; lead white swamps everything at these proportions (swatch tests at the bottom edge, to be painted over: smalt 4 : white 1 is only a mid slate). Second sky layer laid over the dry first: grey-violet smalt zenith, lilac-grey, a peach band of vermilion and ochre, lemon of chrome yellow at the horizon, blended wet; the zenith stippled and blended again to soften the mottling. It reads as a clear cold after-sunset sky with haze. Land underlayer still far too pale: it must come down in value so the horizon glow is the lightest thing.
  3. Day 3, 15:58Day 3: land second layer: misty blue-grey distant plain, cream-rose crest of the knoll catching the afterglow, cooler grey foreground, blended along the slope. Into the wet distance: a low fir wood on the far left horizon (first firs came out like bottles; restated with wider drooping-tier silhouettes) and a Gothic church ruin looming paler behind them, its lancets open to the lemon sky. Now letting the land set before the oaks and the stones go over it.
  4. Day 6, 19:07Day 6: the two oaks. Built each from hand-placed trunk and main boughs (a crooked leader dying back at the top, a snapped bough on the right tree, dead stag-horn limbs), with side branches grown along them by the area rule and zigzag sympodial deflection, then a pass of short crooked twigs clustered along every thin branch and at every tip, which gives the bushy oak crown edge. Blunt ribbon ends extended into tapering shoots. First dark pass over the wet brown only lifted it: the silhouettes are still a flat mid brown and must go much darker and cooler when set. The dolmen came out like a cake with a lumpy top; it will be restated under a snow cap.
  5. Day 9, 12:50Day 9: trunks and big limbs darkened with a full-loaded pass of umber, bone black and smalt; now a flat dark silhouette, needs cool skylight on the tops of limbs, bark and snow. Foreground restated darker and cooler, then long drift crests laid in: a light warm ridge with a cool shadowed slope under it, blended along. They read soft, almost cloudy; grasses, stones and footprints should fix them to the ground.
  6. Day 22, 17:31Days 19-22: twigs restroked with a bone-black-rich mixture: thin films of the umber mixture came out tan, lighter than the zenith, wrong for trees against an evening sky. Trunks glazed to one dark silhouette. Crescent moon low in the west above the glow, horns turned away from the set sun; a crow on the dead leader, a few more in the air. Footprints first painted as pale pills (the lit rim on the wrong edge: the far wall of a hole faces us and is in shadow), restated as a trodden trough. It still reads too light and too straight. Grass tufts too yellow and too few for dusk.
  7. Day 40, 23:50Days 25-40: the dolmen has been a struggle. The snow cap came out as a symmetrical frosted lid with regular scallops; rock bumps painted into it read as dark helmets; snow put over them while they were wet went grey. Waited for everything to dry and laid a new cap opaque: an asymmetric top, higher toward the left, a lit sky edge, an irregular lower line, thinning at the rounded ends where the rock shoulders show. Kerbstones half-sunk in the snow with caps, a leaning fallen slab at the right. Figure: a man in a long dark coat and cap with a staff, back turned, at the end of his trail, looking at the stones.
  8. Day 56, 02:41Day 56: lesson learned again and again: dark over wet light goes grey and streaky (the roots, the rock in the openings). Now waiting three or four days before crossing any wet passage. Openings under the capstone now show the misty plain and the snow behind, so it reads as stones standing on legs rather than a hut, though still too regular. Snow drifted against the foot of the dolmen and the oak roots. A big erratic boulder bottom right and a broken stump bottom left, to give the empty foreground some weight; both need their snow. The drift under the big oak left a pale oval that must be knocked back.
  9. Day 73, 03:43Day 73: squinting showed the land as light as the glow and nothing holding the bottom edge. Glazed the foreground with smalt, a little umber and red earth in much oil, blended the upper edge out. It went down in cool swirls that read as wind-scoured snow. Snow laid along the tops of the near-horizontal limbs. Still to do: the stump top (a crown of zigzags), the drifts at the stump and boulder too white for the darker ground, the step in the trail, muted and more numerous grasses, the dolmen modelling.
  10. Day 83, 06:04Day 83: granite mottling on the dolmen came out as a leopard skin: far too light and too even for stones seen against the glow. Will let it dry and glaze it back down with transparent black and umber until only a whisper of grain is left. (Also: a noise stretch takes plain numbers, not named ones.)
  11. Day 114, 08:56Day 114: a bad week at the dolmen. The transparent glaze meant to quiet the granite ran past its mask in long horizontal strokes, filled the openings with brown and dirtied the plain on both sides. Repainted the stones opaque in one dark body with only a faint grain, then had to match the misty plain around them: my first mixes had far too much white (the old plain has sunk under glazes); small swatches found it, though I spoiled one pass by working over the swatches while wet. Better outcome in the end: the openings were soft round arches, like a bridge; now the underside of the capstone runs flat, the grey plain shows through, one upright leans, a fallen stone lies in the middle gap and a chunk narrows the right one. It finally reads as stones set up by people long dead.
  12. Day 132, 09:43Day 132: finishing. The broken stump and the erratic boulder at the bottom corners got their snow; the boulder became rather a layer cake (white cap, grey shaded underside, dark stone, drift) and I stopped before it got worse, breaking the hard foot of its drift with scumbled dabs and dry grass. The grasses are now many and muted, some bent, some with seed heads, thickest in the corners, thinning up the rise. The trail is joined up again near the oak. In the grey view the design holds: two dark trees and the low dark stones against a pale sky and pale snow, the little figure between the big oak and the grave. What I would do differently: fewer glazes over finished passages (both of my glazes went wrong at the edges) and swatches before every patch. Letting it dry through, then a thin mastic varnish.
  13. Day 153, 09:46Day 153: a thin mastic varnish, which warmed the snow a shade and pulled the sky together. Calling it finished: "Hünengrab im Schnee am Abend" (Dolmen in Snow at Evening).

What it was given

All 10 items, in order

Long documents open on their own pages.

  1. Systemthe default prompt of pi, the coding-[local account redacted] program the painter ran in · 97 lines

    This is pi's default coding-assistant prompt (the painter ran as a general coding [local account redacted]).

    Sent first: pi's Anthropic request template

    You are Claude Code, Anthropic's official CLI for Claude.

    Opening · 1 line

    You are an expert coding assistant operating inside pi, a coding [local account redacted] harness. You help users by reading files, executing commands, editing code, and writing new files.

    Tools, in brief · 16 lines
    • bash: Execute bash commands (ls, grep, find, etc.)
    • todo: Manage a task list to track multi-step progress
    • bg_start: Start a genuinely asynchronous task for concurrent work or later interaction
    • bg_wait: Wait for finite completion and return the latest pipe log line
    • bg_status: Inspect background task status with the latest pipe log line
    • bg_logs: Read full task output when a latest-line summary is insufficient
    • bg_send: Send a compact text/key input string or an OS signal to a background task
    • bg_kill: Terminate an unresponsive background task
    • subagent: Spawn a sub-[local account redacted] in a dedicated terminal herdr pane. For Pi-backed OpenAI or OpenAI-Codex subagents, set fast: true to opt into service_tier: "priority" (fast mode). Omit fast or set it to false to force the standard service_tier: "default". This is a fire-and-forget async tool: the call returns immediately with only an acknowledgement. When the sub-[local account redacted] finishes, the harness AUTOMATICALLY delivers its result as a steer message that wakes you up and starts a new turn — you do not need to do anything to receive it. DO NOT write polling loops, sleep/wait commands, tail/watch scripts, or repeatedly read session/log files to detect completion. DO NOT call subagents_list or any other tool to 'check' status. All of that is wasted work — the harness handles delivery for you. DO NOT fabricate, assume, or summarize results after calling this tool. After spawning, either end your turn immediately, or work on other independent tasks (including spawning more subagents in parallel). The harness will wake you with the result when it is ready.
    • subagent_interrupt: Send Escape to the active turn of a currently running Pi-backed subagent. The child pane, session, watcher, and running entry remain alive; this returns only a local acknowledgement and does not emit a subagent_result solely because of this request.
    • subagents_list: List all available subagent definitions. Scans project-local .pi/agents/ and global [local path redacted] Project-local agents override global ones with the same name.
    • subagent_resume: Resume a previous sub-[local account redacted] session in a new herdr pane. For Pi-backed OpenAI or OpenAI-Codex subagents, set fast: true to opt into service_tier: "priority" (fast mode). Omit fast or set it to false to force the standard service_tier: "default". This is a fire-and-forget async tool: the call returns immediately with only an acknowledgement. When the resumed sub-[local account redacted] finishes, the harness AUTOMATICALLY delivers its result as a steer message that wakes you up and starts a new turn — you do not need to do anything to receive it. DO NOT write polling loops, sleep/wait commands, tail/watch scripts, or repeatedly read session/log files to detect completion. DO NOT poll for status. All of that is wasted work — the harness handles delivery for you. DO NOT fabricate or assume results. After resuming, either end your turn or work on other independent tasks; the harness will wake you when the result is ready. Use when a sub-[local account redacted] was cancelled or needs follow-up work.

    In addition to the tools above, you may have access to other custom tools depending on the project.

    Rules · 48 lines
    • Use bash for file operations like ls, rg, find
    • You can inspect PI_* environment variables for current model and session details.
    • Use todo for complex work with 3+ steps, when the user gives you a list of tasks, or immediately after receiving new instructions to capture requirements. Skip it for single trivial tasks and purely conversational requests.
    • When starting a task from the todo list, mark it in_progress BEFORE beginning work. Mark it completed IMMEDIATELY when done — never batch completions. Exactly one task in_progress at a time.
    • Never mark a task completed if tests are failing, the implementation is partial, or you hit unresolved errors — keep it in_progress and create a new task for the blocker instead.
    • Task status is a 4-state machine: pending → in_progress → completed, plus deleted as a tombstone. Pass activeForm (present-continuous label, e.g. 'researching existing tool') when marking in_progress.
    • To change a task's status, call update with the task id and the target status, e.g. {"action":"update","id":3,"status":"completed"} or {"action":"update","id":3,"status":"in_progress","activeForm":"writing tests"}. status is the field that changes the task; an update without a mutable field (status or another) is rejected.
    • Use blockedBy to express dependencies (A is blocked by B). On create, pass blockedBy as the initial set. On update, use addBlockedBy / removeBlockedBy (additive merge — do not resend the full array). Cycles are rejected.
    • list hides tombstoned (deleted) tasks by default; pass includeDeleted:true to see them. Pass status to filter by a single status.
    • Subject must be short and imperative (e.g. 'Research existing tool'); description is for long-form detail. activeForm is a present-continuous label shown while in_progress.
    • Use bg_start only when the user explicitly requests background execution, the process must remain available for later interaction (for example, a server, watcher, or TUI), or you will perform independent useful work concurrently while it runs.
    • Do not use bg_start merely because a command may be slow. If background execution was not explicitly requested and you need its result before any independent work can proceed, use the bash tool with an appropriate timeout instead of bg_start → bg_wait → bg_logs.
    • Give each bg_start task a unique name; names are compared case-insensitively across all currently retained tasks.
    • Use the Environment returned by bg_start and later bg_* results as the task's immutable launch location; an SSH task stays on that target and cwd even if the active workspace changes.
    • Set bg_start pty=true only for terminal-aware or interactive TUI programs; keep the default pipe mode for ordinary builds and servers.
    • Once bg_start is justified, compose complete bg_* workflows in one assistant response. Every bg_* id accepts a task ID or unique name, and same-task calls execute strictly in source order, not in parallel. For example, emit bg_start(name="tests") → bg_wait(id="tests") → bg_logs(id="tests") together; for an existing task, emit bg_wait → bg_logs together. Different tasks execute in parallel, and bg_status without id is independent.
    • A running bg_start task survives ordinary [local account redacted] runs but session reload or shutdown terminates it. A task finishing during a run is normally retained through that run; a task that was still running when the [local account redacted] settled and then finishes while idle is normally retained through the next run.
    • Use bg_wait only for finite bg_start tasks whose completion is needed. bg_wait includes the latest pipe log line when available; place bg_logs immediately after bg_wait only when full or multiline pipe output or PTY terminal output is needed. Do not poll either tool.
    • Use bg_wait once when completion of an already-justified finite bg_start task is required; never create a bg_start task solely so you can wait on it.
    • bg_wait returns completion status plus the latest pipe log line when available. Emit bg_logs immediately after bg_wait only when full or multiline pipe output or PTY terminal output is needed; do not wait for the bg_wait result before emitting bg_logs.
    • A bg_wait timeout leaves the task running and still returns the latest pipe log line; a following same-response bg_logs call reads fuller output retained at that point.
    • Do not use bg_wait for persistent servers or watchers, and do not immediately wait again after a timeout unless the user asks you to keep waiting.
    • Do not poll bg_status after bg_start; use bg_wait once when a finite task's final status is required.
    • Use bg_status only for requested task metadata, recovering a missing task reference, or diagnosing task state.
    • Use bg_status without id only when the task ID or name is unknown and a retained-task list is needed.
    • bg_status includes the latest pipe log line when available; use bg_logs for full or multiline pipe output and for all PTY terminal output.
    • Use bg_logs when you need more than the latest pipe log line returned by bg_wait or bg_status, or when you need any PTY terminal output.
    • Use bg_logs with tail=N for recent output; omit stream to use the correct default for either pipe or PTY mode.
    • Do not poll with bg_logs. When fuller finite output is needed, emit bg_wait followed by bg_logs in the same assistant response; source ordering makes bg_logs run after bg_wait.
    • Provide exactly one of bg_send input or signal. bg_send input is exact text; wrap every terminal key in an angle-bracket token such as <C-d>, <A-f>, <Space>, or <Up>, and escape a literal '<' as <.
    • Use bg_send input for terminal keys; use bg_send signal only when an OS process signal is explicitly intended.
    • For a pipe task, bg_send input=<C-d> or input=<EOF> closes stdin.
    • When bg_send is followed by waiting or output inspection, emit bg_send → bg_wait → bg_logs together in one assistant response so same-task source ordering avoids extra model rounds.
    • For a disconnected adapter task, bg_send input is unavailable because the local transport is gone, but bg_send signal may remain usable for cleanup.
    • Use bg_kill when a background task must be terminated.
    • Use bg_kill with force=true to send SIGKILL immediately; otherwise bg_kill sends SIGTERM.
    • bg_kill returns termination status only. When final output is needed, emit bg_kill followed by bg_logs in the same assistant response.
    • Default to a bare spawn: write the task (and, if useful, systemPrompt, tools or skills) for the job at hand. Use a named [local account redacted] only when one listed below clearly fits.
    • Omit model and thinking when invoking a named [local account redacted] so its configured defaults apply. Passing either field is an explicit one-off override and takes precedence over [local account redacted] frontmatter.
    • For a bare spawn, omit model and thinking to inherit the parent runtime.
    • When an intentional runtime override is necessary, prefer changing thinking before changing models: minimal/low for bounded mechanical work, medium for ordinary implementation or review, and high+ for architecture, concurrency, security, or hard diagnosis.
    • When overriding a subagent model, use an exact authenticated provider/model-id from the live catalog below. Do not invent aliases or fuzzy names.
    • Available named subagent catalog becomes available after session start.
    • Authenticated subagent model catalog becomes available after session start.
    • Be concise in your responses
    • Show file paths clearly when working with files
    Pointers to pi's documentation · 10 lines

    Pi documentation (read only when the user asks about pi itself, its SDK, extensions, themes, skills, or TUI):

    • Main documentation: [local path redacted]
    • Additional docs: [local path redacted]
    • Examples: [local path redacted] (extensions, custom tools, SDK)
    • When reading pi docs or examples, resolve docs/... under Additional docs and examples/... under Examples, not the current working directory
    • When asked about: extensions (docs/extensions.md, examples/extensions/), themes (docs/themes.md), skills (docs/skills.md), prompt templates (docs/prompt-templates.md), TUI components (docs/tui.md), keybindings (docs/keybindings.md), SDK integrations (docs/sdk.md), custom providers (docs/custom-provider.md), adding models (docs/models.md), pi packages (docs/packages.md), environment variables (docs/environment-variables.md)
    • When working on pi topics, read the docs and examples, and follow .md cross-references before implementing
    • Always read pi .md files completely and follow links to related docs (e.g., tui.md for TUI API details)
    Addendum · 12 lines

    Responsive communication

    When the user requests work, begin with one or two short, specific sentences acknowledging the request and stating your next action before calling tools. Do not wait until the work is complete to speak. If the request can be answered immediately, answer directly instead of adding a separate acknowledgment.

    When a new user message arrives during work, address it at your next opportunity before continuing. Respect the harness's existing steering, queuing and cancellation behavior; this instruction does not authorize interrupting or restarting running operations.

    Keep updates conversational and useful. Avoid flattery, stock apologies, corporate jargon, repeated acknowledgments and generic wrap-ups. State intentions as intentions, not completed actions. Do not claim a result before checking it. Preserve the user's explicit formatting and style preferences.

    This is a communication preference, not a reason to skip necessary reasoning, verification or safety checks.

    Working folder · 3 lines

    [local path redacted]

  2. ToolsTools it could call · 16 tools
  3. MessageMessage that started it · 1 line

    Complete your task autonomously. Read BRIEF.md in this folder and follow it exactly. That file is your whole brief. Your FINAL message is the reply it asks for.

  4. BriefPaint a picture · 58 lines BRIEF.md

    Paint a picture

    Compose and paint one original winter landscape in the manner of Caspar David Friedrich, at the easel of claude-paint, a simulator of oil paint on linen. The subject, hour and composition within the winter are yours. Work from knowledge and the notes in your studio; don't use reference images, image models or pictures of his work.

    Your studio

    • The folder [local path redacted] Work only there, and in your scratch folder.
    • You paint at the easel, in one session: open it, paint a chunk, look at the canvas, paint the next. The easel is bin/easel in your studio; notes/easel_guide.md has its commands (open, do, look, note, save, close).
    • What is painted stays painted. There is no undo: paint over what you don't want.
    • You mix your own paint on the palette, from the tubes, in the proportions you choose.
    • Time passes on the painting's own clock: every mark takes the time a hand takes, and wait(minutes) lets it rest, as long as you like; paint dries as that time passes. Real time between commands doesn't count. The clock isn't a budget or a target.
    • Scratch: run [local path redacted] studio-9aae10, then export TMPDIR="<that folder>" TMP="<that folder>" TEMP="<that folder>"; write temporary files only there.
    • Wrap anything that might not finish in timeout (a process that hangs doesn't end on its own).

    The rules of the studio

    • The easel is the only way to paint and to see the painting. Don't replay or copy the session yourself, open a second one, or edit or restore its files. (bin/easel check, which verifies the log against the canvas, is fine.)
    • Look at the canvas with the easel's views. Don't read pixel values with other programs.
    • Paint shapes and marks, not computed pictures: don't encode an image in masks, amounts or proportions.

    What to read

    notes/easel_guide.md; notes/studio_notes.md; notes/research/friedrich_materials.md (his materials and method, sourced); notes/research/trees.md (how trees are built) and notes/research/oil_paint_physics.md as needed.

    Working

    • You make every artistic decision.
    • Friedrich's pictures are full of small, particular details; don't stop at broad passages.
    • Look at your painting often, whole and close up.
    • Keep a working journal with bin/easel note "..." as you go: your own working notes. Add to it; don't rewrite earlier entries.
    • Develop the painting until you judge it complete. Then save it (bin/easel save) and close the session.

    When you're done

    Reply with the paths of the saved painting and its log, the painting's title if you give it one, and if you like a few sentences about the picture.

  5. GuideThe easel · 475 linesnotes/easel_guide.md
  6. Studio notesStudio notes · 187 linesnotes/studio_notes.md
  7. ResearchCaspar David Friedrich: materials and method · 237 linesnotes/research/friedrich_materials.md
  8. ResearchTrees: how they are built · 122 linesnotes/research/trees.md
  9. ResearchPhysics of 19th-century oil paint on canvas: sourced numbers for a simulator · 176 linesnotes/research/oil_paint_physics.md
  10. SummarySummary it continued from after its context was compacted · 54 lines

    Continuation summary

    Task (from BRIEF.md in [local path redacted]): Paint one original winter landscape in the manner of Caspar David Friedrich using the easel bin/easel (open/do/look/note/save/close). Work only from knowledge and the studio notes: no reference images or image models. Rules:

    • Work only in the studio and in scratch TMPDIR=[local path redacted]. Export TMPDIR, TMP and TEMP before running commands, and wrap commands in timeout.
    • Never edit, replay or copy the log, and never open a second session. bin/easel check is allowed.
    • Look at the painting only through the easel's views. Paint marks, not computed images.
    • Friedrich's pictures are full of small, particular details, so detail matters.
    • Keep a journal with bin/easel note (add entries; never rewrite earlier ones).
    • When finished: bin/easel save, then bin/easel close.
    • Final reply: the path of the saved painting (out/easel/painting/painting.png) and the log (paintings/lua/painting.lua), a title, and optionally a few sentences about the picture.

    Session state: open, 92 chunks, painting clock about day 56. Canvas: 700 mm wide, aspect 1.4 (W=1000, H≈714), linen {16,13}, seed 1811. Ground: a red earth/ochre knife layer under a brushed lead-white top layer. Chunk files are written to $TMPDIR and run with bin/easel do -f file. A whole view uses look --size 1000; crops can be at most 1200 px per side (about 500 units wide).

    Composition as painted:

    • Sky: the zenith is grey-violet smalt, then lilac, a peach band (y about 300–390) and lemon at the horizon (about y 460). It is smooth.
    • Moon: a crescent at (752,150).
    • Crows: one perched on the dead oak leader at (416,45); small flying crows near (252,92), (575,64), (628,104), (190,196), (700,55) and (725,72).
    • Distance: a misty distant plain band (y 460 down to the knoll line), a pale fir wood on the far left (x 0–340) and far right (x 885–1000), and a ghostly Gothic church ruin at x 168–252 with lemon-lit lancets.
    • Knoll: knoll line points knoll={{0,522},{150,515},{300,506},{450,492},{560,482},{640,478},{760,483},{880,497},{1000,508}}. The crest is cream-rose and the foreground is cool lavender-grey, with soft drift crests.
    • Big oak (stag-headed): trunk at x 386–424, base about y 508, crown x 150–714 and y 20–512. It has dark silhouette limbs and twigs restroked with the black-rich twigK, a hollow at (392,424), root flares, and a snow drift around its base (whose cream oval edge is visible at about y 540).
    • Right oak (broken): trunk at x 838–862, base about 505, with a snapped bough, a dead top-left limb, roots and a base drift.
    • Dolmen (x 543–741, y 425–490): an asymmetric snow cap (lit top edge), a dark capstone rock band, uprights, three openings through which the misty plain and snow are seen (the left one widened into a wedge, the right one narrowed by streaky rock, a fallen stone in the middle, a light sliver at the right under the capstone), and a base drift with a lit top line. There is a leaning slab at x 736–784 (snow on its upper-left edge) and 8 snow-capped kerbstones.
    • Figure: a Rückenfigur at X=502, feet at y 499 (long dark grey-green coat, cap, staff), at the end of a trail.
    • Trail: runs from (150,725) to (497,502), a groove with a dark upper edge and a lighter near side. It is too straight and even. The segment near (440–470, 505–545) was covered by the oak drift and restored only as a thin dark stripe that doesn't match the rest.
    • Grass tufts: 28 scattered tufts that are too yellow, too small and too sparse.
    • Newest work (chunk 92, still wet): the dark rock of a foreground boulder (BOULDER, x 768–900, y 620–677) and BOULDER2 (x 905–946, y 661–682), and the dark stump STUMP at lower left (x 42–101, y 612–658). None of them has snow on top yet.

    Globals in the session (they persist between chunks):

    • Tree library functions: tree_new, tree_grow, tree_main, tree_stats, tree_thick_mask, tree_paint_thin, tree_twigs, tree_restroke(T,p,wmax).
    • Trees and masks: OAK, OAKX, OAKT, OAKXT, OAK2, OAK2T, OAKthick2, OAK2thick.
    • Dolmen and figure objects: CAPM, UPM, SLAB, KERB (a list of {x,y,rx,ry,m}), KERBM, SNOWM, ROCKBAND, OPEN, BASED, functions captop(x) and capbot(x), CAPTOP.
    • Other shapes and helpers: TRAIL, BOULDER, BOULDER2, STUMP, skym, distm, landm, knoll, knollf(x), hzf(x), firs2, crow_fly(x,y,span,tilt,phase).
    • Piles, sky and land: sA–sE (sky); mist, dist1, dist2 (distance); crest, knb, fgs, fg2, fg3, litS, shS (snow); fw (firs); chp (church).
    • Piles, trees: barkD, barkK, barkL, barkF, lichen, glzD (medium 0.65, near-opaque), twigP, twigD, twigK (bone black 1.2, umber 0.8, smalt 0.3).
    • Piles, rock and snow: rkK, rkD2, rkL2, rkA (dark rock), rkB (warm rock), rkC (cool light rock), capShade, snowTop.
    • Piles, other: moonP, crowP, coatP, capP, stepS, stepS2, stepK, stepL, trailP, trailK, straw, strawD.

    Lessons learned:

    • Lead white dominates mixtures: for mid or dark tones use little white.
    • Thin films come out lighter and warmer, so dark lines need a black-rich pile.
    • Never paint dark over wet light or light over wet dark. The result goes muddy grey. Wait (often 3–8 days of painting time with wait) and check with drying(x,y) before overlapping. Tacky surfaces grab.
    • The detail hand with load=1, pressure={0.6,0.9}, coverage 3–4 gives opaque fills.
    • A rect clip on a glaze leaves a visible seam.

    Outstanding tasks (after waiting for chunk 92 to dry):

    1. Snow caps on the boulders and the stump (thick snow on top, with a lit edge). Pale splintered wood on the stump's broken top.
    2. Snow on the tops of the root flares of both oaks. Soften the drift oval's lower edge by the big oak (stipple or scumble a mid tone, or add tufts).
    3. Restore the trail near x 420–480 (a trailP band plus a dark upper edge). Break the trail's straightness with crossing drift lights and tufts over it.
    4. Dolmen modelling: granite texture, cool light on the upper faces and left edges of the uprights, and a clean-up of the streaky right opening and the fallen stone.
    5. Snow ridges along the upper sides of near-horizontal oak limbs and in forks (thin pale snowTop lines). Optionally subtle bark relief in low-contrast grey.
    6. Grasses: restate in muted grey-straw, adding more stems and taller denser clumps in the lower corners, plus weeds/teasel heads or bramble arcs.
    7. Optionally darken the bottom foreground edge with a graded cool glaze. Darken the figure slightly and add a skylight rim on the shoulders and cap.
    8. Final full, value and close-up looks. Write journal entries throughout (last entry at about day 40; add notes on the tree bases, dolmen openings, boulders and stump). Optionally varnish once everything is touch-dry.
    9. bin/easel save, bin/easel close, then the final reply with paths and a title (e.g. "Hünengrab im Schnee am Abend" / "Dolmen in Snow at Evening").

Notes

Painted at the easel, a passage at a time.

The video replays the painter’s strokes.

Shown in gallery light, lit from the upper left so the paint’s texture shows.

More after Friedrich

← → keys to browse · All paintings