Applied screens
Project workspace
Tasks, events, and supporting links remain within a recognizable project context.
On this page
Capture context
These are fresh captures of Radarist’s actual imported components in a temporary copy of the local source repo. Fictional records are supplied through props and intercepted local API responses. The harness preserves component styling and interaction code; it replaces server actions with no-op functions and blocks external network access.
Desktop captures use a 1440 × 1000 CSS-pixel viewport and phone captures use 390 × 844, at 2× pixel density. Some long workspaces are shown at a representative viewport position. The original PNGs remain in ignored local capture storage; optimized WebP assets are used here.
Read the screen
| Area | What to inspect |
|---|---|
| Identity editor | Title and appearance belong to the same project. |
| Lifecycle | Status and consequential completion are separate from appearance. |
| Section selection | Tasks, Events, Links, Files organize the resources. |
| Task grouping | Milestones divide execution into useful parts. |
Evidence boundaries
A complete-looking screen can include prototype-only controls. Applied captures do not assert that an account was updated, a task persisted, a file uploaded, or a backend request succeeded. Follow the linked component and pattern specifications for the actual behavior and known gaps.
Examples from the app
Actual Radarist components with fictional data. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-07 · Revision 0103e2549959 · Documentation v0.1