SaaO / Framework
SaaO reference architecture
This architecture describes the layers a complete SaaO system (Level 3) needs. It is provider-agnostic and stack-agnostic: any implementation that fulfills each layer's responsibilities is valid. Concrete implementations live in the directory.
The five layers
- LAYER 5
INTERFACE
Channels through which the client asks and receives: voice, chat, web dashboard. The client never sees the layers below.
- LAYER 4
GOVERNANCE
Verifiable agent identity, intent declaration, immutable audit, governed agent-to-agent communication. Produces the Software Passport.
- LAYER 3
ORCHESTRATION
A meta-agent coordinates the work: receives the request, breaks it into workflows and assigns specialized agents.
- LAYER 2
SPECIALIZED AGENTS
Software lifecycle roles as agents: strategy, product, design, architecture, frontend, backend, data, QA, security, DevOps, release, support.
- LAYER 1
RUNTIME
The environment where agents execute. Any agent framework works if it supports the layers above.
Implementation principles
The governance layer wraps all others: no action in layers 1 to 3 happens without identity, intent and record.
Human gates (Level 2) sit between orchestration and execution, at fixed, auditable points, never ad hoc.
Blueprints live outside the runtime: they are the asset, the runtime is replaceable.
The interface speaks the language of the business, never the language of infrastructure. The client asks for outcomes, not deployments.
Neutrality note
This site does not promote a stack. Implementation examples (agent frameworks, governance protocols, runtime platforms) are listed in the directory as references, including the reference implementation maintained by the framework's author.