Views¶
Every view of the built-in navigation, by section, with its route, what it shows, its buttons and dialogs, and which of its actions are writes. A write goes through the write gate: admins only (for everyone else the button is disabled, with an Only admins may … tooltip, and the view says read only: only admins may change …), a confirm dialog first on a protected context, and an entry in Changes.
Most Trading and Infra views are built-in pages: JSON page specs shipped with the app
(src/pages/builtin/*.json) that render one browser component over declared data
sources. You can copy them in Config > Pages and build your own (see
Pages).
Common controls¶
The header¶
| Control | What it does |
|---|---|
| Virtufin logo | Goes to Home. |
| AI | Opens or closes the AI assistant panel (shown once a context is active). |
⚠ N |
The number of unread alerts (red when one is an error); click to open Alerts. Hidden when there are none. |
⛔ N halted |
The scenarios whose trading is halted (names in the tooltip). Hidden when none is. |
| Kill switch | Admins only: halts every scenario and cancels every open order (Scenario). |
| Context menu | The active context, its health dot, switching (Contexts). |
| Name, admin / read only, Log out | Who is signed in; Log in when signed out; no sign-in (dev) on a dev server without sign-in. |
Below the header: the tab bar (the top level of the navigation) and the sidebar (the entries of the chosen tab), as the representation profile draws them. Views stay alive while another is shown (filter, selection and scroll are kept); a context switch drops them. Notices (a failed action, an undo offer) appear as toasts for 8 s.
Tables¶
Every table is the same data grid (src/grid/DataGrid.vue):
| Input | Effect |
|---|---|
| Click a row | Selects it (the toolbar buttons act on the selected row). |
| Click a column header | Sorts by it; again reverses (▲/▼). |
| Drag a header's right edge | Resizes the column (remembered per table in this browser); double-click the edge resets it. |
| Double-click a cell | Shows its full value in a popover (cells are one line). |
↑ ↓ PgUp PgDn Home End |
Move the selection (the table must have focus: click it). |
Space |
Marks or unmarks the selected row (tables with a mark column: Workers, Connections). |
Enter |
Opens the selected row (its detail), where the view has one. |
Escape |
Closes the full-value popover; in a dialog, closes the dialog. |
Rows keep their selection, marks and scroll position while the data updates live.
The filter¶
Most tables have a filter line above them. It parses as you type; an invalid
expression is marked red, says why and filters nothing; Escape clears it; shown/total
counts the rows that pass.
- Whitespace-separated terms, all of which must hold; case-insensitive.
- A word matches if any of the row's word fields contains it.
field:patternmatches one field;-termmust not hold; quotes group words ("two words",value:"two words").- A pattern with
*or?is a glob over the whole field, any other a substring. - On plain tables the fields are the column headers in lower case, non-letters as
_(Target topic→target_topic,Tick size→tick_size). - Worker filter (Workers, Connections, EventStores): fields
name,id,type,status,topic,source,tag(tag:world=act); a word looks in name, id, topics and tags. - Value filter (States, Events): fields
name,kind,type,source,subject,value.
Home¶
Route / (and /home). The active context and its state (Context demo: up.), and the
list of the navigation's views this app has, as links. With no context active: No context
is active: pick one from the context menu.
Trading¶
Feeds¶
Route /trading/feeds. Built-in page feeds (FeedBrowser). The feed definitions
shared on the context: JSON documents (cfg.feed.<NAME>, listed in cfg.feed.index)
that name a market-data-devkit venue preset and the topics its WebSocketFeed workers
serve (see Connect a market-data feed).
Columns: status dot (green all of its feeds connected, yellow some connected or
connecting, red none), Name, State (connected, partly connected, disconnected),
Preset, World, Topics, Feeds, Msg/s, Latency p50/p90, Description. Feeds tagged
feedowner=<name> whose name has no definition are listed too, so they can be
disconnected.
| Control | What it does | Write |
|---|---|---|
New preset… |
Opens the editor with a new definition for the picked preset. | Saving is |
| Edit… (View… for non-admins) | Opens the definition in the JSON editor. | Saving is |
| Connect | Brings the definition's feeds to its topics (market-data-devkit feeds.resolve/apply, the definition's name as owner); a notice says how many feeds serve how many topics. |
yes |
| Disconnect | Deletes its feeds (asks first): the workers reading its topics get nothing until it is connected again. | yes |
| Delete… | Deletes the definition; refused while its feeds run (disconnect it first). Every client of the context loses it. | yes |
Detail (or Enter) |
Its state, validation errors, topics and each feed with its state, subscribed count, msg/s and id. | no |
The editor (New feed / Edit feed <name>) is a JSON text area validated as you type
against the feed-definition schema: name, description, preset,
world (default act), universe, pairs × families (× intervals) or topics,
reconnect (default true), secrets (references, never values), feed (further
WebSocketFeed config keys). It lists every error at its path, warnings (e.g. intervals
no family uses), and a preview: N topics on M feeds, each feed with its preset, world
and topics, and the plan's problems (unserved topics, over a venue limit). Save saves
the definition; Save and connect saves it and connects it. Renaming keeps the old
definition as well.
Instruments¶
Route /trading/instruments. Built-in page instruments (InstrumentBrowser). Every
instrument whose snapshot topic the api has seen (from the api's topic catalog, kept
current by sys.api.topic.catalog.added), any venue and world. Columns: World, Venue,
Pair, Tick size, Lot size, Updated (UTC); tick and lot size come from the saved instrument
(state service workmanager), then each snapshot. Filter e.g. venue:binance pair:BTC*.
Read only.
Order Book¶
Route /trading/orderbook. Built-in page orderbook (OrderBookBrowser). Pick a book in
the drop-down (Pick a book (N); every book the api has seen, the choice kept per
context). Shows mid, spread (and in bp), update id, age and whether the image is saved
or live; the ladder of the top 15 levels per side (Side, Price, Size, Depth bar,
Cumulative), redrawn at most every 250 ms. A Gap line appears when an update is
missing (waiting for the next book); after 10 s without any book: Nothing produced this
book in 10 s, and none is saved: does an order-book worker run for it? Read only.
Indicators¶
Route /trading/indicators. Built-in page indicators (IndicatorBrowser). Pick the
scenario and the indicator among the changed topics the api has seen (names from
@virtufin/indicator-devkit). One row per pair, columns by the value's shape (TradeFlow,
BookImbalance, a single value, else JSON), seeded from the saved values, then each
changed event. Open (or Enter) shows a pair's values received while shown, newest
first. Read only.
Portfolio¶
Route /trading/portfolio. Built-in page portfolio (PortfolioBrowser). Pick an account
among the account.snapshot topics seen. Balances (Asset, Free, Locked, Total; zero
balances hidden until show N zero balances is ticked) and Open orders (Symbol, Side,
Type, Qty, Filled, Price, Status, Time), from the saved account, then each change. After
10 s without data: does a portfolio worker run for it? Read only.
P&L¶
Route /trading/pnl. Built-in page pnl (PnlBrowser). The scenario picker (the scenario
this browser works in, see Scenario) and the scenario's P&L book
(sc.<S>.pnl.book): per symbol Qty, Avg cost, Mark, Unrealized, Realized, Fees, and a
total; read again on each P&L update. Without a book: No P&L book for <S>: does a P&L
worker run for it? Read only.
Risk¶
Route /trading/risk. Built-in page risk (RiskBrowser). The scenario picker and the
scenario's exposure per symbol: Symbol, Qty, Mark, Notional, Share, Limit, Status, and the
gross total (red when breached); from risk.exposure.update events, else from the P&L
book with the scenario's limits.
| Control | What it does | Write |
|---|---|---|
| Limits… | Risk limits of <S>: Max notional per symbol, Max gross notional (in the scenario's quote asset; empty is no limit). Save writes them to the scenario's entry. Shown and reported by the P&L worker, never enforced. |
yes |
Strategy¶
Route /trading/strategy. Built-in page strategy (StrategyBrowser over ListWorkers).
The atomic strategies (workers tagged type) and the composite ones
(cfg.strategy.<NAME>, {components}). Columns: Name, Kind, Detail, Status. Filter e.g.
kind:composite.
| Control | What it does | Write |
|---|---|---|
| New strategy worker… | The registry's New worker from the registry dialog (see Workers). | yes |
| Compose… | Compose a strategy: an upper-case Name (e.g. MOMENTUM_MIX) and at least two components picked in order; cycles are refused. Compose saves cfg.strategy.<NAME>. |
yes |
| Remove… | A composite: deletes its entry (its components stay). An atomic one: deletes its worker. Warns when other composites use it. | yes |
Scenario¶
Route /trading/scenario. Built-in page scenario (ScenarioBrowser). The scenario
registry (cfg.scenario.*). Columns: ID, Status (active, paused, archived,
deleted), Trading (halted or not, from sc.<S>.trading.halt; unreadable counts as
halted), Market, Portfolio, Strategy, Updated. The line above says which scenario this
browser is using ((real trading) for LIVE).
| Control | What it does | Write |
|---|---|---|
Use (or Enter) |
Makes the selected scenario the one this browser works in on this context (P&L and Risk follow it). | no |
| Add… | Add a scenario: ID (upper-case letters, digits, _, at most 32; not LIVE), Name, Market World and Universe (default act, ALL), Portfolio World, Strategy World and Strategy id. |
yes |
| Pause… / Resume | Sets the status paused (Its workers stop taking decisions until it is resumed.) or back to active. Not for LIVE, archived or deleted. |
yes |
| Halt trading… / Resume trading… | Sets or clears the scenario's trading halt: strategies withhold their orders and executors refuse them; open orders stay. | yes |
| Archive… | Status archived: registered, read only, trades no more. Not for LIVE. |
yes |
| Delete… | Irreversible: type the ID, then confirm again (Yes, delete it). Marked deleted, taken out of the index, every state key under sc.<S>. purged, then its entry deleted. Not for LIVE. |
yes |
LIVE can only be used and halted, and the app does not create it.
Kill switch (header, admins): finds the plan — the scenarios to halt (every one not
archived or deleted) and the running executors (found by their
sc.<S>.trading.order.submitted topic) — shows it, asks twice (Continue, then Yes,
stop trading now), then halts first and sends cancel-all to each executor second, with
a report per scenario and executor. Nothing resumes by itself. See
Scenarios: create, set status, halt and resume trading.
Infra¶
Workers¶
Route /infra/workers. Built-in page workers (WorkerBrowser over an invoke source of
workmanager ListWorkers and the worker lifecycle topic). The context's workers, kept
current from the WorkManager lifecycle topic (read again on a listing change, and every
2 s only while the subscription is down). Columns: mark, Name, Status, Type, Source,
Topics, Tags, Created, Id. The line above counts workers, marked ones and N with a newer
version. Filter with the worker filter, e.g. tag:world=act status:running.
| Control | What it does | Write |
|---|---|---|
| New… | New worker from the registry: see below. | yes |
| Start, Stop | The selected worker. | yes |
| Delete | The selected worker, asked first (Its code, config and state go; this cannot be undone.). | yes |
| Tag… | Tag <worker>: Key and Value; Set tag. An empty value removes the tag. A notice offers Undo for 10 s. |
yes |
| Upgrade… | Loads another version of its registry package (see below). | yes |
Detail (or Enter) |
Id, Status, Type, Code, Topics, Created, the last failure, Tags, Config, Secrets (references), Code history, Lifecycle since connecting. | no |
| Marked / All shown (N): Start, Stop, Delete, Upgrade | The bulk actions: on the marked workers, or with none marked on every worker the filter shows. A dialog lists them (Delete needs Yes, delete all N), then a report per worker (✓/✗ with the error). Upgrade loads each one's latest registry version. | yes |
New worker from the registry (New…; also New strategy worker… on Strategy): pick a
Worker (the registry is general-workers/workers.toml, shipped with the app; entries
that need a personal credential or a local source say (not in the web app)), its
Version (newest first, (latest)), Topics (comma-separated; templates such as
{pair} bind the config, the resolved list is shown as Subscribes to: …), the Config
form from the entry's schema (string, integer, number, boolean, enum; required fields
marked *; other properties named and skipped), an optional Reply topic, and Secret
references (names of secrets, never their values). A world config re-binds every
world-scoped topic. Create creates the worker tagged type and source, not
started.
Upgrade…: shows the package and version it runs and whether a newer one exists; pick a
Version ((running), (latest)) and Load <version>. The worker keeps its id,
topics, config, secrets and tags; a running worker stops, loads the new code and starts
again (its in-memory state starts fresh). A worker whose code is not a versioned registry
package has nothing to load.
Connections¶
Route /infra/connections. Built-in page connections (ConnectionBrowser over
ListWorkers, the lifecycle topic and wrk.websocketfeed.metrics). The WebSocketFeed
workers. Columns: status dot (green connected, yellow connecting or reconnecting or not
reported yet, red disconnected), State, Name, URL, Publishes to, Published, Msg/s, Latency
p50/p90 (⚠ with the reasons when it carries clock skew), Subscribed, Failures, Tags, Id.
| Control | What it does | Write |
|---|---|---|
| Connect… | Connect: Name, Preset (a market-data-devkit venue preset, or none: a bare URL), URL (wss://…; overrides the preset's), World (with a preset: act or hyp.<NAME>), Publish topic (optional), Reconnect when the connection drops, Secret references. The feed starts without topics and serves topics on request; Connect waits for it to report connected. |
yes |
| Publish… | Sets the topic it publishes to. | yes |
| Stop publishing | Stops publishing. | yes |
| Disconnect | Stops and deletes its feed worker, asked first: nothing reconnects, its tags and saved session go. | yes |
| Tag… | As on Workers. | yes |
| Refresh status | Asks the feed its status (a read-only worker command). |
no |
Detail (or Enter) |
State, latency and its doubts, recent p50, the raw status answer. | no |
| Marked / All shown (N): Stop publishing, Disconnect | Bulk, asked first (Disconnect needs Yes, delete all N feed workers), with a report. | yes |
Triggers¶
Route /infra/triggers. Built-in page triggers (TriggerBrowser). The context's
scheduled triggers from the api's Trigger service, read again on sys.api.trigger.scheduled
and sys.api.trigger.deleted. Columns: Name, Schedule, Due time, Target topic, Repeats (∞
for 0), TTL, Owner worker.
| Control | What it does | Write |
|---|---|---|
| Schedule… | Schedule a trigger: Name, mode Cron (Schedule, a cron expression such as 0 * * * * *) or Point in time (Due time: RFC 3339 or a Go duration such as 30s), Target topic, Repeats (0 = indefinitely), TTL (optional). Schedule. |
yes |
| Delete… | Deletes the selected trigger, asked first. | yes |
States¶
Route /infra/states. Built-in page states (StateBrowser). The state store's keys
(State.QueryState, up to 1000; the first 1000 keys only when there are more), read again
on state-change events and every 2 s only while the view is shown. Flat (Key, Value
preview, ETag) or Tree (the keys as a name tree by their dot-separated segments, with
counts; click a segment to show only the keys under it, all to go back). Filter with
the value filter, e.g. name:cfg.*. Open (or Enter) shows a key's
Value (pretty-printed) and its Stream (the values read while shown). Read only.
EventStores¶
Route /infra/eventstores. Built-in page eventstores (EventStoreBrowser over
ListWorkers, the lifecycle topic and wrk.eventstore.metrics). One row per EventStore
worker: Id, Status, Health (from lifecycle status reports: ok, or degraded: <reason>),
Topics, Events, Rows, Failed, Rules, Fallback, Last error, Tags; a summary line of running,
degraded and failed inputs. Refresh status asks the worker's status; Detail (or
Enter) shows its topics and status answer. Read only.
Alerts¶
Route /infra/alerts. What went wrong or needs a look, collected in this browser since
the page was opened (a reload starts empty), for the active context:
- worker failures (error), and degraded or disconnected status reports and input gaps (warning), from the lifecycle topic;
- risk limit breaches (
sc.<S>.risk.limit.breach, one topic per scenario of the registry); - trading halts set (error) or lifted (info) after the first read;
- a context's api going down after it answered (error), and coming back (info);
- every action of the app that failed (error).
Columns: Last, Severity, Context, Source, Subject, Text, Count, First. A repeat counts up
in one row and moves to the top, unread again. Dismiss removes the selected alert;
Clear all removes all. Opening the view marks the alerts read (the header badge
counts the unread ones). Filter e.g. severity:error.
Changes¶
Route /infra/changes. Every write you sent, on every context, newest first (the newest
500 per context). Columns: Time, Context, What, Outcome (done, failed, declined),
Detail (the reason of a failure), Saved (yes, saving…, not saved: <reason>). A run of several writes (a bulk action, a feed
connect) is one entry. The log is kept per user by the app server in each context's state
(cfg.changelog.<USER>), so it follows you to every browser. An entry the server could not
save stays for the session, marked not saved; a context whose log could not be read is
named above the table. Read again reloads. Filter e.g. outcome:failed.
Events¶
Route /infra/events. Built-in page events (EventBrowser). The CloudEvents on the topics
you follow on this context (kept in this browser per context; the state-change topics by
default). The newest 500 are kept, with a running total and ● live / ○ connecting….
| Control | What it does |
|---|---|
| Topics… | Topics to follow: the topics the api has seen, most recently published first; search, tick, or type a topic it has not seen and Add; Follow. |
| Pause / Resume | Pause keeps receiving (paused, N waiting); Resume shows them. |
| Clear | Empties the list. |
| Flat / Tree | Columns Time (UTC), Topic, Type, Source, Data; or the topic name tree. |
Open (or Enter) |
The event's attributes (type, source, id, time, subject) and data. |
Read only.
Services¶
Route /infra/services. The services the api knows (Gateway.ListServices and
Config.GetService), as cards with dialable / not dialable, replicas and state store.
A card opens the service at /service/<name> with three tabs:
- PubSub: pick topics from the api's known topics (Reload topics), subscribe and stream their CloudEvents (Unsubscribe, Clear, search); and Publish a CloudEvent (Topic, CloudEvent type, CloudEvent source, data) — a write.
- State: the service's state (Dapr Query API) with live updates from the state-change topics.
- gRPC: pick a method, fill the form generated from its schema (Expert Mode shows the input/output types), Execute Call, or Start Stream / Stop Stream for a server stream. Methods that are not reads are writes.
Config¶
Pages¶
Route /config/pages. The pages: Built-in (read only; Copy makes it yours),
Shared (this context; Copy; × unshares, admins), Mine (this browser; ×
deletes). New page starts one; Generate… has your AI provider write one. On one of
your pages: Edit JSON / Hide editor (the editor validates as you type, lists the
errors with their paths and keeps showing the last valid version), Change with AI…, and
Share (Share again (replaces the shared version) when it is shared) — sharing is a
write. See Pages and Make a page.
Navigation¶
Route /config/navigation. The navigation structure in use and where it comes from (yours,
the context's shared one, or the built-in default), and its validation problems.
- Your structure: Drag and drop (drag by ⠿ to reorder or nest; drag views, pages and New group in from the Add palette; labels edit in place; ⊞ turns an entry into a group; ✕ removes; entries marked 🔒 can be moved, not removed) or JSON. Save keeps it in this browser; Reset drops it (back to the shared one or the default).
- Share (Share (replaces the shared one)) and Unshare the context's structure: admins, writes.
- Profile (this browser): presets Tabs and sidebar, Tabs and sub-tabs, Sidebar with sections, Sidebar tree, Default, or JSON and Apply.
See Pages.
Scripts¶
Route /config/scripts. Built-in page scripts (ScriptBrowser). Your scripts (this
browser) and Examples, the list of Operations (vf.<group>.<action>()) with a link
to the catalog with input schemas, an editor with a name, Save, Delete, Run on
<context> / Stop, the Output and the Operations called (writes marked,
failures with their error). See Scripts.
Settings¶
AI¶
Route /settings/ai. Your AI providers on the active context: Provider keys and
Model (with prices per million tokens from LiteLLM's list). Saved for you only, not a
platform write (no write gate). See AI.
Views not built yet¶
A navigation entry naming a view this app lacks shows Not in the web app yet with a link to the feature-parity issue (app#7); an entry naming a page that does not exist says so. A route the navigation does not have goes to the view of that name, else to Home with a notice.