Show HN: My public second brain – 660 notes, 15 years, open source Author here. ~660 notes published from a private Obsidian
vault of 8,360 (3M words). Started in OneNote around 2011,
moved to Obsidian in 2021 [1], imported everything with a
Python script [2]. Notes are compounding over time, and that is where my writing comes
from. The Semantic Layer note started in 2022, became a
four-part blog series, then a chapter of my book. Materialized
Views, One Big Table, dbt and OLAP were separate notes written
years apart. I only later noticed they were the same pattern,
and that became another chapter. Publishing: add #publish to a note, run `make deploy`.
Quartz + Hugo, rsync to my own server [3]. Code [4].
Semantic search over the graph [5]. [1] https://ift.tt/W2Lufl0
[2] https://ift.tt/bhrLXnj...
[3] https://ift.tt/2vg3Y5P
[4] https://ift.tt/aNS2Enf
[5] https://explore.ssp.sh https://ift.tt/hOyKEJT August 3, 2026 at 01:12AM
Show HN: Schema-backed, Git-based structured state for agentic systems I looked into how to store agentic state in a) a structured way that b) runs without any dedicated MCP memory/state servers and where I can get c) a clear diff-able audit trail of all state changes over time. Nothing that I could find fit the bill. In https://ift.tt/ZwiTzQX , I demo an implementation that fulfills these requirements by combining Claude agents with my previously published Commitspark library and its entirely Git-backed GraphQL API. In the demo, two independent Claude agents are simulated that contribute to a task tracker. A third agent reviews any task changes and rolls back obviously bad ones. A full demo transcript is included in the README, including the agents' raw tool calls. Task agent access to data happens via a small MCP server that exposes two Commitspark APIs (GraphQL API, schema API). These agents can then fetch the schema and author their own GraphQL calls, with GraphQL automatically enforcing written data is schema-conformant. The validator agent additionally has access to basic git functionality to view diffs and revert commits. I'm looking for feedback specifically on: whether schema validation on shared agent state is a problem people actually have, or whether loosely-typed JSON + retries is good enough in practice. July 31, 2026 at 11:50PM
Show HN: A little physical breakout clone Idea: How about a 5 minute game I can play in my browser and it's actually fun to play. Controls: Mouse or keyboard (left/right, left alt/right alt or A/D), space and esc are pause toggle. Page up / Page Down are next or previous level (if already unlocked). Cheats: Z toggles zapper, M toggles magnets. Debug stuff: I, P, E keys are toggles for various stuff (E lets you change some aspects of physics engine). Game is maybe playable on mobile devices, there is a menu on top right, and then click the circle to select type of control. Physical engine is decoupled from refresh rate and runs at 240 Hz. Fully vibe coded (deepseek, chatgpt), levels are human made with some amount of love. https://brontosaurusrex.github.io/physical/v7/ July 31, 2026 at 08:13PM
संदेश
