Role
Lets short commands become sourced, validated actions while the vault remains the source of truth.
Component / Interfaces
Agent interfaces
The access layer on top of the vault: Hermes, skills, Telegram, repo tools, browser tools, and scheduled jobs that turn the vault into an operational cockpit.
Contains
- Hermes command bus
- Skills as procedural memory
- Telegram text/voice capture
- Repo/web/calendar/email tools that write back with provenance
Interfaces
- Reads vault context, acts through tools, writes back via workflow rules
- Routes reusable work through /skills/
- Keeps session/memory/fact stores as cache unless mirrored
Maintenance rule
Interfaces may be fast and conversational, but durable changes still need provenance and vault writeback.
Proof signal
A command can be traced from Telegram/session input to vault context, repo output, or an explicit blocker.
Failure mode: If interfaces become the source of truth, knowledge fragments across chats and tool state.