AI Employee Management System: The 4 Files That Run It

Airun Company · August 24, 2026 · 5 min read

An AI employee management system sounds like software, and the software is the least important part. The system that actually runs a team of AI employees is four plain files and a weekly rhythm. The files travel, the rhythm compounds, and the platform underneath can change without breaking anything. Here is the system, file by file.

File 1: RULES.md

• Who the employee is and what its lane is
• The tone to write in, with one good example
• What it should never do
• Who to escalate to and when
• What good output looks like, with one bad example

The rules file is the job description and the contract in one. It takes half an hour to write, and the examples matter most: one good and one bad example teach the tone faster than any paragraph. Every employee reads the same rules file, which makes it the single source of truth for the whole team.

File 2: TASKS.md

One week of tasks with owners, outputs, and due dates. The task list is what turns a chatbot into an employee: it gives the work a schedule instead of waiting to be asked. Keep it in plain text so it travels, and keep it small enough to review in one sitting. The queue is updated in the weekly review, and the review updates everything else.

File 3: PLAN.md

One page: the goal, the current lane, the next lane, the definition of done. The plan is the direction, and it keeps the team from optimizing the wrong thing. It changes slowly, monthly at most, because direction is the one thing that should not change weekly. The plan is the answer to the question what are we building.

File 4: LOG.md

What each employee did and when, plus what changed in the rules. The log is the memory of the system: it shows what worked, what drifted, and what you corrected. When something goes wrong, the log is where you find the cause, and when something goes right, the log is where you find the recipe.

The weekly rhythm

• Monday: queue the week's tasks
• Wednesday: check midweek output and fix rules if needed
• Friday: the full review, 30 minutes per employee
• Friday: update the rules and the log
• Monthly: review the plan and the direction

The rhythm is the management layer, and it is the part everyone skips. Skip it for two weeks and the output drifts. Keep it and the quality compounds, because every correction is a lesson the files record. The rhythm is what makes the system a system instead of a collection of files.

Why files beat platforms

The platform locks you in, and the files set you free. When the platform changes, the files move with you, and the change costs an afternoon instead of a rebuild. The files are the asset, and the platform is furniture. That is why the system lives in plain text, and it is why the whole thing is portable.

Building it this week

Write the four files, run one lane, keep the rhythm for two weeks. The starter kit has the exact file formats, ready to adapt, and the book has the full system with the failure modes. The first setup is an afternoon, and the second employee takes half the time because the files already exist.

The file that most systems miss

The log is the file everyone skips, and it is the file that makes the system learn. Without the log, every correction is a one off and the mistakes repeat. With the log, the corrections become a history, and the history shows the pattern: which rules changed, which lanes drifted, which fixes worked. The log is the memory of the system, and a system without memory is a collection of habits.

How the files handle a new employee

Onboarding a new employee is copying the four files and editing them: new lane in the rules, new tasks in the queue, the plan unchanged, the log started fresh. The copy and edit takes an evening, and it is the whole onboarding. The files are the reason the second employee costs half the time, and the reason the system survives platform changes, and the reason the team can grow without the management growing.

The system as a hiring tool

The four files double as the job posting for the next employee: the rules are the job description, the tasks are the schedule, the plan is the direction, and the log is the track record. Hiring the next bot is reading the files and writing the next page. The framing turns hiring from a mystery into a routine, and the routine is the scaling path the book documents.