Senter is the three-eyed owl: a self-documenting, self-extending multi-agent system. The wiki IS the coordination layer.
Built on Hermes Agent by Nous Research. Topics are miniature GOOP instances.
SENTER.mdis the language/context layer; Senter Agent is the interpreter and orchestrator.
Agent Wiki organizes a multi-agent AI fleet as a well-organized markdown vault. Every topic you care about gets its own directory containing the full stack:
- Context — what the system understands about your goal
- Loops — cron jobs and workflows that run over time
- Agents — AI profiles that do the work
- Skills — reusable procedures agents load on demand
You chat with Senter through an unnamed, low-intelligence, tool-free speech-to-speech auxiliary task. Senter watches conversations, comprehends what you want, and proposes the skills, agents, and workflows to make it happen. Progress flows back naturally in conversation.
Every part of the system is a markdown file you can edit. No config dashboards. No YAML wizards. Open the wiki, change what you want, and the system picks it up.
# Clone the wiki
git clone https://github.com/SouthpawIN/agent-wiki.git ~/.hermes/wiki
# Senter's front-end surface is an unnamed STS auxiliary task.
# The three-eyed owl is Senter's Herm TUI identity.
# Start the factory crons
hermes cron create "every 30m" --name "context-factory" --prompt "..."
hermes cron create "every 15m" --name "skills-factory" --prompt "..."
hermes cron create "every 15m" --name "agents-factory" --prompt "..."
hermes cron create "every 15m" --name "loops-factory" --prompt "..."
# Start chatting
hermes --tui→ Full setup: [[spec|Agent Wiki Specification]]
| Primitive | Factory | What It Is |
|---|---|---|
| Context | Context | Wiki pages — raw understanding from chat, structured into knowledge |
| Loops | Loops | Cron jobs, kanban tasks — execution that runs over time |
| Agents | Agents | Hermes profiles — named entities with personality, tools, and skills |
| Skills | Skills | SKILL.md bundles — reusable procedures loaded on demand |
Primitives nest: Context contains Loops which invoke Agents which load Skills.
From idea to working system — driven entirely by markdown reads and writes:
- Chat — You tell Senter about an idea
- Comprehend — Context reads the chat, writes wiki pages
- Create — Factories (Skills, Agents, Loops) build skills, agents, and loops
- Inject — Status flows back through Senter's conversational surface
Every user interest is a self-contained topic — its own directory with the full GOOP stack:
wiki/topics/<topic>/
├── README.md ← human dashboard
├── .system/ ← machine coordination (hidden)
│ ├── continuity.md ← raw understanding
│ ├── injections.md ← messages for Senter's conversational surface
│ └── queue.md ← pending factory work
├── skills/ ← skills for this topic
├── agents/ ← agents serving this topic
└── loops/ ← execution infrastructure
The .system/ prefix hides machine internals. You CAN open them — that's the debugger. But your default experience is clean markdown dashboards.
Four cron jobs run the system. Each watches the wiki for signals and spawns work:
| Factory | Watches | Produces | Uses |
|---|---|---|---|
| Context | Chat sessions | Wiki pages, queue items | session_search(), write_file() |
| Skills | [SKILLS] queue items |
SKILL.md files | delegate_task(), skill_manage() |
| Agents | [AGENTS] queue items |
Agent profiles | delegate_task(), hermes profile create |
| Loops | [LOOPS] queue items |
Cron jobs, kanban | delegate_task(), cronjob() |
All factories use the same 4-stage pipeline: Collect evidence → Generate candidates → Evaluate → Apply.
See everything at a glance. Edit anything directly:
| Catalog | Shows |
|---|---|
| [[catalogs/fleet-dashboard | Fleet Dashboard]] |
| [[catalogs/agent-roster | Agent Roster]] |
| [[catalogs/skill-registry | Skill Registry]] |
| [[catalogs/loop-registry | Loop Registry]] |
| [[catalogs/topic-index | Topic Index]] |
- Markdown is the API — human ↔ machine, machine ↔ machine
- The wiki is the system — no separate database or config dashboard
- User-editable everything — every understanding, queue item, status
- Dot-prefix for machine internals —
.system/is hidden but accessible - Topics are self-contained — each topic holds its own full GOOP stack
- Factories are thin — cron jobs that spawn one
delegate_task - Injections keep you in the loop — factories write to files, Senter's conversational surface reads them
- No self-edit — factories cannot modify themselves
The complete system status and user-test matrix are maintained in [[INTEGRATED_STATUS.md|INTEGRATED_STATUS.md]]. This distinguishes specified contracts, implemented artifacts, exercised paths, and blocked live integrations.
The unified live Wiki is ~/.hermes/wiki/. Its entry point is ~/.hermes/wiki/index.md; its conventions are in SCHEMA.md and operational history in log.md.
- [[spec|Agent Wiki Specification]] — full architecture, setup, comparison to GOOP v1
- [[goop-whitepaper|GOOP Whitepaper v1]] — the original architectural vision (July 2026)
- [[goop-nesting|GOOP Nesting]] — primitive nesting hierarchy
Built on Hermes Agent. Towards Self-Improvement.