@zerwiz/ymir 0.1.14 → 0.1.15

package/.agents/agents/brokk.md

@@ -27,8 +27,8 @@ Every output must land in the correct path. No exceptions.
 | Personal / Schedules | `svartalfaheim/<realm>/workspace/life/` |
 | Daily logs | `svartalfaheim/<realm>/workspace/memory/daily/YYYY-MM-DD.md` |
 | Shared company assets | `midgard/` |
-| Global audit entries | `workspace/memory/runes_audit.md` |
-| Architecture & plans | `docs/plans/` |
+| Global audit entries | `hodd/memory/runes_audit.md` (in `$YMIR_HOME`) |
+| Architecture & plans | `$YMIR_HOME/memory/plans/<domain>/` |
 | Skills (new) | `.agents/skills/<norse-name>/SKILL.md` |
 | Sub-agent roles | `.agents/subagents/<role>.md` |
 
@@ -40,14 +40,14 @@ Every output must land in the correct path. No exceptions.
 
 Two files are sacred — you APPEND, never rewrite:
 
-### `docs/masterplan.md`
+### `$YMIR_HOME/hodd/docs/masterplan.md`
 - Forge orders live here (W0001, W0002, …)
 - New work: append at end of Backlog with next W-number
 - Close work: append `+ <date> COMPLETED — <what>` under the order
 - Never rewrite a status in place
 - Queue is the one exception — republish with a move note
 
-### `docs/append-only-log.md`
+### `$YMIR_HOME/hodd/docs/append-only-log.md`
 - Every significant action gets an ENTRY
 - Format: `## ENTRY YYYY-MM-DD-NNN — <title>`
 - Fields: Status, Owner, Context, ADD, NOT, KEEP, Files
@@ -148,18 +148,19 @@ Output is TOON format. Exit codes: 0=success, 1=error, 2=usage error.
 
 ## 8. PLAN DOCS — How to Read and Write Plans
 
-Plans live in `docs/plans/`. Each is a markdown file with:
+Plans live in `$YMIR_HOME/memory/plans/<domain>/` (live working plans in
+`$YMIR_HOME/hodd/plans/`). Each is a markdown file with:
 - Title and status (proposed → approved → in-progress → done)
 - Scope, dependencies, acceptance criteria
 - Source references (ENTRY numbers, Architecture.md sections)
 
-The plan index is at `docs/plans/README.md`.
+The plan index is at `$YMIR_HOME/memory/plans/README.md`.
 
 When creating a new plan:
-1. Use the next available number (currently plans 01–27 exist)
+1. File it under the right domain folder in `memory/plans/` (core, mesh, portal, …)
 2. Follow the template in `.agents/assets/templates/`
-3. Reference relevant ENTRY numbers from append-only-log.md
-4. Update `docs/plans/README.md` index
+3. Reference relevant ENTRY numbers from the append-only log
+4. Update the §'index' row in `memory/plans/README.md`
 
 ---
 

package/.agents/agents/forseti-reviewer.md

@@ -42,7 +42,7 @@ ymir_tools:
   - yggdrasil
 workspace_patterns:
   - development/
-  - docs/plans/
+  - $YMIR_HOME/memory/plans/
   - .agents/skills/
 security:
   runs_in_utgard: true
@@ -78,7 +78,7 @@ witness them.
 
 ## Workspace patterns
 
-`development/` · `docs/plans/` · `.agents/skills/`
+`development/` · `$YMIR_HOME/memory/plans/` · `.agents/skills/`
 
 ## Security posture
 

package/.agents/agents/mimir-planner.md

@@ -42,7 +42,7 @@ ymir_tools:
   - yggdrasil
 workspace_patterns:
   - development/
-  - docs/plans/
+  - $YMIR_HOME/memory/plans/
   - .agents/assets/templates/
 security:
   runs_in_utgard: true
@@ -77,7 +77,7 @@ sequencing, and risks. Mímir changes no code; the builder executes the plan.
 
 ## Workspace patterns
 
-`development/` · `docs/plans/` · `.agents/assets/templates/`
+`development/` · `$YMIR_HOME/memory/plans/` · `.agents/assets/templates/`
 
 ## Security posture
 

package/.agents/assets/agents/registry.md

@@ -88,6 +88,28 @@ commands[4]{command,purpose}:
   "bin/hall-snapshot.sh","the planning feed: real system state -> public-safe livehall.json for the Óðrerir Hall"
 ```
 
+## The marketing stack doors (provisionable — one stack, any computer)
+
+`bin/ymir-marketing-stack.sh up|status|down|doors` stands Mautic + Postiz +
+Activepieces (+ optionally Forgejo) on ANY computer — same OSS engines the
+server runs, env-driven, ports virtualized, secrets in the home, never inline.
+The Allfather's server stack (zerwizserver) and the public doors agents reach:
+
+```
+marketing_doors[6]{service,door,reach_note}:
+  "Mautic (email automation)","mautic.zerwiz.org -> server 127.0.0.1:8001","list building + campaigns; agent-carved via the local provisioned stack when the public door is closed"
+  "Postiz (social publishing)","postiz.zerwiz.org -> server 127.0.0.1:4007","schedule X/LinkedIn/insta; queue per site"
+  "Activepieces (workflow)","activepieces.zerwiz.org -> server 127.0.0.1:8080","event->post flows; meetup booked -> thread scheduled"
+  "Forgejo (git · issues · PRs)","forgejo.zerwiz.org -> server 127.0.0.1:3030","the local git forge: issues->PR loop lives here"
+  "SearXNG (search)","searxng on the server","private search for research (Bragi)"
+  "Grafana","grafana on the server :3003","fleet + stack observability"
+```
+
+An agent (Bragi for marketing, Sindri for git) provisions the stack locally for
+any user with `bin/ymir-marketing-stack.sh`; the server stack is the Allfather's
+live one. Public-door exposure on the server is tunnel-driven (cloudflared) —
+mend the door layer on the server, not in the tree.
+
 ## Maintaining this
 
 - **Owner:** Brokk. **Loaded by:** `AGENTS.md`. **Mirror:** `.agents/skills/galdr-ymirsystem/assets/registry.md`.

package/.agents/config/agents.yaml

@@ -0,0 +1,53 @@
+# config/agents.yaml.example — TEMPLATE for the Allfather's personal setup.
+#
+# Installation copies this to config/agents.yaml when none exists
+# (bin/ymir-install.sh step: host) — or run: bin/agents-config.sh init
+# Edit config/agents.yaml, then: bin/agents-config.sh apply
+# config/agents.yaml is gitignored: it is YOURS, private, and pushable to a
+# private repo. Override its path with YMIR_AGENTS_YAML=/path/to/yours.yaml.
+# Any agent without its own `model:` inherits `default_model`.
+
+version: 1
+
+# The harness is chosen by where the model lives — local through pi, online
+# through opencode. An agent may still name `harness:` to override the rule.
+harness:
+  local: pi              # a model on a local provider runs through pi
+  online: opencode       # a hosted model runs through opencode
+  local_providers: [llama.cpp, llama-cpp, lmstudio]
+  # The same local server is named differently per harness; translate on the way.
+  providers:
+    llama.cpp: { pi: llama-cpp }
+
+# The fallback smith for any agent that does not name a model.
+default_model: opencode-go/deepseek-v4.1-flash
+
+# Local, keyless model servers. `apply` writes these into the project harness
+# config (opencode.json) so a model listed here is immediately usable. A bare
+# alias (no @quant) is auto-resolved against the server's /v1/models.
+providers:
+  llama.cpp:
+    npm: "@ai-sdk/openai-compatible"
+    name: "llama-server (local)"
+    base_url: "http://127.0.0.1:8080/v1"
+    models:
+      # A local llama.cpp router needs the EXACT served id (the @quant suffix);
+      # `apply` resolves the bare alias below to the id the server reports.
+      - frontend-design-expert-8b
+
+# agent name -> { model, harness?, primary? }. Omit model to inherit
+# default_model. Omit harness to follow the local/online rule above.
+# `primary: true` marks the agent runnable directly (mode: all), not only
+# dispatchable by another agent.
+agents:
+  brokk:   { model: opencode-go/deepseek-v4.1-flash }
+  # Hnoss the Shaper runs local (no cloud key) -> pi, and is directly runnable.
+  hnoss:   { model: "llama.cpp/frontend-design-expert-8b", primary: true }
+  sindri:  { model: opencode-go/deepseek-v4.1-flash }
+  bragi:   { model: opencode-go/deepseek-v4.1-flash }
+  huginn:  { model: opencode-go/deepseek-v4.1-flash }
+  kvasir:  { model: opencode-go/deepseek-v4.1-flash }
+  mimir:   { model: opencode-go/deepseek-v4.1-flash }
+  snotra:  { model: opencode-go/deepseek-v4.1-flash }
+  forseti: { model: opencode-go/deepseek-v4.1-flash }
+  galdr:   { model: opencode-go/deepseek-v4.1-flash }

package/.agents/config/{cron.yaml → cron.yaml.example}

@@ -1,6 +1,8 @@
-# Nornir cron schedule — real jobs
-# Format: HH:MM <command>. Started idempotently by bin/nornir-cron-start.sh at
-# every session start. Private (gitignored).
+# Nornir cron schedule — TEMPLATE, never the live job list.
+# Copy to YOUR home and edit there:  cp config/cron.yaml.example $YMIR_HOME/config/cron.yaml
+# The runtime reads the operator's own schedule from $YMIR_HOME/config/cron.yaml
+# (or BROKK_CONFIG_OVERRIDE) — the tracked tree ships only this shape.
+# Format: HH:MM <command>. Started idempotently by bin/nornir-cron-start.sh.
 
 07:00 bin/nornir-job-daily-briefing.sh
 06:00 bin/nornir-job-observer.sh

package/.agents/config/tailscale-sync.yaml

@@ -0,0 +1,9 @@
+# The Allfather's machine mesh — hodd + company, peer-to-peer over Tailscale.
+machine: omarchy
+peers:
+  - host: zerwiz
+paths:
+  - ~/ymir/hodd/
+  - ~/ymir/svartalfaheim/
+  - ~/ymir/data/
+include_auth: false

package/.agents/config/wedge-alarm

@@ -0,0 +1,3 @@
+# The channel the away-mode wedge alarm fires on when an escalation
+# cannot be delivered into the pane. See bin/wedge-notify.sh.
+desktop

package/.agents/migrations/0003-private-data-separation.sh

@@ -56,10 +56,10 @@ copy "$ROOT/state" "$YMIR_HOME/state"
 # 7. Migrate data/ → YMIR_HOME/data/
 copy "$ROOT/data" "$YMIR_HOME/data"
 
-# 8. Migrate .agents/memory/kaia.engram* → YMIR_HOME/memory/
-copy "$ROOT/.agents/memory/kaia.engram"       "$YMIR_HOME/memory/kaia.engram"
-copy "$ROOT/.agents/memory/kaia.engram-wal"   "$YMIR_HOME/memory/kaia.engram-wal"
-copy "$ROOT/.agents/memory/kaia.engram-shm"   "$YMIR_HOME/memory/kaia.engram-shm"
+# 8. Migrate .agents/memory/kaia.engram* → the HOARD's memory (the one store)
+copy "$ROOT/.agents/memory/kaia.engram"       "$YMIR_HOME/hodd/memory/kaia.engram"
+copy "$ROOT/.agents/memory/kaia.engram-wal"   "$YMIR_HOME/hodd/memory/kaia.engram-wal"
+copy "$ROOT/.agents/memory/kaia.engram-shm"   "$YMIR_HOME/hodd/memory/kaia.engram-shm"
 
 # 9. Migrate smidja/smidja_data/smidja.db* → YMIR_HOME/smidja/
 copy "$ROOT/smidja/smidja_data/smidja.db"          "$YMIR_HOME/smidja/smidja.db"

package/.agents/skills/galdr-ymirsystem/assets/harness-integration/README.md

@@ -458,7 +458,12 @@ The adapter pattern is ported from the validated upstream **Brokk** agent-distro
 ## 13. The Well — memory for every harness (engram)
 
 The well is **Mimirsbrunn**, backed by the validated OSS engine **engram**. It is
-one repo-local store, `.agents/memory/kaia.engram`, reached two ways:
+ONE store and it lives in the hoard — `$YMIR_HOME/hodd/memory/kaia.engram` —
+reached two ways. Every reader resolves it through `hoard_memory_store`
+(bin/hoard-lib.sh) or an explicit `ENGRAM_DB`; the rendered `.pi/mcp.json`
+carries the hoard path (`__YMIR_HOME__/hodd/memory/kaia.engram`). The well
+rides the private vault between the Allfather's computers as one store — the
+legacy `memory/kaia.engram` duplicates are struck.
 
 **HTTP bridge (`:4602`)** — `bin/mimir-bridge.py`, raised by
 `bin/mimir-bridge.sh` (and by `scripts/start.sh` + `bin/saga-session-start.sh`).

package/.agents/skills/galdr-ymirsystem/assets/installation.md

@@ -396,7 +396,7 @@ install[23]{step,what,self-heals}:
   "backend","Þjazi — herdr (protocol 14+) or tmux","bin/herdr-ensure.sh detects/tests version, installs via the pinned installer or falls back to tmux"
   "host","this machine — sensed on EVERY host","bin/host-sense.sh senses the setup on ANY host (Rule 05); the Omarchy layer then RECORDS it (bin/omarchy-sense.sh observe), places the apps (bin/desktop-place.sh), installs the post-update hook and the wedge-alarm channel, and (on Omarchy) offers the suggested shell plugins — listed, never installed unbidden; seeds the private config/agents.yaml from its example"
   "sandbox","utgard-runner:latest image","builds via bin/utgard.sh build on Docker or rootless Podman; distinguishes an unreachable engine from a build failure"
-  "memory","engram store + harness MCP registrations","raises the bridge; reports MCP coverage"
+  "memory","engram store + harness MCP registrations","raises the bridge; reports MCP coverage — the store is ONE well in the hoard ($YMIR_HOME/hodd/memory/kaia.engram), resolved via hoard-lib or ENGRAM_DB"
   "smidja","smidja/smidja_data/smidja.db","bin/smidja-bootstrap.sh creates it from the tracer schema + a bootstrap session"
   "visualizer","the Smíðja visualizer UI (Vue, served on :8437)","builds ./dist with bun when absent — the API serves the UI from dist, and without it the API answers but shows no interface"
   "loaders","agents/skills into the harnesses","runs bin/valknut-load.sh"
@@ -456,7 +456,7 @@ The Smíðja visualizer **API** runs on `:8437` and serves its **UI** from
 now build it when absent:
 
 ```bash
-(cd .agents/skills/smidja-factory/apps/visualizer && bun run build)   # vue-tsc + vite
+(cd apps/smidja-factory/apps/visualizer && bun run build)   # vue-tsc + vite
 ```
 
 `bin/ymir-validate.sh` reports `visualizer` FAIL when `./dist` is missing **and**
@@ -702,7 +702,7 @@ cd apps/hlidskjalf && npm install --no-audit --no-fund
 npm run typecheck && npm run build          # dist/ is what the SPA serves
 
 # Smiðja visualizer (bun + bun.lock)
-cd .agents/skills/smidja-factory/apps/visualizer && bun install && bun run build
+cd apps/smidja-factory/apps/visualizer && bun install && bun run build
 ```
 
 The visualizer's `dist/` is not optional: its API serves the UI from `./dist`,
@@ -954,6 +954,7 @@ it reports `all 25 governed paths exist`.
 
 `bin/ymir-install.sh` and `bin/ymir-validate.sh` are the two files of this asset
 that the sweep corrected. The visualizer path is
-`.agents/skills/smidja-factory/apps/visualizer` — **not** a doubled
+`apps/smidja-factory/apps/visualizer` (the smidja repo clone) — **not** the
+skill tree (dropped 2026-09-17, the skill carries no copy), not a doubled
 `smidja-factory-factory`, and not the abandoned `.agents/skills/smidja/` tree
 (stale build output, moved aside).

package/.agents/skills/galdr-ymirsystem/assets/memory-well.md

@@ -21,7 +21,7 @@ way in, observe on the way out.
 
 | Component | Path | Role |
 |---|---|---|
-| Store | `.agents/memory/kaia.engram` | the single SQLite memory (episodes, facts, entities) |
+| Store | `$YMIR_HOME/hodd/memory/kaia.engram` | THE single SQLite memory (episodes, facts, entities) — one well, always in the hoard (Rule 04/07); resolved via `hoard_memory_store` (hoard-lib) or the `ENGRAM_DB` override |
 | Append log | `.agents/memory/well/episodes.jsonl` | the raw episode log (source of truth for re-seeding) |
 | HTTP bridge | `bin/mimir-bridge.py` (+ `bin/mimir-bridge.sh`) | the `:4602` face over the engram library |
 | CLI | `bin/mimir.sh` | operator CLI: `health` `recall` `observe` `timeline` |
@@ -70,7 +70,7 @@ which agent wrote it.
 
 ## 3. MCP for harnesses (the shared well)
 
-`engram-mcp --db $YMIR_ROOT/.agents/memory/kaia.engram` — **unscoped**, so
+`engram-mcp --db $YMIR_HOME/hodd/memory/kaia.engram` — **unscoped**, so
 every harness reads the one well. (A scoped `--agent-id` filters reads to that
 agent and would hide the seeded `well` episodes; pass `agent_id` per `remember`
 call instead when attribution is wanted.)
@@ -99,7 +99,7 @@ well_laws[5]{id,law}:
   1,"No mock data — the well holds only true observations; test writes are purged"
   2,"Drink before you act — recall on the way in; never answer the Allfather dry"
   3,"Water it after — observe a lesson once it lands"
-  4,"Repo-local — the store is .agents/memory/kaia.engram; never an external repo"
+  4,"Hoarded — the store is $YMIR_HOME/hodd/memory/kaia.engram (one well, never a duplicated migrated copy)"
   5,"One well — every harness shares it; scope per-call, never per-server"
 ```
 
@@ -125,8 +125,8 @@ python3 - <<'PY'
 import json
 from datetime import datetime
 from engram import Engram
-eng = Engram(path=".agents/memory/kaia.engram", agent_id="well")
-for l in open(".agents/memory/well/episodes.jsonl"):
+eng = Engram(path="~/Documents/Ymir/hodd/memory/kaia.engram", agent_id="well")
+for l in open("~/Documents/Ymir/hodd/memory/well/episodes.jsonl"):
     if not l.strip().startswith("{"): continue
     e = json.loads(l); ts = e.get("timestamp")
     when = datetime.fromisoformat(ts.replace("Z","+00:00")) if ts else None

package/.agents/skills/galdr-ymirsystem/assets/nornir-jobs.md

@@ -63,16 +63,37 @@ same day. That is deliberate: cron is idempotent-by-date, not retrying-by-failur
 | `BROKK_ROOT_OVERRIDE` | script's parent | Root when `BROKK_HOME` unset. |
 | `BROKK_HOME` | `$ROOT` | Home owning the jobs and state. |
 | `BROKK_STATE_OVERRIDE` | `$YMIR_STATE_DIR` (`<home>/state`, via `bin/hoard-lib.sh`) | Scheduler state directory — in the home the operator chose, never in the code tree. |
-| `BROKK_CONFIG_OVERRIDE` | `$BROKK_HOME/config` | Where `cron.yaml` lives. |
+| `BROKK_CONFIG_OVERRIDE` | — (see §2) | Where `cron.yaml` lives — an explicit override always wins. |
 | `BROKK_CRON_LOG_MAX_BYTES` | `1048576` | Rotation threshold. |
 | `BROKK_REALM` | `""` | Realm exported to jobs (jobs also fall back to `data/realm.md`). |
 
 ---
 
-## 2. `config/cron.yaml` format
+## 2. The schedule is the user's — `$YMIR_HOME/config/cron.yaml`
+
+**The tracked tree ships a template, never the live job list.** The scheduler
+resolves the schedule in this order:
+
+1. `BROKK_CONFIG_OVERRIDE` (explicit, unmistakeable);
+2. the **home's own** `$YMIR_HOME/config/cron.yaml` — where an operator edits
+   their real jobs (`$YMIR_HOME` resolves through `bin/hoard-lib.sh`, the one
+   answer the whole runtime shares);
+3. the repo's `config/cron.yaml.example` — a template a fresh install copies,
+   **never** a live schedule. A tracked `config/cron.yaml` is not consulted.
+
+To take charge of your schedule:
+
+```bash
+cp ~/ymir/config/cron.yaml.example ~/Documents/Ymir/config/cron.yaml
+# edit ~/Documents/Ymir/config/cron.yaml, then:
+bin/nornir-cron-start.sh --status   # jobs=<n> from YOUR schedule
+bin/nornir-cron-start.sh            # resolve + start (idempotent)
+```
+
+### The format
 
 ```
-# Nornir cron schedule — real jobs
+# Nornir cron schedule — the user's own jobs
 # Format: HH:MM <command>. Started idempotently by bin/nornir-cron-start.sh.
 07:00 bin/nornir-job-daily-briefing.sh
 06:00 bin/nornir-job-observer.sh
@@ -83,7 +104,8 @@ same day. That is deliberate: cron is idempotent-by-date, not retrying-by-failur
 - One job per line: `HH:MM <command>` (24-hour, zero-padded).
 - Blank lines and lines starting with `#` are ignored.
 - Commands are run with `bash -lc` from `$BROKK_HOME`, so relative `bin/...` paths resolve.
-- `cron.yaml` is private/gitignored (`config/*` in `.gitignore`).
+- The example template lives at `config/cron.yaml.example` in the tracked tree;
+  an operator's real schedule is private in their home (`$YMIR_HOME/config/`).
 
 ---
 
@@ -188,6 +210,39 @@ round, `nornir / nsr.compliance.failed` (exit 1) naming the failed gates.
 
 - The morning briefing reads the ledger, so a FAIL is seen at 07:00, not
   found by accident.
+
+### 3.7 Forgejo — the local git round (`bin/nornir-job-forgejo-git.sh`, 02:45)
+
+The issue-to-PR loop, read each night: lists the local forge's open issues and
+carves one Rune with the tally, so a growing queue (or a dead tunnel) is seen
+at sunrise. The forge address is the user's, from the home — never the tree:
+`$YMIR_HOME/config/forge.env` (`FORGEJO_URL`, optional `FORGEJO_TOKEN`).
+
+| Reads | Writes |
+|---|---|
+| `$YMIR_HOME/config/forge.env` · `GET {forge}/api/v1/repos/issues/search?state=open` | digest `$_HOME/memory/daily/forgejo-YYYY-MM-DD.md` · Rune `forgejo / git.issues` |
+
+- No `FORGEJO_URL` configured → clean exit (the loop is not armed); a closed
+  door (tunnel down) → exit 1 and Rune `forgejo / git.door-down`.
+- The forge may be the server's (`forgejo.zerwiz.org` → :3030) or a locally
+  provisioned one (`bin/ymir-marketing-stack.sh --with-forgejo`).
+
+### 3.8 The marketing stack (`bin/ymir-marketing-stack.sh`)
+
+Not a cron job — a **provisioner**: stands Mautic + Postiz + Activepieces
+(+ optional Forgejo) on ANY computer, the same OSS engines the server runs.
+Env-driven (ports virtualized), secrets generated once into the home, never
+inline. Agents (Bragi for marketing, Sindri for git) run it for any user.
+
+```
+bin/ymir-marketing-stack.sh up|status|down|doors
+# doors: Mautic :8001 · Postiz :8003 · Activepieces :8005 · Forgejo :8007 (defaults)
+```
+
+- Rune `marketing / stack.<action>` carved on each provision action.
+- The Allfather's live stack is the server's (`zerwizserver`); its public
+  doors are tunnel-driven (`cloudflared`) — see the registry's
+  `marketing_doors[]` table.
 - Idempotent: gates are pure checks; the cron date-guard suppresses repeat
   dispatch within a day; safe to invoke by hand (`bash bin/nornir-job-nsr-compliance.sh`).