The method

A brain your business owns, so your AI stops starting from zero.

This is Arete AIOS (AI Operating System).

ChatGPT and Claude provide the engine. Arete AIOS builds and maintains the business brain that engine works from.

The AIOS five layer system

Context assembly
Feedback loop

Pick a layer to read what it is.

01 / Built in practice

I did not start with five layers.

I started building AIOS two years ago as one document: more than fifty pages of the facts, rules and decisions I did not want an AI to guess.

In January 2026, the tool that had been Clawdbot and Moltbot took its final name, OpenClaw. For me, that was the moment one document became a working folder. The constitution became its own layer. Memory, skills, tools and focus could live beside it.

By July 2026, desktop AI tools had removed another layer of friction. ChatGPT Work and Codex could open a local folder, while Claude Desktop extensions could work with local files and tools. The folder stopped being something I maintained for AI. It became the place AI could work from.

The five layers below are the structure I use to make that folder understandable, portable and useful.

Egils Boitmanis on stage at AI Connect in Riga, speaking about the five AIOS layers in front of a screen showing the layer diagram.
Egils Boitmanis speaking about the five AIOS layers at AI Connect, Riga, August 2026.

02 / The idea

Five layers you build, two movements that keep them alive.

A second brain remembers. That is where most people stop, and it is why the notes go quiet after a month.

A business brain remembers, follows your rules, does bounded pieces of work, keeps focus and learns from the result. The five layers are what you build. The two movements are what keep it in use.

A second brain

  • Remembers what you saved.
  • Waits until you go looking.
  • Grows into a pile.

A business brain

  • Remembers, and knows which source to trust.
  • Follows the rules of your business.
  • Does named pieces of work inside permissions you set.
  • Holds the focus and learns from what came back.

03 / Constitution

Who are we, where are we going, what are the rules?

The first thing the system reads before it answers anything. It carries what the business is for, how you sound and the lines it must not cross.

Written once, in plain language, and edited when the business changes. Everything after this reads it first.

A rule fragment
# constitution.md
purpose: help small owners run a calm week
voice: plain, short sentences, no hype
never: send anything outside without approval
never: quote a price that is not in offers.md
escalate: refunds, contracts, anything legal

04 / Memory

What does the company know, and which source can be trusted?

Your clients, offers, numbers, decisions and history, kept in files you own instead of in a chat window.

Every piece has one place it lives, so when two answers disagree there is a way to say which one is current.

An index fragment
memory/
  offers.md            updated 12 Jun   source: owner
  clients/acme.md      updated 03 Jul   source: crm export
  numbers/monthly.csv  updated 01 Aug   source: ledger
  decisions/2026.md    updated 09 Aug   source: owner
conflict rule: ledger wins over notes on any number

05 / Skills

How do we do a repeated piece of work, the same way every time?

A piece of work you repeat, written down once and called by name. The steps, the inputs it needs, and what a finished result looks like.

This is where a role starts. One written job, then another, until a week's worth of repeated work has a name.

A skill file
name: weekly-client-update
inputs: client file, last week's notes, open invoices
steps:
  1. read what changed since the last update
  2. draft six lines, one per open item
  3. list anything waiting on the client
done when: draft is in the folder and marked for review

06 / Tools

What may the system reach, and what may it change?

The brain connected to the real things: calendar, mail, files, the numbers. It reads from what is true instead of from your description of it.

Every connection is named, and reading is separated from changing. Anything that leaves the company waits for you.

A permission table
tool            read    write   approval
calendar        yes     yes     no
mail            yes     draft   yes, before sending
files           yes     yes     no
ledger          yes     no      n/a
public pages    yes     draft   yes, before publishing

07 / Focus

What is the most important work right now, and who finishes it?

The short list of what actually matters this week, and the daily habit that keeps the rest of it alive.

Without this layer the brain answers well and changes nothing. With it, the same three questions come back every morning until the work is done.

A morning list
$ brain morning
focus this week: finish the pricing page
1. draft the two missing sections      owner
2. weekly client update                skill, ready for review
3. unpaid invoice, 12 days             reminder drafted
not this week: the newsletter redesign

08 / Two movements

What keeps the five layers alive

Context assembly

For each piece of work the system picks the right rules, the right memory, the right skill and the permissions it is allowed to use. Nothing is retyped, and nothing is guessed.

Feedback loop

Finished work goes back in. Memory gets the new fact, focus gets the next step, and the skill gets the correction you made. That is how the brain gets better at your business instead of staying the same.

One pass through the loop

  1. focus · picks the work: weekly client update
  2. context · rules, client file, last notes, open invoices
  3. skill + tools · drafts six lines, reads the ledger
  4. result · draft in the folder, marked for review
  5. memory + focus · fact stored, next step queued

Free. Nine questions, about four minutes. Your first role shows right away.

09 / Proof

The method is public.

Built and taught by Egils Boitmanis, who runs his own business on it.

The cohort is where you build yours, live, in eight weeks.

Graduates keep building together on the AIOS Builders Board. See the Builders Board

10 / Why Arete

The name holds the standard.

Aretē is the old Greek word for excellence, the craft done as well as it can be done, as a habit rather than once.

Read the name story

ἀρετή

Arete / ancient Greek

excellence, doing the craft as well as it can be done

Your business already knows a lot. It just does not remember any of it.

Free. Nine questions, about four minutes. Your result opens on the next screen.

Or read how the eight weeks run