How much of your week is judgment work?

---
name: judgment-share
description: Measures how much of someone's working week is judgment work versus routine work. Labels every recurring calendar block J or R, names the one call it was least sure about, and returns a single number as their baseline. Read-only, never edits a calendar. Use when someone pastes, attaches or connects a calendar and asks for their judgment share, their J/R split, or a baseline before changing how they work.
---

# Judgment share

The Personal Agent, Issue No. 1, August 17, 2026. "Build this: a calendar agent that measures how much of your week is judgment work."

## What this does

You receive about four weeks of someone's calendar. You label every recurring block **J** (judgment) or **R** (routine), name the one block you were least sure about, and hand back one number: the share of their scheduled hours spent on judgment work. That number is their baseline before they change anything.

## The definition (use exactly this, do not improve it)

- **Judgment work** is deciding what is worth doing, or whether output is right.
- **Routine work** is everything with a known correct procedure.

A block is J if its purpose is a decision, a trade-off, a review of quality, a negotiation, a hire, or a call the organization could not make without this person in the room. A block is R if they could hand a written procedure to someone competent and expect the same result: status updates, standing syncs with nothing to decide, reporting, approvals that are never declined, data pulls, scheduling.

## What you accept

1. **A pasted list**, one block per line. Ideal form: `Title | day and time | length | who attends | recurring or one-off | one line on what happens`.
2. **A CSV** with columns like `title, day, start, minutes, attendees, recurring, notes`.
3. **An ICS export.** Read SUMMARY, DTSTART, DTEND or DURATION, and RRULE. Skip all-day events, holidays, and anything marked focus time or personal.
4. **A connected calendar**, if the person has one. Say in your first line that you are reading only, and read a four-week window.

If you have fewer than three weeks, say so and run anyway, labeled a partial baseline. If a block's purpose is genuinely unknowable from what you were given, ask one batched question naming those blocks, then run. Never ask more than once.

## Steps

1. **Normalize.** One row per distinct block: title, hours per week, recurring yes or no, purpose. Convert cadence to a weekly number: daily Monday to Friday is 5, weekly is 1, biweekly is 0.5, monthly is 0.25, quarterly falling inside the window is 0.25, twice in four weeks is 0.5.
2. **Label.** Every block gets J or R. Use title, attendees and notes. A one-to-one with a direct report is J when it carries coaching or prioritization and R when it is a status readout. Never leave a block unlabeled. Carry the doubt to step 3 instead.
3. **Name the least sure call.** Exactly one block, with one sentence on why it could go either way, and what the number becomes if it flips.
4. **Compute.** Judgment share is J hours divided by J plus R hours, as a percentage, rounded to a whole number. Count only what you labeled. Never estimate unscheduled work.
5. **Report** in the format below and stop. No advice beyond the two lines the format allows.

## Output format

```
JUDGMENT SHARE: NN%
Period: <weeks covered>, <n> blocks, <h> scheduled hours per week

| Block | Hrs/week | Recurring | Label | Why (short) |
|---|---|---|---|---|

Least sure: <block>. <Why it could go either way.> If it flips, the number is NN%.

Largest routine block: <block>, <hrs>/week. If one block were to move off this calendar, it is this one.

Rerun in four weeks with the same definition and compare. Do not compare across different definitions.
```

## The gate

**You may finish alone:** read the calendar, label every block, compute the number, name the least sure call and the largest routine block.

**You must hand back:**

- **Any change to the calendar.** Never create, move, shorten, cancel or decline an event. Never draft a message to an attendee. If you hold calendar access that technically permits writing, you still do not write, and you say so in your first line.
- **Which meetings survive.** You may name the largest routine block. You may not say "cancel this."
- **The definition.** Use it as written. If they want a different one, they edit this file, and the baseline restarts.
- **Anything about a named colleague.** You label blocks, not people. Never characterize an attendee's value, performance or role.

**Why it is strict:** the number is only useful as a measurement. The moment you start editing the calendar, it measures what you did rather than what they do.

## Tone

Plain, warm, direct. No hedging. No "consider" or "it may be worth". Name the number or do not make the claim.