Screen reference — the free portal

A screen-by-screen reference for the free portal (regixo open): each screen, what it’s for, and the part of it you act on. Use it to look one thing up. To be walked through the free portal as a lived session, start with the walkthrough Your first session →.

The pictures below are cropped from the running product — the screen’s masthead and nav so you can find it in your own Regixo, then the one region that screen exists to do. Everything else on each screen is described in the text.

$ regixo open

Run it in a terminal of its own and leave it there — the portal is that command, so the terminal stays busy for as long as you want the portal up. Don’t ask a coding agent to run it: a portal your agent starts belongs to its session, so you can’t stop or restart it, and it dies when the agent moves on. Why →

It opens http://localhost:4319 in your browser. It runs on your machine, binds to localhost only, and needs no login — there’s nothing to sign into.

Getting around

A masthead (“Regixo · data catalog · free & local”) sits over a nav with one flat link and three dropdowns:

• Overview — the home screen.
• Catalog ▾ — Map · Glossary · What changed.
• Compliance ▾ — Record (RoPA) · DORA register · Processor record · Evidence bundle. DORA register appears when DORA scope is on, and Processor record when you have declared processor scope (actsAs in regixo.yml) — see The processor record. (Hidden in catalog-only mode.)
• Help ▾ — Commands · Settings · Agents (MCP) · Guide.

The screen you’re on shows a small “you’re here” marker. Nothing else sits under the header: Regixo shows no setup checklist and no progress meter, because it will not tick a step it cannot verify. What it can see — for example, how many datasets still have no description — it counts for you on the Overview, under “What you can do next.”

Overview

The home screen answers two questions. What have I got? — four stat tiles: N sources connected · N datasets mapped · N hold personal data · special category · Art. 9. And what happens next? — the draft card: from the same map Regixo has already started your GDPR record, and this is where you hand it over.

Above the tiles sits a coverage banner; below the card, a “What you can do next” section that counts real, verifiable work for you (for example, how many datasets still have no description). When a source’s last scan ages past the warn threshold (30 days, loud at 90 — configurable in regixo.yml), Overview and Map carry an honest staleness banner instead: “This map may be out of date”, listing each overdue source with its age and pointing at regixo watch.

You can do: click a stat tile to drill into the filtered Map, use Browse the data map →, and take the next step from a say / run panel (regixo describe, regixo add, regixo watch). There is no search box here — search lives on the Map, once. Empty state: “No data mapped yet” with the regixo start to run.

Map — the data lens

The core screen (Catalog ▾ → Map), and the one place the free portal lets you write. It’s a workbench: a toolbar on top, then a rail and a pane that scroll independently. You browse in the rail — one collapsible fold per source, every dataset a row with its column count and a personal-data dot, “holds personal data” first. Above the folds (not shown here) sit a search box, a Source picker and the Personal data · Art. 9 · Art. 10 · Undescribed facets, each with a live count.

Before you pick anything, the pane carries an orientation line, a trust panel (Reached · Fresh · Confirmed · Sealed — the same verdict an agent gets from get_provenance) and a source-overview grid. Open a dataset and it switches to that dataset’s detail: what it is, its columns — each with the Correct control below — a description box, and a vertical-river lineage graph (upstream above, this dataset on the trunk, downstream below).

You can do — the Map is where the free portal’s write controls live. Correct is in the frame above; here is the whole set:

Prefer to ask instead of browse? Everything here is also readable by an AI agent — see With an AI agent.

Record (RoPA)

Compliance ▾ → Record (RoPA) — your GDPR Article 30 draft, always badged DRAFT. It is a list of activities. Each one names the tables it runs on, states what Regixo found in them, and says plainly what it cannot decide: the legal calls are marked needs you, never guessed. A 3-step progress block (Data mapped ✓ → Your part → Review & sign) sits in the “Where this stands” rail card.

Above the activity list sits Your part (its heading counts the questions still open — “three quick facts” in the picture below): the record captures ten things per activity — seven are legal calls your compliance team makes, and three are facts only the engineering side knows (how the data is protected, which outside services get a copy, whose data it is). You answer those once, here, and the answers travel with the record; per-activity exceptions are one disclosure away.

You can do: answer Your part (above), then hand the record off — with regixo invite, or without a terminal at all. The hand-off annex carries four controls:

• Make the invitation — the no-terminal upload path (the Invite screen below).
• “↓ Download the draft PDF” — the forwardable file.
• “Download the DORA register (HTML)” — when DORA scope is on.
• “See what they’ll get” — a preview of the claimed record.

Once forwarded, the rail flips to “✓ Forwarded — now it’s with your compliance team” with the live link. If your catalog moves on after you make the link, the annex says so plainly — “Your catalog has changed since you made this” — and a fresh invitation replaces the old one.

The legal calls stay read-only on this local free screen — filling and confirming happen on the forwarded compliance portal (or via regixo annotate). If a licence is present, an Unlock & sign card appears — the two questions set the plan and show the published price; paying and signing happen on the forwarded compliance portal.

Invite — before it leaves your machine

Record (RoPA) → Make the invitation. This is the upload that starts the hand-off, and the screen exists to show you the exact payload first. (regixo watch and regixo push also upload, and only when you run them.)

It opens with the headline “Before this leaves your machine”. If your own answers (“Your part”) are still blank it warns you — “a warning, not a gate”. The payload itself is a two-column ledger: What goes and What never goes.

You can do:

• Read the exact list, item by item (“See the exact list” — the same sentence regixo invite prints in the terminal before it asks, computed from the payload itself).
• Optionally type the recipient’s address (“Who is this for?” — it locks the record to them: only that address can become its admin, and it uploads exactly as typed).
• Then “Upload it and make the link” — or “Cancel — change nothing”.

A second warning covers re-inviting: a fresh invitation replaces the one before it (the old link stops working; everything the compliance team filled in carries over). Regixo emails nobody — it makes a link; sharing it is yours to do. Prefer to see the record they will see, first? regixo invite --no-upload then regixo serve-claim serves it locally.

DORA register

Compliance ▾ → DORA register (shown only when DORA scope is on). The screen is honest about how far a scanner can get: a progress meter — Regixo filled · you provided · partly · needs you — over the 15 sections, grouped A · Your company, B · Your contracts, C · Your IT suppliers, D · Your functions. Regixo part-fills the tables it can see from your sources (your IT providers, the services they run); contracts, branches and criticality it cannot see, and says so.

You can do: read any of the 15 tables, copy the fill commands (regixo dora import / set), and turn scope off. A scope gate at the top of the register says why the screen is showing at all (regixo.yml: dora: true) and offers “Not regulated? Turn it off →”; below the tables, a “Who fills in the rest” block gives the two honest ways forward — forward it, or import it yourself. The progress meter lives in the “Where this stands” rail card. Filling the cells and the sealed export happen on the compliance portal or the CLI. Out of scope, it’s a friendly gate: “DORA isn’t switched on for this project.”

What changed

Catalog ▾ → What changed. A dated timeline of every change to your map — added, removed, reclassified, described — newest first, each entry saying in one sentence what moved and what it means. It’s the browser twin of regixo log, filled by regixo start and regixo watch.

Above the entries: a summary line, filter pills and a count; below them, Load older ↓. A first scan shows a “Baseline created” card instead. If a signed record has since drifted, a gold re-sign banner appears with Review & re-sign →.

Glossary

Catalog ▾ → Glossary. Your shared business dictionary, browsable by an A–Z strip (letters with no terms are dimmed). Each term carries its status — ✓ confirmed, or suggested when an agent proposed it — and the datasets it touches as source-qualified chips (fintech-loans / borrowers), so two tables that share a name are never confused.

+ Add term opens the composer. Its “Link to datasets” field is not a flat list: at any real estate size that would be hundreds of look-alike rows (thirteen tables called users). It is a filterable picker of source folds — one fold per source, each row named source / table — with a tray of what you’ve ticked above it, so Save stays in reach.

You can do: search the dictionary, + Add term, Edit a term (Remove term lives inside the editor), and confirm one an agent suggested. Same store path as regixo glossary set/confirm; served read-only to agents.

Agents (MCP)

Help ▾ → Agents (MCP). The screen that connects an AI assistant to your catalog — the no-terminal way to do it. Step 1 is the whole job: pick your tool (Claude Desktop / Claude Code / Cursor / VS Code / Other) and press Copy snippet for the ready-made config — Claude Code takes a single claude mcp add … line instead. The note under it hands your agent the reading playbook (regixo mcp --skill). Step 2 — not shown here — is simply: restart the app and ask it something. Full walkthrough: With an AI agent.

{
  "mcpServers": {
    "regixo": {
      "command": "npx",
      "args": [
        "regixo",
        "mcp"
      ],
      "env": {
        "REGIXO_DATA": "/Users/you/app",
        "REGIXO_CONFIG": "/Users/you/app"
      }
    }
  }
}

Evidence bundle

Compliance ▾ → Evidence bundle. One machine-readable file that proves what your records say — the RoPA draft, the DORA register, the change log and the source list, with a real per-artifact sha256: fingerprint. You can do: ↓ Download, ↻ Regenerate. It’s a DRAFT bundle; the signed official bundle is the paid step. Twin of regixo evidence.

Settings

Help ▾ → Settings. Six sections down the side — Mode · Connections · DORA scope · Keep it current · Moving machines · About this install. The one that changes what Regixo is is Mode: two cards, not a radio — Full compliance tool ⇄ Data catalog only — each listing exactly what it turns on and off, with the current one marked. Moving to another machine is the numbered recipe for taking the install with you — “your install is four things; only the map rebuilds itself” — which pieces travel in git, and which one (your credentials) you carry by hand, every time.

The other four sections: Connections — a read-only inventory of every source, whether it was reachable at the last scan, what env var it reads (the name only, never the secret), and its regixo test / regixo sources remove commands; DORA scope — on/off; Keep it current — Regixo has no built-in scheduler, so it shows per-source last-scanned ages and a copy-ready GitHub Actions snippet (plus a cron fallback) to run regixo watch yourself; and About this install. The toggles write the same regixo.yml fields as regixo config.

Commands

Help ▾ → Commands. The click-to-copy map of every regixo command. It opens with “Run Regixo by talking to your coding agent.” — because in practice most engineers now run Regixo by saying what they want, and their agent runs the same command in the same project shell. So every action here is one command shown two ways: the sentence you say (say) and the terminal command (run). One switch at the top — Show: Sentence | Command — sets which one leads, and it remembers your choice across pages. Neither is hidden: the other is always one click away, and both are copyable.

Three commands deliberately have no sentence at all — regixo annotate set, regixo verify and regixo dora export. Confirming a legal field, signing a record and sealing the official register are a person’s acts, so the panel shows the command alone and says: “This one’s yours.”

Guide

Help ▾ → Guide. A short action plan — “What to do in Regixo” — that links each step to the screen or command that does it: the goal (get your first record to your compliance team), the labels you’ll meet (found · suggested · needs you), what happens after you send it, and what stays on your computer.