User interface reference
3 min read
Reference for every rendered surface Remy delivers and how it is built. The user-facing description of each surface is in the relationship manager / financial advisor track; this page is the contract behind them.
Surfaces
Surface | Built from | Path | Notes |
|---|---|---|---|
Installer | Shipped page, one for everybody | skills folder | Sends the install prompt; shows the setup steps live from |
Dashboard |
|
| Recommendations (ranked, capped, paginated), meetings (7 back / 30 forward), relations (joined from the other stores), drafts, overnight status, radar; footer with build stamp, install report, setup |
Client 360 | The client's memory |
| Identity and key facts, executive summary, touch-point history, documents, portfolio and mandate context; unknown shows as unknown; observed, estimated and suggested visually distinct |
Meeting record | Meetings register and the brief |
| Brief before; write-up and follow-up draft after |
Meeting brief | The client's memory plus live web intelligence where approved | Beside the meeting record; PDF alongside | Header, timeline, recent asks, commitments both sides, changes, sensitivities, agenda, source chips; versioned refresh; branded four-page PDF |
Draft | Drafts store |
| Two tones; "Create draft" hands it to the user's mailbox |
Setup |
|
| Name, data mode, connectors; the only thing that moves a user from installer to dashboard |
Install report |
|
| Keeps the step graph after the run - answers "did every step actually run" |
Questions, approvals, evidence | Chat | - | Distinct interactions for clarification, memory adjudication, approval, missing permission - always with a defer path; per-task source coverage |
How a page talks to the platform
Channel | Mechanism |
|---|---|
Data | Read a knowledge-base file by path, under the reader's own permissions. A page addresses its reader's tree as |
Rendering | A list is declared with a template and hydrated by posting a typed message to the page's own window. The host renders rows; the page never writes them. |
Actions | A click carries a JSON payload read at click time: sendPrompt runs a skill by sending its prompt into chat; openDocument opens another file in the panel. Opening a document is an action, not a navigation. |
The panel is sandboxed without same-origin or top-navigation rights. Selected client, meeting, artefact version and active workflow stay explicit; switching client never reuses the previous client's context, draft or attachment.
Build-time checks
The chat client's attribute contract drops anything invalid without a word, so the build refuses a page whose script does not parse, whose bound field the row model cannot carry, whose prompt names a skill that does not exist, whose class has no rule in the stylesheet, whose bridge message has the wrong shape, or which carries an unsubstituted token. Each check exists because that exact failure reached a panel once.
Design system and brand pack
Colours, typography, spacing and component patterns are defined once in the design-system skill. A bank's brand pack overrides tokens for rendered briefs and PDFs. Accessibility - keyboard navigation, focus states, screen-reader labels, non-colour status indicators - is part of the base templates.
What is configurable
Which cards appear and in which order, per user, team or organisation.
Ranking bands and the cap on recommendations; the meetings window.
Brief structure and the sections of the client 360.
Languages, currency and time zone; brand pack.
Which actions a card offers and which skill each one calls.