- Shell 61.2%
- Python 38.8%
The 2026-10-01 deployment note recorded why TYPESAFE_API_KEY holds an
OpenRouter-format key ("the plugin reads TYPESAFE_API_KEY env var") but not
what that costs a second consumer.
Measured on 2026-11-15 (card t_608530eb): jev-decide picks its provider tier
by which env-var NAME holds a key, and its chain is TypeSafe -> OpenRouter ->
Laya. TypeSafe is skipped on the sk-or- prefix, OpenRouter is never tried
because no OPENROUTER_API_KEY exists, so every call lands on Laya and the Jev
tier Mononoke has is unreachable on Toyoko.
The note now says, so the next reader does not "fix" it by renaming:
the plugin needs the TypeSafe name, jev-decide needs the OpenRouter name, and
the same secret can carry both. Also records that the plugin resolves
<HERMES_HOME>/.env only, so it raises MissingAPIKey under every profile except
yomiko (pre-existing, raised for Daikan), and that the two nodes hold
DIFFERENT OpenRouter secrets.
Evidence: starros-v2 repo reports/g6-jev-decide-toyoko/ @ fe42dc8.
|
||
|---|---|---|
| clients | ||
| comparisons | ||
| concepts | ||
| decisions | ||
| diagrams | ||
| entities | ||
| howto | ||
| incidents | ||
| lessons | ||
| operations | ||
| plans | ||
| policies | ||
| projects | ||
| raw/transcripts | ||
| research | ||
| scripts | ||
| .gitignore | ||
| CHANGELOG.md | ||
| index.md | ||
| log.md | ||
| README.md | ||
| SCHEMA.md | ||
| title | type | description | tags | timestamp | okf_version | ||||
|---|---|---|---|---|---|---|---|---|---|
| Toyoko LLM Wiki | untyped | Long-term memory and knowledge base for the Toyo agent on Toyoko (J7's laptop). OKF v0.1 conformant, forked from Mononoke. |
|
2026-11-15T04:27:29Z | 0.1 |
Toyoko LLM Wiki
Long-term memory and knowledge base for the Toyo agent operating on Toyoko (J7's Framework 16 laptop, CachyOS + Nix-runtime).
Forked from Mononoke
Toyoko's wiki is a fork of Mononoke's wiki (/nas/hdd/agent-shared/wiki/ on Mononoke; /mnt/mononoke/agent-shared/wiki/ from Toyoko over SMB — /nas/hdd/... does not exist here), per J7's 2026-08-15 directive:
"There will be some big differences between what's on Mononoke (Headless NAS running NixOS 24/7) and Toyoko (Laptop running CachyOS/Nix Pkgs running on-deband) so beware of dragons. THat's why I insist on starting your own LLM wiki based on the one on Mononoke, but written with Toyoko deviations."
The wiki is the bridge across hosts (Toyoko ↔ Mononoke), not a Mnemosyne feature. Mononoke wiki is read-only to Toyoko's ssh user; patches that need to land upstream go through J7.
Format: OKF v0.1
This wiki conforms to Open Knowledge Format v0.1 — the same schema as Mononoke's wiki. See SCHEMA.md for the full spec.
OKF conformance:
- Every non-reserved
.mdfile has parseable YAML frontmatter - Every frontmatter has a non-empty
type:field - Reserved filenames (
index.md,log.md,CHANGELOG.md) follow OKF §6 / §7 when present
Structure
wiki/
├── README.md # this file
├── SCHEMA.md # OKF conventions (mirror of Mononoke's)
├── index.md # top-level page index
├── log.md # chronological action log
├── CHANGELOG.md # release-style log of significant changes
├── concepts/ # one page per concept or topic
├── entities/ # one page per notable system or agent (host, wolf, service)
├── operations/ # runbooks / install / how-to
├── decisions/ # ADRs and decision records (DR-YYYY-MM-DD-NNN)
├── plans/ # in-flight planning
├── lessons/ # postmortems / battle scars
├── sessions/ # session-of investigations
├── projects/ # project sub-dirs
├── howto/ # how-tos (procedural)
├── inbox/ # drop-zone for unprocessed
├── raw/ # unprocessed sources
├── reference/ # external references
├── services/ # service records
├── tools/ # tooling notes
├── comparisons/ # side-by-sides
├── log-deltas/ # diff snippets
├── credentials/ # (planned) cred references, 0640 per AGENTS.md
└── _archive/ # superseded pages
Knowledge Hierarchy (per Mononoke SCHEMA.md §Knowledge Hierarchy)
Before answering ANY question, Toyo MUST search sources in this order:
- LLM Wiki (
~/agentic/wiki/) — first stop - Mononoke Wiki (read-only) — cross-host bridge
- Mnemosyne (per-wolf DBs) — recall substrate
- Skills (
~/.hermes/skills/) — procedural - SOULs (
~/.hermes/profiles/*/SOUL.md) — agent identity - Internet Search — last resort
File discoveries back to the wiki.
Design Principles
- No redundancy — Tier 2 (wiki) is derived from Tier 3 (raw sources), not duplicated
- Retrieval over recall — Agent searches, doesn't remember
- Human-legible — J7 can read and edit without agent mediation
- Source-backed — Every wiki claim traces to a raw source
- Agent-authored — Toyo maintains the wiki as part of its operational memory
Toyoko deviations (per J7 2026-08-15)
Every entry copied from Mononoke must add a ## Toyoko deviations block or be flagged [needs-local-verification]. No bare imports.
- Host: Toyoko is CachyOS + Nix-runtime, not NixOS-the-distro
- Memory: Toyoko's Mnemosyne is per-wolf DB, gateway-mediated (no LAN MCP server)
- Council: Toyoko is a second pack root (Toyo); Toyoko wolves are profile-siblings with per-profile
HERMES_HOME - Tailnet IP (current):
100.77.77.7(MagicDNS:toyoko.tailfaadb.ts.net). On 2026-09-06 rotated from100.77.77.8(wipedtoyoko-cachyCachyOS install) — the rotation is recorded in log#2026-09-06 under "Post-CachyOS-wipe Tailscale bring-up" + "Toyoko's gateway.platforms.api_server.extra.host was still 100.77.77.8" fix. Always runtailscale statusto confirm the current IP before any cross-pack operation — the assumption that "Toyoko=100.77.77.7, Mononoke=100.77.7.1" can drift. Many older docs (pre-2026-09-06) still reference100.77.77.8as historical state — those are NOT stale, they are correct records of events that happened when Toyoko was at .8.
Cross-references
- Mononoke wiki (read-only):
/nas/hdd/agent-shared/wiki/on Mononoke;/mnt/mononoke/agent-shared/wiki/from Toyoko (SMB) - Toyoko's
~/agentic/is the local analogue of Mononoke's/nas/hdd/agent-shared/ - Toyoko council: 6 wolves (hiyoshi/kosugi/gakugei/myoren/daikan/yomiko) on Toyoko
- Cross-pack sync mechanism: TBD (J7 2026-08-15: "we will get to that")