Clientlyy | Truth Computing

Problem

Client communication for personal injury law firms.

Client communication infrastructure for personal injury law firms: routine status updates to clients, at the volume a busy practice generates, without losing attorney control over what actually goes out.

Research Question

Can routine updates be automated without losing attorney control?

Can routine client updates be automated while keeping an attorney in control of every message that goes out.

Architecture

Not published.

No technical documentation of Clientlyy's internal architecture exists in this repository. We do not describe its architecture here rather than guess at it.

The following sections are not published for the same reason: no source documentation for them exists in this repository.

Models / Components. Not published.
Data Boundary. Not published.
Evaluation. Not published. No pass rate, accuracy number, or benchmark score for Clientlyy should be inferred from anything on this site.
Failure Modes. Not published.
Security. Not published.
Reliability Controls. Not published. Clientlyy is not known to use the CLINICAL_HOLD pattern described on the Reliability page — that pattern documents a different, healthcare-context system.
Release History. Not published beyond what's in the public Shipping Log on the homepage.

Human Authority

Attorneys control what goes out.

Per the product description on our Systems page, Clientlyy "automates routine client updates while keeping attorneys in control of outbound communication." We do not have further internal documentation on exactly how that control is implemented, so we describe only what is publicly stated.

Known Limitations

What we don't know, publicly.

This repository contains no technical documentation of Clientlyy beyond product-facing descriptions and business records unrelated to the software itself. We are not publishing architecture, model, security, or evaluation claims for Clientlyy because we do not have grounded material to publish. This is a gap in our own documentation, not a claim that no such material exists internally.

Artifacts

What's public today.

The live product at clientlyy.com. Its short description on the Systems page.