Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji
reacted with thumbs down emoji
reacted with laugh emoji
reacted with hooray emoji
reacted with confused emoji
reacted with heart emoji
reacted with rocket emoji
reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
{{title}}
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
{{editor}}'s edit
{{editor}}'s edit
Uh oh!
There was an error while loading. Please reload this page.
I use Graphify a lot, and one thing I wanted to explore further was time — when did a node first show up, what came before what. Graphify already gives you the structure; I wanted to add a temporal layer on top of it.
Turns out your filesystem already tracks this: mtime, ctime, birthtime, even the parent directory's mtime. That's a timeline sitting there for free, no LLM call needed.
So I built graphify-temporal, a companion CLI that runs after a graphify build:
It stats the file behind each node, stamps file_mtime / file_birthtime / dir_mtime, and chains nodes with preceded_by edges — within a file by line order, and optionally across the whole project. It's idempotent, so you can re-run with different flags anytime.
Once the graph has timestamps, query and timeline let you filter and walk it by time — what changed since a date, oldest node in a file, gap stats across the project.
Repo: github.com/todotge/graphify-temporal