Receipts / non-claims / inspection
Evidence.
The public record should make it possible to tell what actually ran, what merely exists as a design, what failed, and what remains unknown.
01 / Rule
Narrative does not promote state.
A persuasive description cannot turn a specification into implementation, a local test into independent validation, or a synthetic demonstration into product readiness.
Where public claims depend on implementation, the preferred evidence is inspectable: source, tests, hashes, manifests, run reports, recorded terminal conditions, and adverse evidence.
claim → source or artifact → validation boundary → falsifier → non-claim02 / Public surfaces
Where to inspect.
Undomesticated AI is the founder/research surface. ANANS has a separate public system surface. The source for this publication is public as well.
01
ANANS public site.
anansai.org
anansai.org
02
ANANS public site repository.
DrBlacks-lab/Anans-AI-anansai-site
DrBlacks-lab/Anans-AI-anansai-site
03
Undomesticated AI source.
DrBlacks-lab/undomesticatedai.com
DrBlacks-lab/undomesticatedai.com
03 / Non-claims
What publication here does not establish.
- External validation.
A public artifact can be inspected; that does not mean an independent party has validated the underlying system. - Production readiness.
A working local slice, demo, or test result is not equivalent to operational readiness. - General autonomy.
A bounded workflow does not prove unrestricted or reliable autonomous operation. - Canonical admission.
Publishing a candidate does not promote it into ANANS canon or grant it execution authority. - Completeness.
The public surface intentionally excludes confidential and trade-secret material.