magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit

Backfill

The recent history the daemon replays to a dashboard on connect, so its charts start populated instead of empty. It is served from a bounded ring buffer of the last few hundred samples.

Elsewhere

In data engineering a backfill recomputes a pipeline over a past date range (an Airflow backfill). The magus backfill computes nothing: it replays samples the daemon already holds.

Example

The console's dashboard receives the backfill when it connects to the daemon.

magus server start

Used in

In the docs:

See also

glossaryexecution-and-caching
Last updated (2df714e8)
Glossary

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). Op in full.

Engine

The interpreter a magusfile runs on; magus embeds the Buzz engine. Engine in full.

Broker

The per-user background process that holds this host's capacity: the machine budget every run claims slots from, and the shared services runs keep warm. A run starts it on demand; broker: off in magus.yaml runs without one. Broker in full.

Daemon

The background process a person starts with magus server start. It serves MCP, the console, background jobs and the warm knowledge graph, and adopts nested magus calls into one pool. Daemon in full.

Snapshot

A point-in-time view of live state (the pool's occupancy or a tick of exported metrics), as opposed to accumulated history. Snapshot in full.

Backfill

The recent history the daemon replays to a dashboard on connect, so its charts start populated instead of empty. It is served from a bounded ring buffer of the last few hundred samples. Backfill in full.

Knowledge graph

The queryable graph of a workspace's spells, targets, docs, and code relationships; query it with magus query/explain/path. Knowledge graph in full.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.