Record through —
The record,
at a glance.
What the record holds, how much of it has been read, and which patterns travel together.
See Shelby work the record →Artifacts
—
on the published manifest
Analyzed
—
—
What travels together. Of the — ways to pair the — labels, — share two or more artifacts. The tightest pair shares —.
Tightest pair
—
—
— patterns in the record; ten generic labels shown here. Arc length: artifacts carrying each label. Ribbon width: artifacts two labels share, on the same scale; one artifact can carry several labels, so ribbon ends can overlap. Pairs sharing fewer than two are not drawn.
Go deeper. Every figure above opens onto a view built from the same record.
| Case | Tier | Key Fields |
|---|
| Case | Posture | Lore |
|---|
| Case | Posture | Lore |
|---|
Artifacts
Explore the corpus by shape and density. Artifact-level rows live in the operator console.
Aggregate artifact snapshot
LoadingLoading corpus shape and density. Searchable artifact rows are available in the operator console.
Patterns
A ten-label demonstration of aggregate relationships from the snapshot, rendered with generic pattern labels.
| ID | Created | Kind | Matter | Status | Sources | Purpose |
|---|
| Time | Case | Hrs | Description |
|---|
Portal Settings
Preferences are saved locally in your browser.
Used for billing entry totals and daily exports.
Initials used on billing exports (e.g. MAK).
Snap time entries to this multiple.
Pre-selected code when opening the Billing tab.
Rows shown in the Artifacts table before pagination.
Tab shown when the portal loads.
Max characters shown for artifact summaries in tables.