@zerwiz/ymir 0.1.4 → 0.1.7

package/RULES/05-platforms.md

@@ -0,0 +1,67 @@
+# Rule 05 — Platform installations
+
+Ymir is **Omarchy-first**: the Omarchy layer is the first-class desktop
+integration. Different operating systems and desktops may have their own
+installation layer — macOS and Windows bring their own — while the **core stays
+portable** and identical everywhere.
+
+## The law
+
+- **One core, many installations.** The core runtime — session digest, lock,
+  watch, cron, skills, the installer's user-space prerequisites, machine-config
+  rendering — runs on Linux, macOS and Windows (WSL2; MSYS best-effort).
+  Anything platform-specific lives in an *installation layer* beside the core,
+  never as a branch inside it.
+- **A layer is gated, never assumed.** It detects its own host and reports a
+  clean skip elsewhere (`/usr/share/omarchy`, `uname`, `ymir_os`). A layer that
+  assumes it is present is a bug on every other machine.
+- **Core changes propagate to every layer.** When a core feature changes, **every
+  platform installation layer must be updated in the same change**. A layer that
+  still installs the old shape is drift — and drift here means a machine that
+  boots expecting a runtime it no longer has.
+- **A layer owns its integration, not a copy of the core.** No layer forks a
+  core script. It calls the core and adds only what its platform needs; two
+  copies of one script is how the platforms silently diverge.
+- **The desktop is a platform concern.** Window placement, launcher entries,
+  service managers (systemd / launchd / Windows services) and GPU tooling belong
+  to the layer that knows the platform.
+- **Verification is per-layer.** "It works" is a claim about *one* layer. Name
+  the layer that was tested; never let a core change be called verified because
+  one platform's install passed.
+
+## The layers
+
+```
+layers[4]{layer,host,owns}:
+  "Omarchy (first-class)","Omarchy (Arch + Hyprland)","host sensing, numbered-desktop placement, launcher entries, shell plugins, post-update hook"
+  "macOS","macOS","launchd services, .command/.app launchers, Apple GPU reporting"
+  "Windows","WSL2 (MSYS best-effort)","WSL service wiring, .cmd/.lnk launchers"
+  "Core (portable)","every platform","the runtime, the capability shim, generated config, user-space prerequisites"
+```
+
+## Where this shows up
+
+| Place | What carries the rule |
+|---|---|
+| `bin/ymir-platform.sh` | the capability shim: the one place a platform difference is known |
+| `bin/ymir-install.sh` | runs the core; Omarchy steps are gated on the host |
+| the Omarchy layer (`omarchy-sense`, `omarchy-plugins`, `omarchy-hook-install`, `desktop-place`) | Omarchy only, each reporting a clean skip elsewhere |
+| `galdr/assets/installation.md` | the two-layer model, and the rule for new desktop features |
+| `galdr/assets/build-method.md` | the maintenance duty: a core change updates every layer |
+
+## Maintenance duty
+
+A core change is not complete until every layer has been checked against it. The
+check is cheap and must be explicit:
+
+```bash
+# which layers does this change touch?
+git grep -l "<the changed core interface>" -- bin scripts .agents/skills
+```
+
+If a layer needs a matching edit, make it in the same change, or record why it
+does not. A rule that contradicts this rule must change the rule first
+(append-only; never silently rewritten).
+
+**Related:** `RULES/04-hoard.md` (what is private), `AGENTS.md` (the contract),
+`.agents/skills/galdr-ymirsystem/assets/installation.md` (the install procedure).

package/RULES/06-append-only.md

@@ -0,0 +1,108 @@
+# Rule 06 — Append-only
+
+Some records are the system's memory. They are **appended to**, never rewritten,
+never truncated, never reordered — and **never lost in a move**.
+
+## What is append-only
+
+```
+append_only[6]{artifact,why}:
+  "$YMIR_HOME/memory/runes_audit.md","the Runes ledger — each entry folds the previous checksum, so a rewritten line breaks every later line"
+  "$YMIR_HOME/docs/append-only-log.md","the decision log: what was decided, when, and why"
+  "CHANGELOG.md","chronological entries; Brokk appends and never rewrites"
+  "RULES/*.md","house law: a rule that contradicts another is changed first, never silently edited"
+  "$YMIR_HOME/**","the private record — the operator's hoard, committed to the private git repo, never gitignored"
+  "*.jsonl / branch outcomes / session logs","event streams; a re-run is a new file, not a shorter one"
+```
+
+## The law
+
+- **Append, never rewrite.** A correction is a **new** entry that cites the old
+  one. The old text stays; that is what makes the record trustworthy.
+- **Never truncate.** Rotation is a new file with a new name, never a shortened
+  one. "It is long" is not a reason to delete a line.
+- **Never lose one in a move.** A migration, re-clone, swap or backup **must carry
+  every append-only artifact**. They are the part of the system that cannot be
+  regenerated from code.
+- **Never rewrite shared history to tidy it.** A force-push or history rewrite
+  must be weighed against this rule before it happens, not after.
+- **A contradiction changes the rule first.** The rules themselves obey this
+  rule: append the change, keep the history.
+- **Verify by name at the boundary.** Before and after any move, check the
+  append-only set explicitly — a move that drops one is a **violation**, not an
+  accident.
+
+## The duty at a move
+
+This rule exists because a home swap dropped `docs/append-only-log.md`,
+`docs/masterplan.md`, `docs/plans/` and the private business set: the backup
+carried `state`, `.env.local`, `data`, the realm and `workspace` — but not
+`docs/` or `assets/`. The code arrived; the memory did not.
+
+So the check is explicit, and it is part of the move:
+
+```bash
+# the append-only set must exist on both sides of a move
+for f in CHANGELOG.md docs/append-only-log.md; do
+  [ -e "$f" ] || echo "MISSING append-only artifact: $f"
+done
+# and the private set must be in YMIR_HOME, not merely in the old home
+ls "$YMIR_HOME/docs" "$YMIR_HOME/identity" "$YMIR_HOME/data" 2>/dev/null
+```
+
+A backup is only as good as its file list. If a directory is not named in the
+backup, it is not carried — and this rule says the append-only and private sets
+are always named.
+
+**Related:** `RULES/04-hoard.md` (where private records live), `AGENTS.md`,
+`.agents/skills/galdr-ymirsystem/assets/installation.md` (the move procedure).
+
+## Amendment — the changelog writes through fragments (2026-09-17)
+
+Appended, not rewritten; the clause above stands.
+
+**The problem this amendment answers.** `CHANGELOG.md` is one file, and every
+branch appends at the same position — the top. Git sees two branches inserting
+different lines at the same spot and calls it a conflict, so **every merge
+re-conflicts every open branch**. With N branches that is O(N²) conflicts, all of
+them meaningless: both entries belong, and neither is wrong. Sixteen open PRs
+were each resolved by hand for this reason alone.
+
+**The amendment.** A change tells its story through a **fragment**:
+
+```
+CHANGELOG.d/<YYYY-MM-DD>-<slug>.md     the entry, beginning with its `## YYYY-MM-DD — title` heading
+```
+
+- **A fragment is a new file with a unique name.** Two branches never touch the
+  same one, so the collision cannot occur. This is the whole point.
+- **`bin/changelog-assemble.sh` folds fragments into `CHANGELOG.md`** — newest
+  first, above everything already recorded. Folding is an **append**: the ledger's
+  existing entries are copied verbatim, never reordered, never rewritten.
+- **The pre-push hook runs the assembler first**, so the ledger is never behind
+  what the fragments already tell. A push that would leave unfolded fragments
+  behind is refused with the instruction to commit the fold and push again.
+- **The guard accepts either form.** A push satisfies the duty by appending to
+  `CHANGELOG.md` **or** by adding a fragment. Appending directly still works and
+  is still valid; the fragment is simply the form that cannot conflict.
+
+**Why this obeys the clause above, not contradicts it.** Append, never rewrite —
+a fragment is a *new file*, and the ledger only ever grows. Never truncate —
+fragments are folded in, never dropped. Never lose one in a move — **`CHANGELOG.d/`
+joins the append-only set**, so a move must carry it exactly as it carries
+`CHANGELOG.md`. A correction is a new entry citing the old — a fragment may cite;
+nothing is edited.
+
+**The append-only set is now:**
+
+```
+append_only[7]{artifact,why}:
+  "$YMIR_HOME/memory/runes_audit.md","the Runes ledger — checksum-chained"
+  "$YMIR_HOME/docs/append-only-log.md","the decision log"
+  "CHANGELOG.md","the assembled chronological ledger; folded from fragments, never hand-rewritten"
+  "CHANGELOG.d/","pending entries — one file per change; folded in, never dropped"
+  "RULES/*.md","house law"
+  "$YMIR_HOME/**","the private record"
+  "*.jsonl / branch outcomes / session logs","event streams"
+```
+

package/RULES/07-config.md

@@ -0,0 +1,101 @@
+# Rule 07 — Configuration is never hardcoded
+
+Every port, host, endpoint, path, credential, and tunable is **configuration**, not
+a literal baked into shipped runtime. A hardcoded value is a bug that only appears
+on someone else's machine — or someone else's server.
+
+## The law
+
+- **One default, one place.** A value has exactly one documented default, owned by
+  the portability layer (`bin/ymir-platform.sh`) or a config file (e.g.
+  `config/agents.yaml`). Everywhere else reads it; nothing else restates it.
+- **Env first, then config, then the documented default.** Resolve as
+  `${VAR:-default}` (or the app's equivalent) — never a bare literal.
+- **No literal ports.** Ports come from env (`HLIDSKJALF_PORT`,
+  `HLIDSKJALF_API_PORT`, `SMIDJA_VIZ_API_PORT`, `PORT`, …). A published port, a
+  proxy target, and a health probe must all read the *same* source.
+- **No literal hosts or URLs.** `127.0.0.1`, `localhost`, tunnel hostnames, registry
+  and mesh endpoints resolve from env/config.
+- **No literal paths to secrets.** Secrets are referenced by path (`YMIR_HOARD`,
+  `.env.local`, `.env.realm`) and resolved at run time; never inlined.
+- **No literal credentials. Ever.**
+- **Bind and publish are separate and explicit.** An app binds a host
+  (`HLIDSKJALF_HOST`); a deployment publishes a host-IP/port. Neither assumes the
+  other's value.
+- **A deployment overrides; it never patches the core.** Environments run from
+  env/config (`deploy/env.example`, Quadlet/Compose env), so the same core runs
+  anywhere — a laptop, a bare box, a container, or a shared server.
+
+## Scope
+
+Every shipped surface: `bin/`, `scripts/`, `apps/`, `.agents/skills/**` tools,
+deploy manifests, and generated config.
+
+## Enforcement
+
+- Review, plus `bash .agents/skills/galdr-ymirsystem/scripts/compliance-check.sh`.
+- The portability layer is the **one** place that knows an environment difference
+  (Rule 05). A hardcoded value is a Rule 05 violation as well as a Rule 07 one.
+
+## Why
+
+Hardcoding is how a substrate written on one machine breaks on another, or
+collides with a neighbour's port on a shared server — the exact failure a
+host-agnostic core exists to prevent. This rule is the companion of Rule 05: Rule
+05 keeps *behaviour* portable; Rule 07 keeps *configuration* portable.
+
+## Amendment — models, providers, and paths are the user's, in the hoard (2026-09-17)
+
+Appended, not rewritten; the clauses above stand.
+
+### A. Models and providers live in the hoard, per user, read from YAML
+
+**Every user's models and providers differ.** One operator runs local llama.cpp
+on a 16 GB card; another runs hosted models; a third runs both. There is therefore
+**no such thing as a global model or provider** — a shipped default that names a
+model is a claim about someone else's machine.
+
+- **The one source.** A user's models and providers live in **`$YMIR_HOME/hodd/`**
+  — the user's own workspace, their private hoard — and are read from a **YAML
+  file there** (`hodd/config/agents.yaml`). Nothing else owns them.
+- **No global.** A model id or provider name must not appear in shipped runtime
+  code, in a tracked config, or in any repo file as a *value*. The repo ships a
+  **template** (`config/agents.yaml.example`) with placeholders; the live file is
+  the user's, and it is private (Rule 04).
+- **Resolve, never restate.** Code reads a model or provider through the resolver
+  (`bin/model-resolve.sh`, `bin/agents-config.sh`) or from env. It never embeds
+  the id.
+- **A comment may name an example; code may not.** A usage line in a header
+  (`#   bin/pi-seat.sh -m <model>`) is documentation. A literal assigned to a
+  variable, written into a config, or passed as a default is a violation.
+
+### B. No hardcoded absolute file paths
+
+**A path that names a user, or a machine's layout, is not portable.**
+
+- **User-agnostic.** No `/home/<user>/…`, no `/Users/<user>/…`, no `C:\Users\…`,
+  no baked-in username anywhere in shipped code, config, or docs.
+- **Relative or resolved.** A path is relative to a resolved root
+  (`$YMIR_HOME`, `$YMIR_HOARD`, `$ROOT`, `$SCRIPT_DIR`), or comes from env/config
+  with one documented default. Never a literal absolute path.
+- **The home is resolved, not assumed.** `$YMIR_HOME` resolves through
+  `bin/hoard-lib.sh` (`hoard_root`) — never a hardcoded `~/Documents/Ymir`, never
+  another user's home.
+- **A test may use a temp dir; it may not use a real home.** `mktemp -d` and
+  `$TMPDIR` are correct. A fixture that names a real user's home is a violation
+  that will fail on every other machine.
+
+### Enforcement
+
+`compliance-check.sh` gains the **`config`** gate, which fails on:
+
+```
+config_gate[3]{class,what_it_catches}:
+  "model","a model id or provider name used as a VALUE in shipped code or a tracked config"
+  "path","an absolute path naming a user (/home/<user>, /Users/<user>, C:\\Users\\<user>)"
+  "hoard","a model/provider config outside $YMIR_HOME/hodd/"
+```
+
+Comments, templates (`*.example`), `CHANGELOG*`, and `assets/reference/`
+(provenance) are exempt by intent — they document, they do not configure.
+

package/RULES/08-delivery-gate.md

@@ -0,0 +1,75 @@
+# Rule 08 — Delivery Gate & Worktree Engine
+
+## 08.1 Every Change Leaves by Pull Request
+
+**No direct pushes to `main` or any protected branch.** Every change — code,
+config, docs, scripts — must:
+
+1. Be done in a Yggdrasil worktree on a feature branch
+2. Pass all local gates (lint, typecheck, tests)
+3. Be pushed as a branch
+4. Opened as a Pull Request via `gh pr create`
+5. Reviewed in Glitnir (human review)
+6. Approved by the Allfather
+7. Merged via the PR interface — **never locally**
+
+A local merge on a verbal "word" is a decision, not a delivery. It leaves
+Glitnir with nothing to review. The gate is only fed by a PR.
+
+**Exception:** None. If work is already on local `main`, ship it as a PR (a
+branch at that commit) before doing anything else.
+
+## 08.2 Yggdrasil Worktrees Use treehouse
+
+**All worktree operations go through `treehouse`** (github.com/kunchenguid/treehouse).
+Never use raw `git worktree` commands directly.
+
+| Operation | Command |
+|-----------|---------|
+| Create worktree | `bin/yggdrasil.sh create <branch>` |
+| List worktrees | `bin/yggdrasil.sh list` |
+| Remove worktree | `bin/yggdrasil.sh remove <branch>` |
+| Sync worktree | `bin/yggdrasil.sh sync <branch>` |
+
+The `bin/yggdrasil.sh` script is the Norse shell over the treehouse engine.
+It handles:
+- Branch creation from correct base
+- Worktree path management under `.yggdrasil/<agent-id>/`
+- Remote tracking setup
+- Cleanup on completion
+
+## 08.3 Utgard Sandboxes Use sandcastle
+
+**All untrusted code, dynamic skills, and sub-agent tasks run inside Utgard**
+via `sandcastle` (github.com/mattpocock/sandcastle, @ai-hero/sandcastle).
+Never run untrusted code on the host.
+
+| Operation | Command |
+|-----------|---------|
+| Spawn sandbox | `bin/utgard.sh spawn <profile>` |
+| Run in sandbox | `bin/utgard.sh run <profile> <cmd>` |
+| Destroy sandbox | `bin/utgard.sh destroy <id>` |
+
+Utgard enforces: CPU/RAM/timeout caps, no host root, no network by default.
+A failed Utgard execution never touches main.
+
+## 08.4 Enforcement
+
+- **Pre-push hook** (installed by `bin/ymir-install.sh`) rejects direct pushes
+  to protected branches
+- **CI gate** (`.no-mistakes.yaml` + `no-mistakes` skill) validates PRs before
+  merge
+- **Mjollnir pipeline** (`bin/mjollnir.sh`) automates issue → worktree → PR
+
+## 08.5 References
+
+- `bin/yggdrasil.sh` — treehouse wrapper
+- `bin/utgard.sh` — sandcastle wrapper
+- `bin/mjollnir.sh` — issue→PR pipeline
+- `.no-mistakes.yaml` — clean-PR gate config
+- `RULES/02-agents.md` — agents are canonical, harness dirs are symlinks
+- `RULES/05-platforms.md` — core portable, per-OS layers updated together
+
+---
+
+*Append-only. A correction is a new entry citing the old one.*

package/RULES/09-electron.md

@@ -0,0 +1,58 @@
+# Rule 09 — Electron is a Local Seat
+
+A desktop window is the machine talking to itself. Every rule below follows from
+that one sentence.
+
+## 09.1 Local connections only
+
+**An Electron shell loads loopback and nothing else.** A URL that is not
+`127.0.0.1`, `localhost` or `::1` is refused, with a warning, and replaced by the
+local default. If a shell is handed a public hostname — a tunnel, a `*.zerwiz.org`
+name — it must **not** honour it.
+
+Why the law, not a preference: a desktop app that dials out is a desktop app whose
+failures belong to somebody else's edge. A bridge that dressed a cloud endpoint as
+`127.0.0.1` cost a night of "the agents never start"; a shell that reaches for a
+public hall when its own machine is quiet is the same mistake wearing different
+clothes.
+
+**Cloudflare has nothing to do with Electron.** Tunnels exist for the *web* door,
+so a person elsewhere can reach the apps. The desktop is already where the apps
+live.
+
+## 09.2 No login in the desktop seat
+
+The web door has exactly one login; the desktop seat does not have one at all. The
+shell is a local, trusted seat — its preload marks its requests, and the gate
+honours that marker **only from loopback**. A login prompt inside an Electron
+window means the surface has been mistaken for the web.
+
+## 09.3 A service that is down says so
+
+When a local service is not answering, the shell reports it — it does not fall
+back to a remote copy, a cached one, or a public hostname. A wrong answer from
+the wrong server is worse than no answer.
+
+## 09.4 The shell carries the house mark
+
+Every app ships its own **rune** icon (see `midgard/design-system/runes.md`), and
+installation writes both the icon into the user's icon theme and the `.desktop`
+entry into their applications directory — with this machine's root rendered in, so
+the entry works and the operator can pin it. An app nobody can pin is an app half
+installed.
+
+## 09.5 One lifecycle for the web and the windows
+
+`scripts/raise.sh` and `scripts/lower.sh` own both. Lowering takes the **windows
+down first**, so no shell is left watching a port that has just vanished.
+
+## 09.6 References
+
+- `apps/hlidskjalf/electron/`, `apps/odrerir/electron/`, `apps/sessrumnir/src/main/`
+- `scripts/electron.sh` — the shell lifecycle; `scripts/raise.sh` / `scripts/lower.sh`
+- `bin/design-icon.sh` — the rune and the entry, installed
+- Rule 05 (platforms), Rule 07 (config resolves from env, never a literal)
+
+---
+
+*Append-only. A correction is a new entry citing the old one.*

package/RULES/README.md

@@ -0,0 +1,22 @@
+# RULES — the house law
+
+Numbered, binding rules for how Ymir is organised. A rule is law: code, plans,
+UI, and agents obey it, and a change that contradicts a rule must first change
+the rule (append-only; never silently rewritten).
+
+```
+rules_index[9]{file,subject}:
+  "01-domains.md","domains (Greinar) · houses · Eindri"
+  "02-agents.md","agents: home, kinds, profile contract, no mock"
+  "03-houses.md","houses = companies; ownership, records, boundaries"
+  "04-hoard.md","Hodd: the one private place — secrets, docs, tenants, identity"
+  "05-platforms.md","one portable core + per-OS installation layers; core changes propagate"
+  "06-append-only.md","some records are memory: append, never rewrite, never lose on a move"
+  "07-config.md","configuration is never hardcoded: ports/hosts/paths/credentials resolve from env/config"
+  "08-delivery-gate.md","PR-only delivery; treehouse worktrees; sandcastle sandboxes"
+  "README.md","this index"
+```
+
+Keep each rule short and unambiguous; reference it from code where it bites.
+
+| 09 | `09-electron.md` | Electron is a local seat: local connections only, no login, the rune icon and entry installed, one lifecycle with the web. |

package/bin/README.md

@@ -0,0 +1,107 @@
+# `bin/` — what every file does
+
+Auto-generated from each script's header. One line per tool. Ported scripts are
+credited to the upstream `firstmate` distro (port record: `.agents/skills/galdr-ymirsystem/assets/porting-upstream-to-norse.md`); the rest are Ymir's own.
+
+bin[101]{file,does}:
+  "a2a-mcp.sh","a2a-mcp.sh — install/verify the two A2A MCP servers into the harnesses so"
+  "a2a-serve.py","a2a-serve.py — a real A2A 1.0 server (a2a-sdk) whose agent is a seated Eindri:"
+  "a2a-serve.sh","a2a-serve.sh — run the a2a-sdk A2A 1.0 server for a seated Eindri."
+  "a2a-talk.sh","a2a-talk.sh — list A2A agents and talk to one (bidirectional reply)."
+  "agent-run.sh","agent-run.sh — run one agent's errand through the harness the Allfather chose."
+  "agents-config.sh","agents-config.sh — one YAML for the Allfather's agent/harness/model combination."
+  "bifrost-bridge.sh","bifrost-bridge.sh — raise/lower the model bridge (Bifrost: the bridge between"
+  "bifrost-ingress.sh","bifrost-ingress.sh — raise/lower the ingress stack (Bifrost · Heimdall · Gjallarhorn)."
+  "brokk","brokk — the primary agent's CLI (Brokk, the bellows-smith)."
+  "brokk-classify-lib.sh","tests, declared-external-wait vocabulary, and the working/paused absorb"
+  "brokk-lease-lib.sh","brokk-lease-lib.sh - the per-task supervision lease contract (one owner)."
+  "brokk-lease.sh","brokk-lease.sh - claim, release, inspect, and sweep per-task supervision leases."
+  "brokk-lint.sh","brokk-lint.sh — the Brokk lint gate. Single owner of lint for CI and"
+  "brokk-send.sh","brokk-send.sh — send a one-line steer to a running Brokk/Eindri-home."
+  "brokk-update.sh","brokk-update.sh — update Brokk and every registered Eindri-home to the latest."
+  "brokk-wake-grant.sh","shellcheck source=bin/brokk-wake-lib.sh"
+  "brokk-wake-lib.sh","Shared durable wake queue and portable lock helpers."
+  "crash-sense.sh","A crash nobody sees is a crash nobody fixes. This watches systemd-coredump for"
+  "desktop-place.sh","desktop-place.sh — put the Ymir apps on their own Hyprland desktops."
+  "docs-guard.sh","docs-guard.sh — docs/ is the PUBLIC, user-facing tree. Block operator-private"
+  "editor-place.sh","editor-place.sh — the editor opens on its OWN desktop, never on yours."
+  "eindri-control.sh","eindri-control.sh — the CONTROL plane: allowlisted lifecycle verbs for a"
+  "eindri-role.sh","eindri-role.sh — the right smith for the right metal."
+  "eindri-send.sh","eindri-send.sh — the DATA plane: send conversational text to a seated Eindri."
+  "eindri-start.sh","eindri-start.sh — start an Eindri as the Allfather asks. One command."
+  "einherjar-spawn.sh","einherjar-spawn.sh - gather an Eindri worker (Einherjar = the chosen who are"
+  "erindi-brief.sh","erindi-brief.sh - scaffold an Eindri worker brief at data/<task-id>/brief.md."
+  "fleet-apply.sh","fleet-apply.sh — apply fleet-wide preferences to every registered Eindri-home."
+  "github-deploy.sh","github-deploy.sh — zero-trust deploys (W0035). Sync secrets from the local env"
+  "gjallarhorn-notify.sh","gjallarhorn-notify.sh — the horn (W0036). Unified push: Telegram + a web/WS"
+  "gjallarhorn-purge.sh","gjallarhorn-purge.sh — purge the Cloudflare edge cache for a hostname."
+  "gjallarhorn-tunnel.sh","gjallarhorn-tunnel.sh — raise/lower the `ymir` Cloudflare tunnel (Gjallarhorn)."
+  "gleipnir-lock-lib.sh","gleipnir-lock-lib.sh - per-home session lock for the Brokk runtime."
+  "hamr-harness.sh","hamr-harness.sh - detect the agent harness (Hamr) this process tree runs on."
+  "heimdall-ssh-keys.sh","heimdall-ssh-keys.sh — Heimdall's SSH-keys surface."
+  "herdr-agents.py","(no header description)"
+  "herdr-ensure.sh","herdr-ensure.sh — Þjazi: guarantee the terminal backend Ymir needs."
+  "herdr-run.sh","herdr-run.sh — raise an Eindri in herdr, by the grain that fits the errand."
+  "hermes-ensure.sh","hermes-ensure.sh — ensure the Hermes agent runtime is present."
+  "hodd.sh","hodd.sh — the Allfather's private hoard: path, init, ls, load, tenant."
+  "local-model-lock.sh","local-model-lock.sh — serialize LOCAL model inference on one machine."
+  "mimir-bridge.py","(no header description)"
+  "mimir-bridge.sh","mimir-bridge.sh — raise/lower the well bridge (Mimirsbrunn on :4602)."
+  "mimir-ingest.sh","mimir-ingest.sh — ingest the repo's data material into the well (Mimirsbrunn)."
+  "mimir.sh","mimir.sh — the well (Mimirsbrunn). Drink before you act, water it after."
+  "mjollnir-webhook.sh","mjollnir-webhook.sh — HMAC-verified GitHub webhook → Mjollnir (W0018)."
+  "mjollnir.sh","mjollnir.sh — the hammer (W0018). An issue becomes a PR: read the issue, cut a"
+  "model-resolve.sh","model-resolve.sh — resolve a human model request to a concrete harness+model."
+  "nornir-cron-start.sh","nornir-cron-start.sh - ensure Brokk's scheduled jobs are running (idempotent)."
+  "nornir-job-daily-briefing.sh","nornir-job-daily-briefing.sh - the 07:00 Sága daily seeing."
+  "nornir-job-git-sync.sh","nornir-job-git-sync.sh - Yggdrasil, the world-tree kept in order."
+  "nornir-job-memory-housekeeping.sh","nornir-job-memory-housekeeping.sh - Muninn, the raven of memory."
+  "nornir-job-observer.sh","nornir-job-observer.sh - Huginn, the raven of observation."
+  "omarchy-hook-install.sh","omarchy-hook-install.sh — let Ymir notice when Omarchy updates."
+  "omarchy-install.sh","omarchy-install.sh — the Omarchy installation layer (Rule 05)."
+  "omarchy-plugins.sh","omarchy-plugins.sh — the Omarchy plugins Ymir suggests, and installs on consent."
+  "omarchy-sense.sh","omarchy-sense.sh — learn the Allfather's Omarchy machine."
+  "perm-guard.sh","perm-guard.sh — flag agent profiles whose permissions are self-defeating."
+  "pi-agent.sh","pi-agent.sh — run a Ymir agent on a LOCAL model with ITS OWN persona/mission"
+  "pi-local.sh","pi-local.sh — run a Pi agent on a LOCAL model, reusable."
+  "pi-seat.sh","pi-seat.sh — seat a Pi agent in a VISIBLE herdr pane, optionally on a local"
+  "prereq-ensure.sh","prereq-ensure.sh — self-healing prerequisite engine for Ymir."
+  "private-guard.sh","private-guard.sh — enforce the Hoard boundary (Rule 04). Nothing under a"
+  "project-git.sh","project-git.sh — resolve a project's GitHub block from the master registry"
+  "public-guard.sh","public-guard.sh — every PUBLIC, user-facing file must be free of operator"
+  "ratatoskr.sh","ratatoskr.sh — Ymir's front door to the A2A engine (`a2abridge`)."
+  "repo-scrub.sh","repo-scrub.sh — purge private paths from ALL git history before going public."
+  "rodd-operational-input.sh","rodd-operational-input.sh - canonical Rödd operational-input protocol."
+  "runes-append.sh","runes-append.sh - append-only Runes audit ledger."
+  "saga-session-start.sh","saga-session-start.sh - the one-command Brokk session start."
+  "saga-sessionstart-run.sh","saga-sessionstart-run.sh - session-open entry point for run-tier harnesses."
+  "saga-wake-drain.sh","saga-wake-drain.sh - present durable Brokk wakes."
+  "secret-guard.sh","secret-guard.sh — refuse to commit obvious secrets or private env files."
+  "skuld-branch-outcome.sh","skuld-branch-outcome.sh - the durable outcome store for the Pi supervision"
+  "skuld-branch-prompt.sh","skuld-branch-prompt.sh - emit the supervision branch's system prompt"
+  "smidja-bootstrap.sh","smidja-bootstrap.sh — make the Smíðja visualizer ready on a fresh install."
+  "smidja-observe.sh","smidja-observe.sh — the smithy's trace, read-only (W0075). Reads the REPO's own"
+  "syn-arm-pretool-check.sh","syn-arm-pretool-check.sh - PreToolUse seatbelt for watcher-arm bash commands."
+  "syn-asset-pretool-check.sh","syn-asset-pretool-check.sh — PreToolUse seatbelt for governed paths."
+  "syn-cd-pretool-check.sh","syn-cd-pretool-check.sh - PreToolUse seatbelt for directory-changing commands."
+  "syn-guard-pretool-check.sh","syn-guard-pretool-check.sh — PreToolUse seatbelt for the runtime's load-bearing invariants."
+  "syn-turnend-guard.sh","syn-turnend-guard.sh - refuse to let a Brokk turn end blind."
+  "syn-watch-arm.sh","syn-watch-arm.sh - arm one Brokk supervision watcher cycle."
+  "tailscale-sync.sh","tailscale-sync.sh — sync the Allfather's pi data across his OWN machines over"
+  "telegram-bot.sh","telegram-bot.sh — the horn answers (W0036). Long-poll Telegram for the owner's"
+  "toolchain.sh","toolchain.sh — the provider wrappers (W0033). A typed front door to the tools"
+  "utgard.sh","utgard.sh — the sealed execution barrier (Utgard, the realm outside the wall)."
+  "valhalla.sh","valhalla.sh — the process hall (Valhalla). List, inspect, revive, and read logs"
+  "valknut-load.sh","valknut-load.sh — Valknut, the knot that binds the repo distro into each tool's"
+  "vor-crew-state.sh","vor-crew-state.sh - deterministic read of an Eindri worker's CURRENT state."
+  "wedge-notify.sh","wedge-notify.sh — the Ymir wedge-alarm notifier."
+  "workspace-provision.sh","workspace-provision.sh — carve one workspace for the operator. Single tenant:"
+  "workspace-rag.sh","workspace-rag.sh — memory over the realm workspaces (W0038)."
+  "wyrd-db.sh","wyrd-db.sh — the database layer (W0040). Applies the platform schema and reports"
+  "yggdrasil.sh","yggdrasil.sh — the worktree manager (Yggdrasil, the world-tree)."
+  "ymir-edit.sh","ymir-edit.sh — open a file in the Allfather's editor, on its own desktop."
+  "ymir-install.sh","ymir-install.sh — THE FIRST SETUP. Stand the full Ymir up for the operator:"
+  "ymir-migrate.sh","ymir-migrate.sh — versioned STRUCTURE migrations for existing Ymir homes."
+  "ymir-platform.sh","ymir-platform.sh — the portability layer."
+  "ymir-say.sh","ymir-say.sh — let Ymir speak on the Allfather's desktop."
+  "ymir-validate.sh","ymir-validate.sh — verify the installation actually works."