> ## Documentation Index > Fetch the complete documentation index at: https://docs.prbe.ai/llms.txt > Use this file to discover all available pages before exploring further. # Projects > The directory of work: kinds, the project page, the Metrics center, papers, subprojects and published pages. **Projects** opens on the [workspace canvas](/dashboard/overview.md#the-workspace-canvas): every project in the current workspace on one board. Turn the canvas off in **Settings** → **Preferences** to get the Projects list instead: the workspace digest, then one row per project with a **Details** column that shows its first chart or diagram, or its description when it has none. The list filters by kind and sorts by **Recently updated** or **Name A–Z**. Use the workspace switcher to browse elsewhere, or **All workspaces** to see everything. ## Kind decides the layout A project's kind is fundamental identity, declared at creation and not a reader preference — there is no relabel control. | Kind | Its Overview leads with | | - | - | | `training` | The Metrics center: experiment comparisons, tables and charts | | `evaluation` | The Metrics center | | `general` | The Metrics center | | `research` | Its papers, in the explorer and on the canvas | `evaluation` used to be called `inference`. Every such project was converted, and `inference` is still accepted on input as an alias that is stored as `evaluation`. An experiment is itself stored as a project of kind `experiment`, filed under its parent. > [!NOTE] > > Kind reaches the project page only. It never restructures an experiment or a run — anything type-specific inside an experiment is driven by that experiment's own data. ## The project page The header carries the project's name, kind, research tags and contributors. Below it sit the page tabs: **Overview**, then **Data**, **Subprojects**, **Integrations** and **Sessions** as they apply. **Data** appears once the project has recorded data, **Subprojects** once it has subprojects or references, and **Sessions** once a coding-agent session is attributed to it. **Overview** has three parts: **1. Explorer, on the left** The project's experiments with their runs, **Live runs** (running now) above **Project runs** (runs with no experiment), and on a `research` project its papers. **Filter…** matches experiments, runs and papers. Lists show 10 runs at a time; **Show more runs** reveals 10 more, and selecting an experiment shows all of its runs. **2. Center** The Metrics center, or the papers on a `research` project. Selecting an experiment or run in the explorer narrows the center to it. With the canvas on, an **Overview** / **Canvas** toggle switches the project scope to a board of its experiments and runs. **3. Context pane, on the right** **Summary**, **Notes** and **Files** for the project or the selected experiment; a selected run shows [its own tabs](/dashboard/experiments-runs.md#runs) here. The Summary is the project's or experiment's page, written by the recorders; an entity nobody has written up yet says "No summary yet." See [summaries](/tracking/summaries.md). When the center has nothing to show, the Summary moves into the center instead. ## The Metrics center `training`, `evaluation` and `general` projects share one Metrics center. Each experiment gets a collapsible section that compares its runs on shared charts, with its saved question above them. Runs with no experiment share a **Project runs** section before the experiments. * **Tables and charts an agent picked** (tables, metric grids, bar, scatter, heatmap, box, histogram and parallel charts) render inside their experiment's section, before its metric charts. Project-owned tables keep their own headings above the experiment sections. * **One search** above every section matches metric keys and reopens matching tables. * **The legend and the explorer's eye controls** hide and show runs across a section's charts. Hidden runs stay listed so you can bring them back. * **Show more runs**, at the bottom, reveals 50 more runs from the activity-sorted roster. An experiment section with nothing to chart and no tables is hidden until data arrives. A section whose read was cut short keeps what came back and names what it left out — it never reads as "no data". ## Papers On a `research` project, papers are listed in the Overview explorer, even before the project has experiments or runs. Selecting a paper opens it in the context pane: its summary, its source and repository links, its tags and its sharing action. An old `/papers/{id}` link opens the owning project with that paper selected. The **Canvas** view of a `research` project is one board of its papers. Each paper sits to the right of the earlier paper its first recorded link points to, so the board reads as a tree of how the reading went. Arrows are only links an agent or person recorded (`relates_to`, `discovered_via`, `informed_by`); hover one for its reason. Recording a paper is an act by whoever did the reading, so the dashboard has no add-paper form. See [Papers](/tracking/papers.md). ## Subprojects A phase of a bigger effort appears nested under its parent, on the **Subprojects** tab and as a compact box on the canvas. Attaching a subproject is an agent or CLI act, like recording a paper — the page shows the tree, it does not compose it. Projects can also **reference** each other laterally, for when a review informed a training run or two efforts share a method. References are listed on the same tab. ## Workspace digests Digests report what changed across recent projects, with prose describing the activity rather than a diff of row counts. They generate on a schedule and are available to every team. ## Published pages A project page can be published, which serves a read-only twin at a public URL: the Overview, its figures, and an attached repository README where one is configured. Published pages render panels and chips without any create, edit or delete control. > [!WARNING] > > Publishing is a deliberate act with a real blast radius — a published project page is reachable by anyone with the link. A private repository's README embedded in an Overview is served on that page too. ## Integrations The **Integrations** tab has a **GitHub** and a **Weights & Biases** panel. The GitHub panel lists the repositories attached to a project and reads their commit timeline **through** GitHub — nothing is mirrored, so attaching is cheap and detaching loses nothing. On an experiment, repositories are managed on the parent project. ```bash theme={null} probe project code list folding probe commits folding ``` The GitHub panel is behind a per-user gate on some accounts. **Connecting GitHub is not** — that is a knowledge source and is generally available, as is the published README read. See [GitHub](/integrations/github.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.