Graphify
shippedPaste in code, docs, SQL, or a PDF and watch a deterministic parser turn it into a queryable knowledge graph, live in the browser.
Why this matters
You paste in a chunk of code, a document, a database schema, even a PDF, and Graphify draws a map of it — boxes for the important pieces (functions, tables, sections) and lines showing how they connect — right there on the page. The key word is 'deterministic': it's not an AI *guessing* at how things relate based on a vague sense of similarity, the way a lot of AI search tools work today; it's a predictable parser that reads the actual structure and draws exactly what's there, so the same input always produces the same, trustworthy map. That distinction matters more than it sounds — a lot of 'AI understands your codebase' tools are really approximate pattern-matching, and this is a small, honest demonstration of the more reliable alternative: genuinely parsing structure instead of statistically guessing at it.
Other ways this idea or technique could be used
- Onboarding: a new engineer pastes in an unfamiliar codebase and gets an instant visual map instead of reading files blind for a week.
- Contract or legal-document review: turn a long agreement into a graph of who owes what to whom, and where the dependencies are.
- Database migration planning: paste a schema and see every foreign-key relationship as a graph before touching anything.
- A study tool: paste lecture notes or a textbook chapter and get a concept map instead of a linear outline.
Approach
A single index.html with inline CSS and JS, no build step and no external libraries, so there is nothing to fetch and nothing that can 404. The user picks a mode (SQL, code, or text), pastes or loads a bundled example, and clicks Parse; three small deterministic extractors turn CREATE TABLE/FOREIGN KEY statements, function-definition/function-call pairs, or capitalized-phrase co-occurrence into a plain nodes/edges adjacency list. The graph is laid out with a small hand-rolled force-directed simulation (a few dozen lines of physics: repulsion + spring edges + simple integration) and drawn as native SVG circles and lines, so there is no charting dependency to vendor or load at runtime. Clicking a node highlights its neighbors and lists them in a side panel; a text query box runs 'neighbors of <name>' against the same in-memory adjacency list. Everything — parsing, layout, querying, rendering — happens synchronously in the browser tab with zero network calls after page load, which is what keeps the 'queryable knowledge graph' claim honest rather than decorative.
The source post
https://x.com/konig0000/status/2102030246468005922
Scoring
Pick
| surprise | 3 |
|---|---|
| demonstrability | 4 |
| self_containedness | 5 |
| honesty | 4 |
Atreyu's note for tonight ('Cool idea I like that one more build another') doesn't name a specific candidate or reference a prior build closely enough to identify which idea he meant, so it couldn't be honored directly — flagging that rather than guessing. Of the five scouted candidates, Graphify is the only one that's actually a single deployable web artifact: paste text in, get a graph out, click nodes to query it, no account or dataset required, and nothing about the demo is faked since the parsing is deterministic rather than an LLM call pretending to understand the input. RuView needs live Wi-Fi CSI hardware, RVC needs trained voice models and real-time audio infra, Agno and future-agi are backend frameworks/platforms that need a paid LLM API and persistent infrastructure to show anything real — none of them survive the single-artifact or self-containedness bar the way Graphify does.
Review
| shipped | 5 |
|---|---|
| honest | 5 |
| worth_it | 3 |
| efficient | 4 |
No change: the gate passed on the first attempt, the artifact is honest about what it does and doesn't do, and NOTES.md's one snag (Playwright/Chromium screenshot checks blocked by the sandbox's macOS MachPortRendezvous restriction) is a same-night environment limitation the build already worked around via direct Node checks, not a repeated failure pattern in evidence here.
Cost
| total | $0.1327 |
|---|---|
| xai | $0.1327 |
What it looked at
no scouted candidates recorded for this night
Also considered
Gate
| pass | project directory exists — /Users/artax/code/_nightly/2026-09-23-3/project |
|---|---|
| pass | no build step needed — static project |
| pass | build output with index.html — /Users/artax/code/_nightly/2026-09-23-3/project |
| pass | index.html is a document — 17280 bytes |
| pass | local asset references resolve |
| pass | page loads without console errors |
Stages
| scout | grok · ok · 24.2s |
|---|---|
| pick | claude · ok · 37.6s |
| plan | claude · ok · 39.0s |
| build | codex · ok · 248.3s |
| gate | local · ok · 3.3s |
| publish | local · ok · 13.7s |
| review | claude · ok · 37.7s |
Notes
Omitted for lack of
None. All planned capabilities run locally in the browser without services, generated images, or external assets. Validation: JavaScript syntax, required element IDs, all three example parser outputs, SQL neighbor adjacency, finite force-layout coordinates, and absence of asset references passed direct Node checks. SQL yields 5 nodes / 4 edges; code yields 7 nodes / 6 edges. Browser interaction and screenshot checks were attempted using installed Playwright/Chromium but could not run: the filesystem sandbox's process restrictions denied Chromium's macOS MachPortRendezvous registration (`bootstrap_check_in: Permission denied`). Visual rendering is therefore not confirmed in this environment; the automated browser gate remains necessary.