Local-first 🧠memory for Hermes Agent that lives in your Obsidian vault and remembers project context. Nightly 😴 dream passes turn repeat corrections into confirmed preferences with measurable confidence. Adapters ship for Claude Code, Codex, and OpenClaw, with an MCP server for anything else.
remote-log-reads Specification
Purpose
What a caller below local reach (a remote MCP client) may read of the operational log of a machine whose brain lives in the store.
Requirements
Requirement: Private log events are withheld below local reach
A reader that renders log events to a caller below local reach SHALL
withhold every event the store holds in its private partition, whatever
the event names, and SHALL show it to a local caller. A day whose every
event is withheld SHALL read as a day with no events, the same answer a
day that was never logged gives.
Scenario: A remote caller reads a day with a private event
- GIVEN a switched machine with one shared and one private log event on the same day
- WHEN a remote caller reads
osb://log/<that day> - THEN the page shows the shared event and not the private one
- AND a local caller reading the same day sees both
Scenario: A remote caller reads a day with only private events
- GIVEN a switched machine whose only log event of a day is private
- WHEN a remote caller reads
osb://log/<that day> - THEN the read fails exactly as for a day with no log events
Requirement: Every reader with a remote surface withholds private log events
Every MCP tool and resource that renders log events, or text derived from
them, to a caller below local reach SHALL withhold the events the store
holds in its private partition, whatever they name: the timeline
analytics, the daily, weekly, monthly, today and morning briefs, idea
discovery, idea lineage, agent provenance, backlinks and the note write
logs. A local caller SHALL see them as before.
Scenario: A private note in the remote timeline and briefs
- GIVEN a switched machine with one shared note event and one private note event that names nothing, both inside the window
- WHEN a remote caller reads
brain_analytics(timeline) andbrain_brief(daily, weekly, morning) - THEN each answer carries the shared note's text and not the private note's text
- AND a local caller's answers carry both
Scenario: Agent provenance below local reach
- GIVEN a switched machine where agent
secret-agentwrote only one private log event - WHEN a remote caller runs
brain_agent_queryorbrain_agent_diff - THEN neither the contribution nor the agent appears, and the counts read as if the event did not exist
Scenario: Backlinks from a private event
- GIVEN a switched machine where the only reference to a shared preference is a private log event
- WHEN a remote caller reads
osb://backlinks/<that preference>orbrain_backlinks - THEN the answer lists no backlink from the log and its count is 0
Scenario: Link-derived answers from a private event
- GIVEN the same machine, a shared MOC note that links that preference, and a second private log event that links an artifact id with no file
- WHEN a remote caller reads
brain_analytics(concept synthesis) of the preference,brain_moc_auditof the MOC note,brain_doctor, or thebrain_doctorrepair preview - THEN no answer lists or counts a reference from either private event, and no broken-backlink finding names the missing id
- AND a local caller's answers list and count both
Scenario: Doctor evidence lints from a private event
- GIVEN a switched machine with a private
apply-evidenceevent whose artifact names no file and carries a range that does not parse - WHEN a remote caller reads
brain_doctor - THEN no
orphan-evidenceormalformed-evidence-rangefinding quotes the event's time or artifact - AND a local caller's doctor reports both findings for it
Scenario: A note write in a private operation
- GIVEN a switched machine where a shared note was written inside a private operation, so its note-write event is private
- WHEN a remote caller runs
brain_writesorbrain_write_destinations - THEN the write is not listed and not counted
- AND the revert plan
brain_writesreturns for that note's path lists no write from the private operation
Requirement: Counts and timestamps below local reach ignore private log events
These numbers and timestamps, derived from log events and shown to a caller below local reach, SHALL be computed as if the withheld events did not exist (a preference's stored confidence and status are not among them): most-applied counts and order, the last dream and last apply-evidence times, the count of log days, the maintenance overdue flag, the memory cost meter, the token footprint of the log, and the stale counts. Every private event, counted or rendered, stays visible to a local caller.
Scenario: Most-applied counts
- GIVEN a switched machine with a shared confirmed preference that has
one shared and two private
appliedevidence events in the window - WHEN a remote caller reads
brain_context,osb://activeorosb://digest/latest - THEN the preference's applied count reads 1
- AND a local caller reads 3
Scenario: Status timestamps
- GIVEN a switched machine whose newest apply-evidence event and newest dream event are private
- WHEN a remote caller reads
second_brain_statusorosb://status - THEN the last apply-evidence time and the last dream time are the newest shared ones, or absent when there is none
Scenario: Maintenance actions from the log footprint
- GIVEN a switched machine whose token footprint crosses the warning threshold only with a private event's text counted
- WHEN a remote caller reads
brain_doctor,osb://digest/latest, orbrain_brief(digest, operator) - THEN no answer carries the token-footprint maintenance action
- AND a local caller's answers carry it
Scenario: Cost meter
- GIVEN a switched machine with one shared and one private memory write in the window
- WHEN a remote caller asks
brain_recall_telemetryfor the cost meter - THEN the meter counts one write
Requirement: Preference mode of brain_query applies the reference rule
brain_query in preference mode SHALL return, to a caller below local
reach, only the evidence events its sibling modes would return: no
private event, and no event naming a record the caller cannot read. The
result count it records in recall telemetry SHALL be the count it
returned.
Scenario: Private and unreadable evidence
- GIVEN a switched machine with a shared preference whose evidence is one shared event, one private event, and one shared event that names a page reserved against remote reads
- WHEN a remote caller runs
brain_querywith that preference - THEN the evidence holds only the first event
- AND the recall telemetry row of the call counts one result
Requirement: A new log reader is classified before it ships
Every module that reads store log events SHALL be classified as one that filters for a remote caller, one that serves only local callers, or a computation that must see every event, with its reason; a module that reads log events and carries no classification SHALL fail the build's test suite, naming the module.
Scenario: An unclassified reader
- WHEN a module starts calling a store log reader and no classification names it
- THEN the test suite fails and names the module