LAA is an open orchestration pattern. It defines how a single governing component — the orchestrator — maintains coherence, memory, and governance across a heterogeneous set of agents operating on different platforms, in different domains, with different internal architectures.
What has value and cannot be reproduced is the relationship of trust. Human to human, human to AI — it does not matter. What matters is apprehending and documenting that trust relationship.
Most agent frameworks optimize for execution. LAA optimizes for trust. Capability is necessary but not sufficient — what determines whether a human actually uses an agent is fit: does this agent understand how I work, what I care about, when to act and when to ask?
The 7 layers do not describe how every agent must be built. They describe what the orchestrator must implement in full. The core (1–4) is immutable. Layers 5–6 are dynamic. Layer 7 belongs to the orchestrator only.
The minimum contract any non-LAA worker can return to integrate with the orchestrator. 6 fields. No architecture change required.
reversible feeds the autonomy engine. resource_consumed feeds budget governance. outcome + confidence feed trust calibration over time. side_effects allow reasoning about cascading actions.
LAA adoption is incremental. Each level delivers immediate value. No store required. No shared infrastructure required.
"In a world where AI makes every output cheap, the scarce resource is proven human connection. What becomes scarce and valuable is the proven trust between a specific human and their agent ecosystem."
— LAA Specification, v1.3
The full LAA specification — framework, memory contract, feedback loops, economic governance, and portability model.
Download PDF →MIT-licensed. Reference specification, the whitepaper, and the AI-readable llms.txt format.
View repository →Built on LAA: Klair.work — the first multi-tenant platform implementing LAA across all its professional AI workers.