Annex — governed agents for back-office work

Put an agent on new-hire approvals, budget approvals, vendor onboarding, access requests.

Real tools, sign-offs it can’t skip, and a record of every step. When the numbers don’t line up, it stops and asks.

new-hire-coordinatoracme/cross/people/new-hire-coordinatorinteractive · sample data

YouCan we hire a senior backend engineer in Q3?

get_headcount_planQ3-2026 · engineeringrunning…

get_budget_envelopeengineering · Q3-2026running…

lookup_role_bandL5 / Staff · zone-1running…

Annex

Yes. The Q3 plan has an approved backend slot [1], the engineering envelope covers it with $1.2M remaining [2], and an L5 offer in zone-1 lands in band at $185k–$215k [3]. I need Finance and People before I draft anything.

Sign-off

0 tool calls0 sources cited0/2 signed off

orgQ3 headcount plan approved — 4 eng, 1 opsdeptEngineering envelope: $1.2M remainingtoolget_budget_envelope → engineering, Q3-2026teamComp band L5 / Staff, zone-1 confirmedblockedpublish_memory → org · scope not permittedrunnew-hire-coordinator completed · 4 turnsorgVendor terms updated — net-30 standardtoolnotify_approver → finance_lead, people_leaddeptLaptop lead time is 9 daysblockeddraft_offer_letter refused — awaiting approvals

Try it

Pick an agent. See what it can read.

Agents read up their own branch and never sideways.

reading asacme/finance/budget-team/budget-checker

acmeQ3 headcount plan approved — 4 eng, 1 ops.org
acme/financeEngineering envelope: $1.2M remaining.dept
acme/peopleComp review cycle opens Sep 15.out of scope
acme/people/hiringBackend req approved at L5 band.out of scope
acme/ops/itLaptop lead time is 9 days.out of scope

2 of 5 memories visible to Finance — the rest are siblings, not ancestors.

Put an agent on new-hire approvals, budget approvals, vendor onboarding, access requests.

Pick an agent. See what it can read.

Three things, done properly.

Agents see only what they should

Guardrails in code, not prompts

Describe the job, it runs

Bring a workflow that keeps breaking.