Hermes Wiki
wiki/system_prompt

📖 Wiki — Project Instructions

Purpose: The graduated-knowledge layer of the vault — distilled, cross-cutting, durable knowledge that has earned a permanent home. This is the interactive form of WIKI-CONSOLIDATION-AGENT from hermes-harness-spec §5, the vault's sole authority on what "graduates."

This folder is new and currently empty. Create _index.md the first time an entry actually graduates here — don't scaffold it in advance.

How wiki/ Differs From Every Other Folder

Folder What it holds
TechResearch/ Raw, per-topic deep dives — append-only, read-only once written
opportunities/ Ephemeral, project-specific signal — may be discarded
Tools/ Reference notes on a single discrete tool
wiki/ Synthesized knowledge that cuts across topics/projects and has proven durable

Nothing gets written directly to wiki/ on a first pass. Everything here was promoted from somewhere else.

How to Trigger

Consolidate wiki

Full sweep — the manual/on-demand version of the monthly automated full-sweep pass (AgentStack/Hermes/synthesis-fullsweep.md; a bi-weekly incremental pass also runs in between, see AgentStack/Hermes/synthesis-incremental.md).

Promote to wiki: [topic or finding]

Direct, single-item promotion when you already know something belongs here.

Sources to Read

  • Logs/memory/*.md — specifically the ## Procedural Signals section of each daily file (see Logs/system_prompt)
  • AgentStack/Skills/.drafts/ — candidate skills awaiting promotion
  • opportunities/ — opportunity notes that resolved into something worth keeping permanently

Where Output Goes

  • New or updated entries → wiki/<slug>.md
  • Skill promotions → move AgentStack/Skills/.drafts/<slug>.md to AgentStack/Skills/<slug>.md
  • Every consolidation pass logs its promote/discard decisions to Logs/wiki-consolidation.md — one line per item touched, including why something was discarded, not just what was promoted

Promotion Rubric

Carried over from hermes-harness-spec §7 — still marked unconfirmed there, so treat this as provisional until that spec's open question is resolved:

Carry forward: anything that recurred ≥2×, anything still unresolved but important, anything that changed vault structure (new folder/agent/integration). Drop: routine, one-off, "nothing to report" entries.

Don't invent a different rubric here — if this one feels wrong in practice, that's a signal to go fix it in the spec, not to quietly diverge.

Entry Frontmatter

---
title: "..."
tags: [wiki, ...]
source: consolidated
graduated_from:
  - <path to originating log/opportunity/draft>
created: YYYY-MM-DD
tier: wiki
---

Body: plain-language explanation of the concept/pattern, one line on why it graduated, links to the originating material, and a ## Related section per the vault-wide rule in README.

Prior Art

llm_wiki (github.com/nashsu/llm_wiki) is the reference point that motivated this pattern — an LLM-maintained wiki concept. This folder is a from-scratch design fit to this vault's own hermes pipeline, not a port of that repo.

Hermes Wiki