Organising company knowledge in layers: foundation, domains, rules, access

A company memory brings together what makes your company work the way it does. But putting everything in the same place, at the same level, quickly produces a contradictory catch-all. The solution: organise knowledge in layers, each with its role, its pace and its owner.

Layer 1 — The foundation of fundamentals

What applies to the whole company, whatever the department: purpose, vision, mission, values, strategy, goals and indicators, target customers and markets, offers and prices, business model, brand and tone, organisation and roles, priorities and roadmap, principles, shared rules, data and security policies, key decisions, shared vocabulary.

• Pace: rarely changes.
• Owner: management, which approves it.
• Use: all agents and all teams refer to it.

Layer 2 — The domains

One domain per area of activity — sales, finance, customer relations — with its vocabulary, its processes, its rules, its decisions and its ways of working. Domains are added to the foundation, one by one: the memory is cumulative, and its value grows with use.

• Pace: changes often.
• Owner: the domain manager.
• Use: the agents and teams of the domain.

Layer 3 — The trade-off rules

What is decided without a person, what is escalated, and to whom. When two priorities conflict — deliver fast or check more —, which one wins? These rules turn intentions into decisions that can be applied, by a person as by an agent.

Layer 4 — The usage rules

The governance of the memory itself: who writes, who approves, how often. Without them, the memory fills up with competing versions or stops being kept.

Layer 5 — Access

Each agent is connected to the right scope of knowledge, with its rights, its approvals, its checks and its owners. The invoicing agent reads the finance layer and the foundation; it has no business reading HR files.

The principles that hold it all together

1. A single source for each type of information. A rule lives in one place; other documents point to it. Two copies always end up diverging.
2. Dated and versioned. Every change is dated, and you know which version was authoritative at which time.
3. Readable by people and by agents. Clear, structured sentences, with no internal jargon left unexplained.
4. Named owners. A lead keeps the memory; management approves the foundation; each domain manager keeps theirs.
5. Measured. The right test is simple: three months after it is set up, is the memory still kept up to date?

In a mid-sized company: several domains, several owners

The larger the company, the more this organisation matters: several domains, several sites, sometimes several companies. The foundation guarantees consistency; the domains keep their autonomy; access protects what must be protected. One lead per domain, and one person coordinating the shared rules.

Where to start

Not with everything. The foundation and a first domain are enough to start, with the trade-off and usage rules, and the agents already in service connected. The next domains are added once the first has proved itself.

That is exactly the scope of our Company Brain offer — six to ten weeks for a first scope. It remains optional: the Quick Start, the Process Agent and Business Agents can be bought without it. To understand why a shared memory matters: Why your AI agents need a shared memory and shared rules.

Frequently asked questions

Why separate the foundation from the domains?

Because they do not change at the same pace and do not have the same owners. The foundation rarely changes and is approved by management; a domain changes often and is kept by its manager. Kept separate, they stay consistent.

Does every agent see the whole memory?

No. Each agent is connected to the scope it needs, with its rights, its approvals and its owners. The invoicing agent has no business reading HR files.

How do we stop the memory contradicting itself?

By keeping a single source for each type of information, dating and versioning every rule, and giving named people the right to write and approve.