Quesarby MLAI

Start

Different tools. Clear roles.

Separate runtime, storage, interface, and application framework responsibilities.

Runtime and storage

ABI’s README describes local orchestration, runtime primitives and WDBX integration. WDBX addresses the storage and retrieval side of that work. Their relationship does not imply that every operation is persistent or that a production cluster is deployed.

The README explicitly allows persistence to be disabled or unavailable, and requires those conditions to be reported rather than presented as successful writes. A diagram cannot establish operational behavior; the relevant source and tests must do that.

Interface and identity

Abbey is the primary companion profile described by the source. Aviva is a direct expert mode, while ABI also names the orchestration/governance layer. These identity roles should not be mistaken for separate, independently verified models or repositories.

The existing Quesar platform also separates product and persona visual identities. For example, an ABI product accent does not define the color of an Abi persona. The distinction matters in content models as well as interface design.

A separate framework track

Gama’s README describes Swift scenes and a retained render tree driving different interface backends. This is an application-framework track, not a required component of the conceptual Abbey–ABI–WDBX relationship.

Keep project-specific build instructions and evidence separate. A passing web build does not prove a Swift target works; a local runtime test does not validate a mobile app, a hosted deployment, or a live provider integration.

  • ABI README

    Source description, tool commands and stated limitations; not a reproduced test run.

  • Abbey identity specification

    Further reading linked by the ABI README; not separately audited here.

  • Gama README

    Documented framework architecture, not independent platform acceptance.

Checked against these sources on .

All docsPrevious: Start with the source.Next: ABI runtime, as the tree actually ships.
Architecture

Next

Developers

The READMEs these articles cite.