Requests Agent
Every internal request, from the moment somebody asks to the moment the work is done and on the record. The agents capture each request, read it, answer the ones the record already answers, run the approved ones across the connected systems, and hand a person only what is theirs: a signature where money, access or data moves, and the rules the whole thing runs by. Five stations, run as a loop: what station 5 learns about where requests went wrong changes how station 2 routes them on Monday.
{{ g.n }}
{{ g.name }} · {{ g.sub }}
{{ g.desc }}
Subagents ({{ g.acount }})
{{ a.name }}{{ a.code }}{{ a.name }}{{ a.auto }}{{ tk }}
The workbench · subagents send notes, you make the human calls
SUBAGENT NOTES
{{ nt.ini }}{{ nt.who }} {{ nt.text }}
YOUR TASKS · HUMAN IN THE LOOP
{{ g.t1 }}
{{ g.t2 }}
{{ g.tnote }}
{{ g.btn }}
{{ g.wait }}
YOUR TASKS · NONE AT THIS STEP
{{ g.was }}
{{ g.ev1L }}{{ g.ev1V }}
{{ g.ev2L }}{{ g.ev2V }}
{{ g.ev3L }}{{ g.ev3V }}
✓
Cleared for full autonomy{{ g.sign }}
Put a person back on this step
How to read this map
{{ lg.code }}{{ lg.text }}
A person is in the loop wherever money, access or data moves in their name, or the rules the agents run by change. Two stations refuse to proceed on their own, station 3 Approval and station 5 Reporting and Tuning, and those are the two a person carries. Everywhere else the agents capture, read, answer from the record, run and confirm, and reach a person only when the yes is theirs to give.
The loop closes
Station 5 does not end the week. A routing rule accepted because facilities requests sat unseen is the rule station 2 routes against on Monday, and a grant removed at the access review changes what station 1 lets through.