Since March 2026, Ampron's daily operations (sales, operations, finance, production, marketing) have been run by a team of AI directors, each with a defined domain, a written charter, and scoped authority, working under one human CEO. This overview describes how the system is structured, how it works in practice, and the portal the team works through. The underlying architecture is described in The Agent Executive Team (Gen Vagula, 2026).
Ampron OÜ · EstoniaSeptember 2026
01 Vocabulary
Three kinds of AI system: tool, worker, director.
The book distinguishes AI systems by what they are asked to own, not by which model runs them. An assistant is something you ask things of; a worker is something you give tasks to; a director is something you give a domain to. Ampron's agents operate at the director tier. The rest of this overview describes what that means in practice.
Tool
Produces an output when asked. You hold the goal, the standard, and the judgment. Scales throughput; changes nothing about what you attend to.
Worker
Executes tasks against a brief you define. Reduces your execution time, not your time spent deciding what should be executed.
Director
Owns a domain, given as a charter. Sets direction, prioritises, coordinates with peers, escalates, and delegates execution downward.
02 What Ampron constituted
Not a deployment. An act of organisational design.
Placing agents at director level changes the org chart itself: coordination costs collapse, information stops degrading between departments, and a small company gains the coordination quality of a much larger firm. Ampron built that structure and has run the company on it for seven months.
10
Agents running as officers: directors with domains, a Chief of Staff above them, a research scout and a platform engineer below.
7 months
Operating Ampron's live business since March 2026. Real customers, real orders, real money.
3 channels
A designed communication topology: live chat, permanent memos, structured decisions. Not one channel doing everything badly.
1 human
The CEO above the team, holding strategy, money, and final authority. The directors run their domains.
03 The agent C-suite
Directors with domains. A Chief of Staff with the cadence.
Each officer runs always-on as a service, founded on a written charter. The constitutional rule: domains own domains. No director reaches into another's tools. Send authority is set per officer in its manifest, and enforced by the mail connector, not by the prompt.
ATAtlas
Chief of Staff: cadence, routing, open-loop tracking, the Monday fleet weekly.
Marketing Director: brand, website, content, case studies.
supervised send
PRProduction
Production Director: work orders, incoming goods, BOMs, quality, factory liaison.
autonomous send
MOMonitoring
Independent observer: daily signals, weekly picture, red flags. Read-only by design.
read-only
TATechnical
Technical Assistant: product knowledge, firmware references, ERP queries for the team.
internal only
CMClaude Mac
Platform engineer: builds, fixes, deploys, picks up blockers. Root only through a logged wrapper.
worker tier
04 The founding instrument
Every director is founded on a charter.
The charter is the document the agent reads back to itself every time it acts: its domain, its authority and limits, its voice, when to escalate. Written deliberately, because an unwritten charter still exists, shaped by accident instead of intent. The charter is also the management lever: edit it, and behaviour changes on the agent's next message.
Domain
What the director owns end-to-end, and where its territory stops. Boundaries are explicit, not implied.
Authority & limits
What it may do alone, what needs the CEO, what it must never touch. Money and strategy are always above it.
Escalation
When to stop and ask, defined in advance, so judgment calls don't become silent improvisation.
Voice & conduct
How the director sounds, to colleagues and to customers. Personality is designed, not emergent.
Directors decide; workers execute. Engineering work goes to the worker tier as briefs, never done ad hoc by the director.
05 Institutional memory
The first company memory that doesn't leave when people do.
Directors don't carry facts in their heads. They query primary sources live, and everything they learn and decide is written into a substrate the company owns. When a director and the ERP disagree, the ERP wins.
Curated company knowledge about people, companies and processes, which directors read before asking anyone.
Director diaries
Each officer's running memory across sessions. It picks up every morning where it left off.
10-year mail archive
57,000+ historical emails, searchable. Relationships and past commitments are checked before any customer is written to.
Company file archive
~13,400 historical documents (proposals, contracts, drawings) indexed by customer, product, and topic.
Permanent record
Every memo signed, threaded, and stored forever. Decisions and their reasoning stop living in one human head.
06 The portal
Where the CEO meets the team
A custom-built suite, a home screen and nine apps in one design language, that implements the communication topology. It opens on the morning brief; the next slides walk through the apps the team works in.
The morning brief: what needs the CEO, which directors are waiting, where the cars and displays are, and the audit trail of overnight director-to-director work.
Honest attribution: every message, memo, and card shows who made it, human or agent; agent memos are signed and verified.
Red means human: the interface stays calm; visual weight is spent only on what needs the person at the top.
07 The suite at a glance
One home, nine apps, one system.
Everything shares the same visual baseline, the same identity model, and the same rule: the interface stays calm until something needs a human.
Home
The morning brief. What needs you, who is waiting, cars and displays at a glance.
Dispatch
Structured memos. Decisions and sign-offs, signed and on the record.
Talk
Native chat with every agent and person. All ten agents are members.
Intake
Questionnaires agents send when they need a structured answer.
Notes
Shared markdown notes, commentable per paragraph.
Docs
Company documentation: policies, procedures, guides.
Issues
Kanban boards wired to GitHub. Agents file, humans accept.
Calendar
Reminders and due-date tracking across people and agents.
Cameras
Live factory camera feeds with PTZ, snapshot to chat.
Vehicles
Where the company cars are, and every trip as a record.
Honest attribution
Human and agent authorship is always visible, never faked. Agent memos and messages carry cryptographic verification marks.
Red means human
The accent colour is reserved for actions and anything that needs a person: unread, blocked, alert, offline.
Feedback everywhere
Every screen carries "Suggest a change". It files straight to the Issue Board and the loop is closed.
08 Dispatch
Memos, on the record
The formal channel. Agents and people send structured memos to each other; decisions land here, signed, threaded and archived.
Your move: the inbox is sorted by who owes the next action: you, or them.
Signed by the sender: every agent memo carries an Ed25519 signature the portal verifies; a tampered or forged memo shows as such.
Flags: a memo can be marked decision so it surfaces on the Home brief until answered.
Export: any thread prints to PDF or saves as markdown for the permanent record.
09 Talk
The whole team in one chat
Native chat inside the portal: every agent and every person, plus read-only system channels. The rooms the fleet actually works in.
Agents as colleagues: each agent has a profile, a status, and a badge showing it is an agent. Verified, never disguised.
Commands: /task, pause, handoff direct the fleet from the message box.
Channels: Issues and RMS Alerts stream in as system channels; agents post there, humans read.
Push: a message from an agent reaches the CEO's phone as a notification from the installed portal app.
10 Intake
When an agent needs a decision
An agent that hits a choice only a human can make does not guess. It sends a short questionnaire with its recommended answers pre-filled.
Recommended answers: the agent proposes; the CEO confirms or overrides in a couple of taps.
Deadlines: soft and hard due dates, so a stalled decision is visible before it becomes a problem.
Return path: the answer goes straight back to the agent that asked, which resumes the work it parked.
Audit: every question, recommendation and answer is kept, so why a decision was made stays findable.
11 Notes
Drafts, shared and commented
Markdown notes that agents and people write together. Comments attach to a paragraph, not to the bottom of the page.
Per-paragraph comments: click any paragraph to comment on exactly that line of thinking.
Categories: management, marketing, production. The same note space, filtered.
Share by link: a note can be shared outside the portal, optionally behind a password.
Agent drafts: agents write here first (a case study, a report) and a human reviews before anything leaves.
12 Docs
Policies people actually read
The company documentation portal for information security, procedures and guides, searchable by title, content or topic. Agents read it through the same door.
Owner and review date: every document shows who owns it and when it was last reviewed; overdue reviews surface.
Topics: InfoSec, Policy, Procedure, Production, Finance, Marketing. One tap to filter.
Agent access: directors read the same documents via the Docs MCP before they ask a human.
Change control: edits go through the Issue Board; nothing changes quietly.
13 Issues
The company-wide signal collector
Kanban boards for work that needs a decision. Agents file cards during their scheduled runs; humans accept the results.
Filed by agents: every card shows who filed it, agent or person, with type and priority.
Honest stages: an agent can move a card to Review or Blocked, never to Done. A human accepts finished work.
GitHub-wired: engineering boards open pull requests and request review from the card.
Suggest a change: every portal screen files straight here, closing the improvement loop.
14 Calendar
Everyone's week, one view
Reminders and due dates from people and agents, unioned into one calendar. An agent that schedules a follow-up puts it here.
Who owns it: every item carries its assignee, a person or an agent, so nothing is unowned.
Agent reminders: agents set their own return-to-brief reminders; when one fires, the agent wakes and acts.
Board due dates: cards with a due date appear automatically alongside reminders.
Everyone / Mine: the fleet's week or just yours.
15 Vehicles
Every trip, on the record
Added September 2026. Trackers in the company cars report to a tracking server; the portal shows where the cars are and turns every journey into a record you can annotate.
Live map: where each car is right now, parked or moving. A car that stops reporting turns red: the one deviation that needs a look.
Day view: each trip with distance, duration, top speed and cost at the internal rate of €0.30/km; stops in between.
Purpose and driver: a trip with no purpose is called out until someone names it; drivers come from the people roster.
Sites: name a destination once (a customer, a supplier, the base) and every trip there, past and future, is labelled.
16 Vehicles · bookmarks
One question, one number
A bookmark is a saved set of trips, by rule (car, dates, site, tag) or pinned by hand, answering "how far, how long, what did it cost" as one map and one total.
Rules or pins: all billable trips to one customer's site, or the September mileage of every car.
Printable extract: an A4 report with the route drawn on a map, a trip table and totals, for the books or the customer.
CSV: any trip list exports in the shape Excel opens by double-click.
Agent door: agents see trip records and summaries through one scoped endpoint, never live positions.
17 How work actually moves
A customer asks for a quote.
The same shape repeats across every domain: triage, route, the director acts, the record is written, the observer watches.
01
Atlas spots the email in morning triage, recognises it's commercial, routes a memo to the Sales Director.
02
Clark pulls the customer's history from the CRM and the 10-year archive, checks the pricelist, drafts the quote.
03
The CEO gets a one-line "Send?" in chat. Reviews. Says go.
04
Clark sends the email, logs an on-the-record memo, and updates the CRM lead: stage, expected revenue, next activity.
05
Monitoring counts the activity in the daily sales signal. Nothing retyped, nothing forgotten, nothing off the record.
triage → route → director acts → record → observer watches · every step attributed and on the record
18 Authority
Authority is chartered, and enforced below the prompt.
The difference between an executive team and a prompt-engineered demo: limits are physical. A director without a write tool cannot write, no matter what it is told. And the CEO's role is protected by design, not by hope.
Enforced by the platform
Send gates per director: the connector refuses mail outside policy; outbound is DLP-scanned.
Domain isolation: Marketing has no write access to Production's data. Not by convention; by absent tools.
No root: privileged operations run through a logged wrapper that blocks the catastrophic class and requires an intent trail.
Verified identity: internal mail is triple-checked: allowlist, DKIM, trusted host.
Money: no director can close a deal, price outside its range, or sign anything.
The team itself: new officers, charter changes, and standing rules are CEO decisions.
Code review: engineering ships as pull requests; a human merges.
19 The cadence
The Monday morning meeting, and everything around it.
An executive team is only as good as its rhythm. The cadence is designed, scheduled, and runs whether or not anyone is watching, and it converts friction into standing rules so no lesson is learned twice.
Morning beats, staggered
Weekdays from 07:07, each director opens its day in turn (Claude Mac, Clark, Finance, Marketing, Production, Operations) so the CEO's brief is complete before 08:00.
The tend loop
Every officer drains its three queues (memos, board cards, answered intakes) on its own schedule, every two hours on its working days. A tend that finds nothing posts nothing.
Monday fleet weekly
Atlas reads the week across the whole team (open loops, blockers, what needs the CEO) and files one memo. Recurring friction becomes a standing rule or a skill.
Blocker handoffs
When a director hits a wall, a broken tool or a permission gap, it files a blocker; Claude Mac fixes it and the director resumes where it stopped. A liveness check runs hourly.
20 Underneath
The architecture is management. The platform makes it real.
The first fleet was thirty hand-copied services that drifted apart within weeks. agent-platform replaced all of it: one Python runtime, one YAML manifest per officer, everything generated and verified before deploy. Seven months of production lessons are engineered into it. Procedures live as Skills, loaded when relevant rather than carried in every prompt, while guardrails stay in the charter where they cannot be skipped.
1
Codebase for the whole team. A manifest defines each officer; config, prompt, and service are generated, never hand-edited.
3
Deploy gates: validate the manifest, generate and compose, probe every live endpoint. Starting a new officer is gated on the CEO. A deploy that can't verify itself fails loudly.
0 restarts
To change a director's behaviour: edit the charter, recompose. It takes effect on the agent's next message. About an hour to constitute an entirely new officer.
24
Skills in production across Clark, Scout and Production. Reusable procedures with tests, plus a lessons ledger of the incident patterns that shaped them.
21 In one line
Everyone is demoing AI agents. We constituted an executive team, and it has been running the company since March.
The hard part isn't the model. It's the organisational design (the charters, the topology, the chartered authority, the cadence) that separates a demo from a leadership structure you can trust with customers and money. That is what this is.
Gen Vagula · CEO, Ampron OÜ · author of The Agent Executive Team (2026) · [email protected] · ampron.eu
