Agent Architecture: Agents with roles, rules and schedules by Dima GornovskyiAgent Architecture: Agents with roles, rules and schedules by Dima Gornovskyi
Agent Architecture: Agents with roles, rules and schedules
Most businesses use AI as a chat window: one person, one prompt, one answer, then everything resets. The work of remembering, scheduling and coordinating stays human.
What I built
A team of AI agents, each with a defined role, written instructions and a schedule. One triages tasks, one drafts content, one watches follow-ups, one prepares briefings. They share the workspace as a common memory.
How it works
Map the recurring work and split it into roles, the way you would design jobs for a small team.
Give each agent an instruction page: its job, its sources, its output format and its boundaries.
Connect the agents to the Notion workspace through MCP, reading and writing the same databases the owner uses.
Put each agent on a rhythm: daily for briefings and triage, weekly for reviews and reports.
Land every output in the workspace for review, and evolve the instruction pages as the business changes.
What changed
Recurring work happens without anyone starting it, and every agent works from the same truth. The first two agents take about a week. With four or five roles running, it returns four to six hours a week of delegated work.
Part of a larger build
Part of the Automation & Agents build. I built this system for my own business first. The full write-up and stack are on the Agent Architecture page at dimagornovskyi.com/projects.