Architecture
From request to record, with every layer named.
Select a component to see what is current in source versus what is not claimed. Motion on the connectors is a reminder that work flows; it is not a performance graph.
Select a node. The inspector lists implemented scope and the claims this site refuses. Field notes need the server deployment.
Architecture. Use arrow keys to move between components. Enter selects. The inspector lists what is current in source versus what is not claimed.
Reading the diagram
Input, processing, memory, retrieval, execution, tools, output.
The layers are a map, not a marketing stack. If a name sounds larger than the implementation, the status label is the correction.
- 01
User → Quesar
For the experimental website builder, the browser pairs with an operator-owned Quasar service. Generation requires separate provider configuration.
- 02
ABI + tools: a separate integration path
ABI's inspected sources provide deterministic persona routing and MCP tools. The Quasar builder does not establish an integration with ABI.
- 03
Persona routing and completion
The inspected local router selects a persona profile; template completion does not establish execution of a registry model on a selected device.
- 04
WDBX
WDBX implements durable records, vector retrieval, and structural provenance. Evidence-weighted retrieval remains unimplemented.
- 05
Local / edge / remote compute
The compute substrate provides CPU vector operations. Separately, configured website model requests and Quasar generation can send content to model providers.
- 06
Output
A response, a plan, a tool result, or a refusal. Abbey will not claim what the ledger cannot prove.