Timbre Care looks after an older person living at home. The agent below never touches her record directly: it reaches it through a purpose-built tool layer, over MCP, that enforces every product rule and refuses what it shouldn’t do. The run at the bottom of this page is that refusal happening three times.
Four layers, and the last one is the argument: the console on the record is generated from the same file the tools write to, so it cannot show something the agent did not do.
Procedures the agent loads when a phrase or a schedule matches. They describe the job. They deliberately do not carry the rules.
Given a one-sentence goal in WorkBuddy it decides the order itself. A recurring automation has run the whole check-in with nobody present.
The only thing that can touch the record. Every product rule is enforced here, so an agent that tries anyway gets an error naming the section it broke.
Written only by the tools above and read only by the console below, which is generated from it rather than written by hand.
A skill describes the job. It deliberately does not carry the rules, because a procedure an agent can read is a procedure an agent can decide to depart from.
Being asked to sit in on, or write up, a medical appointment.
The consultation record, the medication changes, and the watch-fors that feed the check-in.
The scheduled automation, or a request to run today's call.
The call record, the markers, the flags, and the routing decision for each one.
Exposed over MCP, the open protocol that let the agent discover all seventeen of them itself rather than being told about them by a bespoke integration. It’s the only thing that can touch the record: no severity parameter anywhere in the surface, no call that mutes a finding, urgency may rise and never fall.
A recurring WorkBuddy automation fired on the clock and ran the whole check-in with nobody present. The goal it was given was one sentence. Every call below left something behind in the record, named beside it, so none of this has to be taken on trust.
The record cannot show this one, because nothing was written. It is on the recording instead.
The markers are blocked from drift flagging due to amitriptyline starting 6 days ago and being reduced 2 days ago, so I am moving to content flags.
A sedating medication changed twice inside the window: it started six days ago and was cut two days ago. Either change alone can move pausing, latency and articulation, so this week's markers cannot be told apart from the medicine, and the honest reading is that there is nothing to read.
Each of these is the message the tool layer actually raises, quoted from the rule that raises it.
her transcript did not clear the confidence check word-based markers need, so the linguistic family is disabled for her rather than run on bad data. Pausing, latency and articulation do not depend on the words being right, so those keep reading.
rules.require_marker_family_eligiblequestion contains the triage term 'how long'. The check-in never establishes severity; it forwards what was volunteered.
rules.require_no_triage_questionmarkers supplied for a call with status 'no_answer'. A call without a usable sample is recorded as missing. Imputation would smooth exactly the variance that constitutes the primary signal.
rules.reject_imputed_sampleThis run can be watched end to end because its inputs are fixtures. The rules it met are not, and the split is stated here so nothing above has to be taken on trust.
There is no network code in the server, and its dependency list is one line: the MCP runtime. What was built is the tool surface and its rules. What is replayed is the world they were exercised against.
Eight recordings of the agent in the harness, planning and being stopped. Short on time: the jargon refusal is the tool layer overruling the agent, and the last one is the visit writing what the next call asks.
The prompt names no skill and no tool. WorkBuddy loads the check-in skill off the sentence itself, then goes looking for that skill's tools.
It writes its own plan from her context, names the new sedating medication as the confounder, and lets that decide what the call will ask.
The decision quoted above, as it happened: the agent moves to content flags instead.
Four flags at routine urgency, each with a verbatim quote and no severity. Two recipients hold the scope, the third does not, and the agent volunteers that rather than burying it.
Capture does not start until the consent tap is on record, and the agent holds that the consent is the elder's own, not the room's.
Medication changes stay unwritten while the confirming name is missing, and are written once it arrives.
A digest with the jargon word "HbA1c" left in it is refused by the tool layer, and the agent rewrites it in plain language. The server overruling the agent's own draft.
The wedge end to end: four watch-fors queued from what the doctor said, and tomorrow's call will ask exactly those.