Hillock’s maintainer claims its local neuro-symbolic engine provides durable agent memory while using less than 1.2GB of VRAM, potentially enabling private persistent agents on modest hardware.
state: expiredheat: lowuncertainty: highknownscott: lowagent-memory neuro-symbolic-systems local-inferenceroandejagerHillock
What is this?
Hillock is presented by maintainer roandejager as a local neuro-symbolic memory engine for persistent AI-agent state, reportedly using hyperdimensional computing and less than 1.2GB of VRAM. The claimed combination could support private, durable agents on modest local hardware rather than relying on hosted memory services. However, the supplied search snippets do not directly document Hillock, its maintainer, benchmarks, architecture, or VRAM measurement, so these remain maintainer claims rather than independently established results.
Why it matters to Scott
This is another unverified local persistent-memory claim in a development lane already tracked by the radar, notably Engrava’s local graph memory, Awareness Local, and Sillage’s compact memory layer. It touches Scott’s durable-external-state and local graph-memory work, but the supplied evidence does not establish architecture, benchmarks, or the sub-1.2GB VRAM result strongly enough to change what he builds or argues.
ip:concept.durable-external-stateip:concept.three-substratesdev:concept.llm-navigated-wikidev:concept.hardware-aware-local-inferencedev:project.openclawradar:engrava-local-graph-agent-memoryradar:awareness-local-agent-memoryradar:sillage-compact-model-memoryradar:concept.agent-memoryradar:concept.local-inferenceradar:concept.memory-efficiency
queries asked of Scott's wikis
- durable agent memory architecture
- agent-maintained wikis versus vector memory
- neuro-symbolic memory for coding agents
- local-first private agent state
- hyperdimensional computing for memory
- resource-efficient local agent infrastructure
Measured heat
no measured readings yet — the hourly heat pass fills this in
How the heat travelled
no chain yet — the hourly chain pass fills this in
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-09-01T18:51:27Z
No validation, technical detail, adoption, or implementation evidence arrived after the maintainer’s initial claim. The episode has faded below standalone tracking and can be reopened if reproducible benchmarks or independent use emerge.
2026-08-30T18:32:49Z
Re-observation adds no evidence beyond the maintainer’s original release and resource claim; without benchmarks, architecture details, adoption, or independent testing, the case remains an unverified implementation in a crowded local-memory lane.
2026-08-30T18:28:26Z
grounded: known/low — This is another unverified local persistent-memory claim in a development lane already tracked by the radar, notably Engrava’s local graph memory, Awareness Loc
2026-08-30T18:25:00Z
case created — The linked first-party repository is a concrete implementation addressing durable agent memory under a specific local-resource constraint.
Decision trace
- 09-02 04:51expireNo validation, technical detail, adoption, or implementation evidence arrived after the maintainer’s initial claim. The episode has faded below standalone tracking and can be reopened if reproducible
- 09-02 04:51alert_silentThe only change is staleness, not a consequential development; the unverified resource and durability claims remain unchanged and can wait unless new testing or adoption appears.
- 09-02 04:51alert_routeThe only change is staleness, not a consequential development; the unverified resource and durability claims remain unchanged and can wait unless new testing or adoption appears.
- 08-31 09:21sensor_dirtyengagement_update
- 08-31 04:32repriceRe-observation adds no evidence beyond the maintainer’s original release and resource claim; without benchmarks, architecture details, adoption, or independent testing, the case remains an unverified
- 08-31 04:32alert_silentNothing consequential changed: engagement is flat and no independent validation or technical artifact was added, so this can wait for evidence of reproducibility, adoption, or measured performance.
- 08-31 04:32alert_routeNothing consequential changed: engagement is flat and no independent validation or technical artifact was added, so this can wait for evidence of reproducibility, adoption, or measured performance.
- 08-31 04:31alert_silentThe GitHub/Show HN appearance establishes that Hillock has been publicly presented, but the only supplied evidence repeats the maintainer’s sub-1.2GB VRAM claim without architecture details, benchmark
- 08-31 04:31alert_routeThe GitHub/Show HN appearance establishes that Hillock has been publicly presented, but the only supplied evidence repeats the maintainer’s sub-1.2GB VRAM claim without architecture details, benchmark
- 08-31 04:28groundThis is another unverified local persistent-memory claim in a development lane already tracked by the radar, notably Engrava’s local graph memory, Awareness Local, and Sillage’s compact memory layer.
- 08-31 04:25createThe linked first-party repository is a concrete implementation addressing durable agent memory under a specific local-resource constraint.