KG Studio

KG Studio is Fontana’s Knowledge Graph workspace UI: a VFS secondary sidebar for namespaces and source files, plus selection cards whose tabs host linked views with shared selection. Select a namespace, folder, or file in the sidebar to open its card. Select an entity, a document, or a chunk in any view, and every other open view focuses on it. Each overlay gets the visual idiom that actually fits it: trees, sequences, and similarity fields are different shapes of data and deserve different renderers.

Workspace chrome

• Secondary sidebar: browse namespaces, folders, and files; create namespaces; upload, rename, move, and delete sources (same unified filesystem pattern as Skills). Queued, processing, and failed files show Q, amber spinner, or F markers on the Knowledge Graph title, namespace, folder, and file rows. A pinned Search row opens the Search workspace. Your browser tab for this page is Knowledge Graph | Fontana AI.
• Enabled / Disabled: each namespace, folder, and file card header has a named toggle (Enabled / Disabled on the track). Disabled rows stay in the sidebar, grayed out. While a parent is disabled, descendant toggles stay locked off; their own flags are unchanged and apply again when you re-enable the parent. New PARSE, INDEX, NER and EMBED jobs do not enqueue for effectively disabled files. Re-enable does not auto-reprocess. Graph search, agent Knowledge Graph tools, MCP file lists, and @-mentions skip disabled content; Studio still lists the grayed rows.
• Delete a namespace: from the namespace menu, choose Delete namespace. The namespace leaves the sidebar immediately. Fontana deletes every file inside it. You cannot recreate that name until cleanup finishes. The menu does not include a second folder Delete.
• Search: you type a query at the bottom of the page. A Scope line above the prompt shows the current sidebar selection (all namespaces, one namespace, or a folder). Four columns (Vector, Full-text, Related, Entities) fill independently.
• Selection cards: amber card with an actions menu, header, and content tabs. Namespace and folder cards open Graphs, Editor, Status, and Config. File cards open Graphs, Editor, and Status — the ontology review is scoped to a namespace, so a file has no agent tab and no settings of its own. Graphs hosts the namespace’s one graph, controlled by visibility toggles. Editor hosts source, entity triples, and ontology editing. On stored text files you can type in Raw and Save; reconstructed office markdown stays read-only. For parsed office files (xlsx, pdf, docx), the Source tab preview is reconstructed markdown from lexical chunks (outline headings plus covering chunk text), not the binary blob. File cards also keep Document tree and Reader on the source workspace.
• Processing status: each card header shows current status (Queued, Processing, Processed, Failed, or Idle for files; rollups for folders and namespaces) plus readiness chevrons (PARSE → INDEX → NER → EMBED).

Views

Graphs tab

The Graphs tab shows one graph of the namespace. A narrow column of toggles on the left of the canvas chooses which kinds of node it shows; each toggle is the kind’s icon with a count next to it.

Toggle	Shows
Namespace	The namespace itself, the root of the tree.
Folders	Your folders, each inside its parent.
Files	Your files, each inside its folder.
Page index	Each document’s section outline (PageIndex).
Chunks	The chunks the AI reads and cites, each under the section that covers it.
Entities	Extracted entities.
Entity types	The published types of your ontology.
Communities	Groups of entities that link to each other more than to the rest, each named after its best-connected members. Available while Entities are shown.

The count next to a toggle is how many nodes of that kind the namespace holds under your current selection, whether the toggle is on or off, so you know what switching it on would draw. Communities show a count once they have been computed, while their toggle is on. A sentence under the canvas says what you are looking at, for example “Entities grouped by type: 1,817 types, 7,115 typed entities.”

Links follow from the kinds you show. There is nothing to switch on for them:

• Containment: every node links to the nearest shown level above it (namespace, folders, files, page index, chunks). Hide a level and the next one down links straight to the one above, so with Files and Chunks on and Page index off, chunks hang under their files.
• Mentions: chunks link to the entities they name; with Chunks off, files link to the entities their chunks name.
• Types and communities: each entity links to its type and to its community. With Entities off, entity types hang under the namespace; entities hang under the namespace only while nothing between them (folders, files, sections, chunks, types) is shown.
• Relations: the extracted relationships between entities are always drawn between the entities you show, named on the link.
• Similarity: files whose whole-file embeddings are close link with their score, while Files are on and Folders are off, so the files show how they relate instead of where they sit.

Entities that share a sentence are not drawn as links; that co-occurrence weighs the communities instead.

Switching a toggle changes the picture at once: the whole graph of the namespace loads once, filtered by your permissions, and stays in your browser, so a toggle never fetches anything. While a big namespace arrives the graph and its counts fill in every second or so, and you can keep working with what is already there. A toggle never moves your view: your pan and zoom stay exactly where you left them.

As of is a day slider under the toggles. It runs from the earliest date your documents carry to today, with those dates shown under it; the right end is today, which means nothing dims. Drag it back to see the graph as it stood on that day.

Outside selection: Dim | Hide appears while a folder or a file is selected and decides what happens to everything outside it.

The graph is a force graph: every pair of nodes repels, every link pulls, and gravity keeps it together. It lays out in your browser and settles in front of you. A graph of a million nodes lays out gradually: the picture appears within seconds and keeps settling while the rest is placed, and nodes not yet placed are not drawn. The view opens fully zoomed out and follows the graph as it fills in, until you pan or zoom; after that it stays where you put it. Use pause and play in the corner of the canvas to stop or resume the simulation. Layout tuning in the Controls dock tunes the force graph live: repulsion, link pull per link class, gravity and flatness.

Everything is laid out in your browser from the namespace’s graph data, which Fontana streams to you already filtered by your permissions: you only ever see, count and group what you may read. While it opens you see Connecting, then Fetching nodes, then Building the graph; when the namespace changes, the canvas follows. The graph is built and laid out beside the page, so it stays usable while a big namespace arrives; when something goes wrong you get a message with Retry rather than a blank canvas. Nodes use the same kind glyphs as the rest of Flow: closed book for a namespace, folder for a folder, file-type badge for a file, a sky triangle for a page-index section, a small slate square for a chunk, plus entity, type and community stamps. Disabled namespaces, folders and files stay on the canvas at reduced opacity; entity stamps gray when no enabled chunk still mentions them. Hover shows the kind and name. Click a node to select it and open the Controls dock: type, name, and Connected to with the connected nodes and their kind icons. Click a neighbour to select it; double-click a namespace, folder, file or section (in the graph or in Connected to) to open its page. Zoom in until labels appear; relationship names and similarity scores label their links. Overlapping stamps and edges get brighter in dark mode and darker in light mode, and you can pan until any node sits in the middle of the canvas.

Search

You open Search from the Knowledge Graph sidebar (/kg?view=search). Four columns fill independently: Vector similarity, full-text chunks, related graph-expand hits, and entity name or embedding matches. Each column has a short footer that explains how those results are fetched. You submit from the bottom prompt. A Scope line above that prompt shows the current selection: all namespaces, one namespace, or a folder. Changing the sidebar selection updates that scope.

Editor and operator views

View	Overlay	Idiom	What you see
Source (stored text)	Stored VFS blob	Preview, Raw, Data, Chunks	On a file card Editor, you edit stored text files (markdown, JSON, and other explorer-text types) in Raw when you have Knowledge Graph write permission. Save on the file card writes the blob and schedules reprocessing. JSON Data shares that buffer. Parsed office files (xlsx, pdf, docx) stay read-only reconstructed markdown. Leaving the file or switching to Graphs while dirty uses the same Unsaved changes dialog as the rest of Flow.
Document tree	Structural (PageIndex)	Collapsible tree	On a selected file, the structure-lane outline: headings for documents (including .xlsx sheet names from anydoc markdown), rows and columns for csv/tsv, modules and classes for code. Click a node to see its covering chunks.
Reader	Lexical	Annotated document reader	Markdown rendering with chunk boundaries, mention highlights color-coded by extraction method, and next-chunk navigation. This is the click-through target for every path citation. The Source tab uses the same chunk hydrate path to rebuild the document preview for binary office files.
Ontology studio	Schema	Editor, Standards, Review	Entity and relationship forms. Standards mode: LinkML / SKOS / OWL import and LinkML / Fontana JSON / JSON-LD context export. Review mode: draft-versus-published diff, proposal inbox, evolution policy.
Status	All lanes	Operator dashboard	Structure, NER and Vector lane progress per namespace, failed jobs with error text, bulk reprocess, per-file actions (reprocess, skip), and forecast-versus-actual cost.

Code corpora reuse the same views

A code namespace’s Document tree becomes a module and class hierarchy, its Reader becomes source with definition and reference highlights, and its entities become an import and call graph, all from the same views and the same algorithmic extraction described in Code and mixed corpora.

Spreadsheets reuse the same views

A csv or tsv file’s Document tree (and its page index on the Graphs tab) is a rows branch, one leaf per data row titled from column 0, and a columns branch, one leaf per header from row 0. Empty keys fall back to row N / column N. An xlsx workbook is parsed as a document: anydoc converts each sheet to a markdown heading plus a GFM table, so the tree follows those headings rather than a synthetic rows/columns grid. Re-run PARSE/INDEX on xlsx files ingested before this document route existed.

Query-scoped rendering

Search and editor overlays stay query-scoped (a seed plus a bounded number of hops, top-K by degree or score). The Graphs tab loads the namespace’s graph once, and Fontana never runs a graph query to show it: the graph comes from a cache of the namespace, filtered by your permissions as it streams, and your toggles choose what to draw from it.

Operator controls (Status tab)

Open Status for progress and failures. Open Config to set ingestion settings:

• Namespace Config: ontology agent, per-lane settings, entity recognition, ontology mining, evolution policy, embed profile, and budget cap. Info icons explain each control. The ontology agent is chosen once per namespace, where a review is scoped — there is no cascade to folders or files.
• Folder Config: open the folder card and set the Structure and Vector lanes for that folder. Clear the override to inherit the namespace again.
• Failures: the header N failed badge is files with failed processing status. Status Jobs by lane Error columns count jobs (one file can contribute several). File readiness Failed matches the file badge (failed status wins over a stale stage). Use Reprocess failed documents for a bounded bulk retry, or Reprocess / Stop on the file card (and the overflow menu) anywhere in Studio.
• Graph presets: the Presets box in the top-left corner picks a question rather than eight switches — Structural (how the corpus is organised), Semantic (how entities relate to one another), Ontology (how entities roll up into types), Vector (what is embedded and similar), and Provenance (which file a fact came from). Changing a switch by hand simply leaves no preset highlighted.
• Graph layout: your browser lays the graph out as a force graph, which keeps moving until it settles: use pause and play in the corner of the canvas to stop or resume it, and the Controls section for the forces.
• Orbit: the Orbit slider under Controls sets how far the graph turns about its vertical axis as the pointer crosses the canvas, so a nearly flat layout shows its depth. Slide it to zero to switch orbiting off; pause holds the graph still.
• Namespace and folder focus: the Namespace switch under Nodes shows everything in the namespace, with a coloured region drawn behind it. Select a folder or a file in the sidebar and the same switch greys everything outside the selection instead; switch it off to leave only the selection, the folders above it, its files and what they mention.
• Communities: switch on Communities with Entities to group entities that link to each other more than to the rest. They are computed in your browser from the entities you can see, so what you may not read never shapes them, and the same graph always gives the same communities.
• As of: drag the day slider under the toggles to see the graph as it stood then; it runs over the dates your documents carry, and its right end is today. Documents not yet in force, or already superseded by their effective window, dim together with their sections, chunks and the entities only they mention; undated documents stay. Hover a file or select it to see its date or its effective window.
• Instant reopen: Fontana keeps the graph you load in your browser. When you come back, only what changed is fetched; a toggle draws from what is already there.
• Home tiles: the Knowledge Graph home view summarizes queued, failed, and processed counts per namespace and opens Status in one click.