Behavioral Psychograph

How You Seem To Think At The Machine

This is not a personality test and not a clinical claim. It is a behavioral reading of your operator style using only telemetry structure from Thu, Mar 19 through Mon, Mar 23: timing, switching, app/domain gravity, typing distribution, and clipboard behavior. No keystroke content was used to build this profile.

Generated 2026-03-24 11:19 PDT
Thesis

The Data Says “System Conductor”

You do not behave like a single-threaded maker trying to protect a monk-like bubble. You behave like a conductor of tools, models, and contexts who can re-enter build mode fast, but pays a real tax when admin and publishing surfaces mix into the same operating field.

93
Externalized Cognition

You appear to think by steering systems and models, not by drafting in isolation.

95
Interrupt Recovery

Switches happen often, but the return path back into build mode is extremely fast.

80
Novelty Appetite

You scan broadly for leverage, examples, tools, and opportunities before collapsing back to build.

85
Mode Purity

When a day is meant to be a build day, you can make it very pure.

78
Afternoon / Evening Voltage

Your serious output shows up after noon, not in a classic morning-maker pattern.

Interpretation

Core Read

You look like a conductor, not a monk.

82.2% of all typed characters in the five full days landed inside Claude, Codex, or OpenWork, with 1,717 paste events into those tools. That is not a person trying to retreat from systems. It is a person using models as thinking surfaces, delegation surfaces, and intermediate memory.

Shadow side: orchestration can feel productive even when the real bottleneck is choosing and committing.

You are unusually elastic after interruption.

Median return from communication back into build mode was 0.36 minutes. From research back into build it was 0.26 minutes. That suggests you are not fragile in the face of interruption. You can bounce out, collect signal, and snap back.

Shadow side: because you recover quickly, you can underestimate how much context shifting is happening around you.

Your best state is a named build regime.

Across the full five-day window, 84.9% of non-ambient focus stayed in build surfaces. The cleanest execution day was Sat, Mar 21 at 97.2% build-share with 31,246 characters typed. You do not look like someone who benefits from open-ended, mixed-mode days.

Shadow side: admin, publishing, and GTM work feel disproportionately grimy because they dilute the state that actually works for you.

You scan wide, but you ship from a narrower channel.

The widest exploration day touched 60 distinct browser hosts, but your dominant hosts still clustered around build and AI surfaces. That pattern reads as strategic scanning rather than random doomscrolling: you range widely, then collapse back into a small execution stack.

Shadow side: a broad scan budget without a closing ritual can quietly turn into low-grade decision debt.

Your clock is operator-time, not office-time.

Only 1,754 typed characters landed in the morning across the full five-day window. Afternoon and evening carried 58,727 and 44,869 characters respectively, with even late night still active at 19,341. The data does not support a fake 9-to-5 self-image.

Shadow side: if you judge yourself by morning standards, you will misread your actual pattern and create shame that is not evidence-based.
Evidence

Behavioral Signals

Assistant char share
82.2%
AI paste events
1,717
AI pastes per 1k chars
13.8
Build-share across five full days
84.9%
Median comm -> build return
0.36 min
Median research -> build return
0.26 min
Widest host spread in a day
60
Morning typed chars
1,754
Afternoon typed chars
58,727
Evening typed chars
44,869
Operating Rules

What This Profile Wants

  • Protect one primary build regime each day before admin or webmaster surfaces open.
  • Use a separate named sweep for Slack, Search Console, Bing, Cloudflare, and similar admin/distribution work.
  • Convert repeated AI copy-paste loops into canonical files, briefs, and standing prompts so orchestration stops leaking memory.
  • Treat afternoon and evening as prime output windows; use morning for setup, intake, or lower-friction tasks if you need structure there.
  • When you scan wide, end the scan with one forced commit: one repo, one artifact, one shipped decision.
Dominant Surfaces

Where The Mind Kept Going

larry.moran.bot 93m
scottpedia0.github.io 69m
github.com 62m
meet.google.com 39m
gemini.google.com 38m
deckmanager.go2.io 30m
app.slack.com 29m
aistudio.google.com 22m
access.moran.bot 19m
mail.google.com 16m
Strongest Work States

Longest Cognitive-Mode Blocks

These are observed foreground stretches after merging same-mode activity. They are useful as state-shape evidence, not exact stopwatch truth.

Build block
Sat Mar 21 10:31 PM
10.5h
Claude: 10.4h, Codex: 7m, Google Chrome: 1m
Build block
Thu Mar 19 02:38 AM
9.0h
Claude: 9.0h, Go2: 1m
Build block
Fri Mar 20 12:21 AM
5.6h
Claude: 5.6h
Build block
Fri Mar 20 06:05 PM
2.5h
Claude: 71m, Codex: 41m, Google Chrome: 30m
Build block
Mon Mar 23 03:12 PM
2.4h
Codex: 72m, Google Chrome: 38m, Claude: 19m
Build block
Sat Mar 21 01:36 PM
2.3h
Codex: 67m, Claude: 51m, Google Chrome: 17m
Build block
Sun Mar 22 11:48 AM
109m
Codex: 48m, Claude: 47m, Google Chrome: 9m
Build block
Sat Mar 21 03:56 PM
103m
Claude: 50m, Codex: 38m, Google Chrome: 13m
Translation

Plain-English Profile

You look like someone who gets leverage by turning thought into orchestrated external structure fast. You appear comfortable thinking in public with tools, comfortable revising in-flight, and unusually capable of resuming a build thread after stepping out for signal.

The real risk is not distraction in the usual sense. It is over-mixing modes. The same traits that let you steer multiple copilots and surfaces can also blur the line between decisive progress and expensive steering. Your best state is not “less tooling.” It is sharper regime boundaries.

Best evidence for that: 84.9% build-share across the full five-day window, 1,717 AI paste events, and sub-minute median returns back into build mode after comms or research.