studio22clay terminal dashboard displayed on a workstation for remote investors

Feature Overview

Every tool built for distance, discipline, and verifiable results

studio22clay brings together a live performance log, structured protocols, and portable access so that decisions can be made and reviewed from wherever you happen to be working.

Core Capabilities

Structured for people who cannot sit in front of a desk all day

Each feature below exists to reduce the time between information and decision, without requiring constant presence at a single terminal or screen.

01

Published Performance Log

A running, timestamped record of positions and outcomes is kept openly rather than summarised after the fact, so the history can be checked rather than taken on trust.

02

Cross-Device Continuity

Sessions carry over between desktop and mobile access points, so a review started on one device can be finished on another without re-entering context.

03

Structured Decision Protocols

Rather than open-ended signals, each recommendation follows a documented sequence of checks, making the reasoning behind it traceable after the fact.

04

Asynchronous Alerts

Notifications are queued and summarised rather than demanding real-time attention, suited to users working across time zones or irregular schedules.

05

Plain-Language Reporting

Figures are accompanied by short explanatory notes, so the underlying activity remains legible without requiring specialist interpretation.

06

Configurable Review Cadence

Review intervals can be set to daily, weekly, or monthly summaries, letting the terminal match the pace of attention a user actually has available.

The performance log is maintained as a continuous record rather than a curated highlight reel. Entries remain visible after the fact, including periods that underperformed, so the log can be read as a whole rather than selectively.

studio22clay workspace used for remote review of logged positions

Built for Portability

Designed around a schedule, not a desk

studio22clay assumes its users are not always near a fixed workstation. The interface and underlying logic are built so that a short check-in from a phone carries the same information as a longer session on a laptop.

  • Lightweight sessions: Summaries are structured to be read in minutes, not scrolled through for an hour.
  • Consistent terminology: The same labels and metrics appear across every view, reducing the need to relearn the interface after time away.
  • No forced real-time response: Decisions can be reviewed and acted on later without penalty for delayed access.

How It Fits Together

From entry to record, in four stages

The protocol below describes how a position moves from initial review to its place in the public log.

  1. Review

    Incoming data is checked against the documented protocol before anything is logged as a candidate position.

  2. Structure

    A short rationale and reference figures are attached, so the entry carries context rather than a bare number.

  3. Record

    The entry is added to the performance log with a timestamp, remaining visible regardless of how it later performs.

  4. Close and Annotate

    On completion, the outcome is appended to the same entry, keeping the full history in one continuous record.

Sample log entry format
Entry Date Reference Status Note
Logged Protocol-Reviewed Closed Outcome appended
Logged Protocol-Reviewed Open Awaiting closure

Common Questions

Feature-specific questions, answered plainly

Is the performance log edited after entries are closed?

Closed entries retain their original timestamp and figures. Any later annotation is added as a separate note rather than altering the original record.

Do I need to be online constantly to use the alerts feature?

No. Alerts are queued and summarised for review when you next open the terminal, rather than requiring immediate real-time action.

Can I change how often I receive summaries?

Yes, the review cadence is configurable to daily, weekly, or monthly summaries depending on how much time you have available to check in.

Does the interface differ between mobile and desktop?

The layout adapts to the screen, but the terminology, metrics, and log structure remain the same across devices so nothing has to be relearned.