Explorer · runs entirely in your browser

Explore the knowledge.
Trace the code.

Browse the real bank wealth knowledge and generated code in one matched snapshot. Follow a knowledge node to its author declaration and code, then click a code line to trace back. Everything runs in your browser; query text and results are not sent to a server.

Source / anchors verified 2026-11-15 · F-30 · Snapshot scope · Bank source license

Snapshot & evidence

Checking the matching bank snapshot and downloaded bytes…

Original file bytes; file candidates and exact spans are different precision levels.

This browser reads a packaged, fixed snapshot—not your local bank generated/ or generated/current/. Displayed paths are relative to that snapshot. Which generated directory supplied it?

Snapshot scope · Source license

01

Browse the nodes

Search nodes by full ID or name, inspect their relationships, then follow verified author and code locations. Qualified aliases keep separate node IDs; matching names alone never establish identity.

Three graph representations, different scopes
Canonical graphstore
The legacy declaration graph fallback: 389 nodes / 413 edges, captured 2026-11-11 (F-03). This file alone does not provide code anchors. A published Graph / Code snapshot binds its own graph and project mappings under one manifest.
Project knowledge/anchor graph
Knowledge and generated-location mappings from a matching project and output. Code queries require that project's identities, precision and freshness.
Workshop project-view export
A browsing export that may be truncated: the 2026-11-06 snapshot contains 120 nodes / 183 edges from declared totals of 861 / 737 (F-17), not a complete copy of either database.

Literal, case-insensitive ID/name substring search (SQLite’s case folding is ASCII); kind and search combine. Filters never change the selected node. All nodes are reachable in pages of 40; each fresh-copy query is cancelled after 5 seconds. SQL drafts are never shared in node URLs.

Loading the node directory…

    Node inspector

    Select a node to inspect its stored record and incoming/outgoing relationships.

    Code locations load from the matching snapshot. An unavailable mapping is shown explicitly; no file paths or line numbers are guessed.

    Code links inspect this fixed snapshot. To verify your own current files, follow the Counter reverse-query tutorial with a matching local project.

    At most 80 edges per direction, 8192 UTF-8 bytes per displayed atom/provenance field, 512 KiB per response. Totals and truncation are explicit. Stored atoms are plain text, not executed or treated as verified generated output.

    Advanced · Query the Graph with SQL
    02

    The console

    Pick a preset (with the expected answer) or write your own SQL against nodes(id, kind, name, atom, extra) and edges(seq, from_id, relation, to_id). Schema is exactly what truthsrc graph --out produces.

    Pick a preset to begin

    Or write SQL below and hit Run. Everything executes against the in-memory copy of the bank graph.

    Disposable SQL sandbox

    Each run uses a fresh local copy. SQL is real; changes are discarded and cannot affect presets. Limits: 16 KiB SQL, 4 result sets, 200 rows per set, 32 columns, 8 KiB per cell, 512 KiB response; cancellation after 5 seconds. Later statements may not run after truncation.

    03

    Don’t trust us — rebuild it

    This graphstore is a derived snapshot, not the project knowledge/anchor database. First complete the guide’s tool setup in the same shell, then point BANK at your existing matched bank checkout. The output below must be a new file. Current-source counts can differ from this dated snapshot; count equality alone does not establish byte identity.

    : "${TRUTHSRC_CLI:?Complete the guide tool setup first}"
    : "${BANK:?Set BANK to your matched bank checkout absolute path}"
    cd "$BANK"
    node "$TRUTHSRC_CLI" graph --tree truth/bank-wealth --out my-copy.sqlite
    DEGRADE GRACEFULLY

    If the sqlite file fails to load (offline first visit, very old browser), the presets fall back to their documented expected answers so the page still teaches the query semantics.