---
title: Architecture decisions
description: Route normative questions to the accepted current ADR sequence.
---

ADRs 0030–0074 in `LioRael/lenso` are normative for the current architecture. Start with these
decision clusters:

| Topic | ADRs |
| --- | --- |
| Reset, Capability packaging, bindings, interaction shapes | 0030–0035 |
| Diagnostics, identity, Auth, state ownership | 0036–0042 |
| UI, immutable Plan, activation, lifecycle, supervision | 0043–0048 |
| Portable values, codegen, Event and Stream semantics | 0049–0052 |
| Driver, implementation layers, native and Plugin Interfaces | 0053–0057 |
| Bun wire and streams, Web UI, OTel, game protocols | 0058–0062 |
| Execution Lanes and repository extraction | 0063–0064 |

ADRs 0001–0029 describe the retired v0.3 Service-oriented architecture. They
remain historical evidence and are superseded by the current architecture.

Use the [repository ADR index](https://github.com/LioRael/lenso/tree/main/docs/adr)
for decision text and supersession links.


| Additional topic | ADRs |
| --- | --- |
| Dynamic Plugin governance, source derivation, immutable transitions, configuration layers | 0065–0068 |
| One Plugin model and Plugin Roots | 0069–0070 |
| One Contract with multiple implementations | 0071 |
| Separate Access Control from Organization | 0072 |
| Named dependencies and persisted choices | 0073 |
| Host-essential terminal failure scope | 0074 |

Acceptance of an ADR does not mean every profile has implemented or released it.
See the [first 0073/0074 implementation status](https://github.com/LioRael/lenso/blob/main/docs/architecture/plugin-authoring-implementation-status.md)
and the [later Bun interaction support](https://github.com/LioRael/lenso-bun-adapter/blob/main/packages/lenso-bun-plugin/README.md).
