Owns the proactive half of a client relationship — the half that runs whether or not the client writes in. It reads the communication record over a bounded window, compares it to what those same people looked like last week, and turns the difference into one of five verdicts. It writes for you, about the client, and never to the client without your sign-off.
For an owner carrying five to fifteen named client relationships personally — the one they email, who also writes the proposals and decides what to charge next quarter. It is not reactive support: no tickets, no client-facing SLAs, no 24/7 handling. This role notices; it is not the one that answers.
One account, read every week and compared against itself. An account it could not read is declared unmeasured, never rendered as healthy.
client-intake
The prerequisite. Every address and every domain, working hours and timezone, SLA tier, the named approver, and the commercial baseline with a document, a version and a date. There is no run-one state without it.
weekly-review
Monday, per account. One week of the record becomes three beats — what changed, why it matters, what is next — where every claim resolves to a specific message.
churn-risk-scan
Weekly, across the roster. Scores drift from the structural floor out of a declared comms-only maximum, and returns one of five verdicts with an explicit list of what was not measurable.
escalation-response
Event-driven. Confirms the trigger against the harvested record, drafts in your voice with the evidence attached, and queues it for approval. It sends nothing.
qbr-report
Quarterly. Synthesizes the weeklies rather than re-reading the quarter, and carries the retainer sanity check — which it answers by flagging and stopping, never by repricing.
A profession doesn’t bundle its skills. It references them by name and version range, and they stay independently owned and separately versioned. The split below is the one thing worth learning: READ skills are the method, CALL skills are the capability. Counting method names says call it; counting http routes says read it. Only the second count is the test — and it holds for all 16 with no exceptions.
opvs profession equip @di-atomic/client-strategistYour first thirty days: run client-intake on one account, not five. The roster, the baselines and the commercial basis all get established there, and an account that skipped it is unmeasured rather than healthy.
One thing to know before you equip it, not after. Weeks one and two will come back mostly insufficient-baseline. Four of the six structural drift signals — reply length, latency, sign-off warmth, engagement — are deltas against a stored baseline and are uncomputable without one. Only a new CC on a formerly one-to-one thread and an RSVP shift work cold. That is the role working correctly in exactly the window where it is doing its most valuable work, and if nobody says so at intake it reads as useless right before it becomes useful.
Every @di-atomic profession is composed from skills I already ship and already use. If you want an account process that tells you what it could not see instead of reporting silence as health, that’s the conversation.
Book a 30-min call with Di-AtomicShipping a package rather than keeping an account? See propagate.