The eaQbe-ISO standard
Each page of this guide covered one building block. eaQbe-ISO is the name we give to the assembled whole : a standard, battle-tested configuration that any project can adopt. It was distilled from our most demanding production system : an agentic platform that has run daily on a server for months, operated end-to-end by Claude Code : and then generalized so the same structure works for a marketing team, a finance department or a solo professional.
« ISO » is a wink, not a certification : the point is standardization. Same structure everywhere, so anyone who has seen one eaQbe-ISO project can navigate all of them.
The anatomy
your-project/
├── CLAUDE.md ← the rules : how to work here
├── MEMORY.md ← the agent's accumulated knowledge
├── lessons.md ← the mistake journal ( re-read every session )
└── .claude/
├── settings.json ← permissions ( 3 zones ) + hooks
├── hooks/ ← the automatic checks themselves
├── skills/ ← one folder per written procedure
└── agents/ ← job descriptions of the sub-agents
Seven elements, all plain text, all readable in an afternoon. Behind each one stands a chapter of this guide :
| Element | Concept | Guide page |
|---|---|---|
CLAUDE.md, MEMORY.md, lessons.md | The three-file memory | Memory |
settings.json | Permission zones | Settings & hooks |
hooks/ | Automatic reflexes | Settings & hooks |
skills/ | Written procedures | Skills & sub-agents |
agents/ | Dispatched specialists | Skills & sub-agents |
| MCP connections | Tools + long-term memory | MCP |
| Session rituals | Start informed, end recorded | Best practices |
The principles it encodes
- Everything is a file. Memory, rules, procedures, permissions : all plain text, all versioned, all reviewable. No black boxes.
- Conservative by default. A fresh setup asks before anything irreversible. Autonomy is earned zone by zone, not granted wholesale.
- Mistakes become rules. The lessons loop is not optional : it is the mechanism by which the system improves with use.
- Evidence before claims. Verification is wired into hooks and task definitions, not left to discipline.
- One structure, many projects. The same skeleton serves a trading pipeline, a documentation site or a client folder : only the contents differ.
Adopting it
The honest effort estimate : a useful first version of this structure takes one focused day : which is precisely what our Claude Code & Agentic AI training delivers : you leave with the standard installed on your own project, guardrails set, first skill written. The services team also deploys it directly for organizations that prefer it done-with-them.
But nothing here is secret : this guide is the standard, explained. Start with CLAUDE.md and three rules. Add a lesson the first time something goes wrong. You are already doing eaQbe-ISO.
Frequently asked questions
Is eaQbe-ISO a product I have to buy?
No : it is a configuration standard, fully described in this guide. The training and services accelerate adoption ; they are not gatekeepers.
Does it work for non-developers?
Yes : that is the point of the standardization. The files are plain language. The technical parts ( hooks, MCP ) are set up once : by us or by a technical colleague : and then simply work.
Where does the name come from?
From our own production system, where the configuration was forged, then generalized. ISO is a wink at standardization : one structure, recognizable everywhere.