Systems
Understand Abbey, Aviva and ABI without confusing identity with implementation.
The ABI README describes Abbey as the primary empathetic-polymath profile, Aviva as the direct expert mode, and ABI as the orchestration/governance layer. The linked identity specification contains the preserved declaration and a Current/Partial/Proposed mapping.
Those are source-described interaction roles. They should not be presented as proof of three separately deployed models, standalone commercial products, consciousness or unlimited autonomous capabilities.
An interface should make its actions and limits legible. A helpful tone and a persona name cannot substitute for permission, a working integration, or an accurate report of what happened.
ABI links a companion repository for Abbey. That reference is useful, but it does not establish the companion’s present deployment state or test health. Its current build was not independently assessed here.
When evaluating an identity-related feature, ask for the implemented behavior and evidence relevant to it. Keep design intent, source description, reported testing and independently measured outcomes as separate statements.
Source description, tool commands and stated limitations; not a reproduced test run.
Further reading linked by the ABI README; not separately audited here.
Checked against these sources on .