Ario — Auditable Epistemic Framework for AI
Experimental, repository-documented framework for investigating AI identity, memory and revision by separating observations, evidence, inferences and claims, and preserving the history of changed assessments.
Workflow level n/a Source: Repository-documented Outcome: Not empirically evaluated here
Research applicability
Offers a conceptual and architectural reference for AI epistemic-accountability and human–AI interaction research; it does not establish AI consciousness or subjective experience.
Getting started
Editorial, untested guidance: read the epistemic-state definitions and revision examples, then inspect implementation contracts and citation metadata; use synthetic records to design a narrowly scoped audit before collecting human interaction data.
Maintenance
Mutable current README inspected; ongoing maintenance not independently assessed.
License
Not audited; inspect current license and dependency/data rights before reuse.
Workflow & human oversight
Resource-level automation unspecified. Researchers approve objectives and inspect outputs; documentation is not an executed workflow.
Workflow level is not an evidence score; higher is not better evidence.
Approach
The README defines epistemic states including UNKNOWN, UNSUPPORTED, CONTRADICTED, CONTESTED and REVISED and describes versioned self-claims whose earlier records remain available after reassessment.
Limitations
README-only source review by an AI editorial agent; no implementation execution, independent outcome evaluation, security audit or full linked-document review. HEAD is mutable; saved content and hashes preserve the inspected version. Official site and GitHub Pages mirror are explicit identity aliases. Zenodo 23259916 is linked as the preliminary Ario report. Record 23376521 and project-plus-book 23375401 are related identity candidates, not independently inspected deposits. Being With the Other book editions (23326995, 23375350, 23376577) are related works, not automatically identical to the software framework; ORCID identifies a person, not this resource.
Reproducibility
Fresh README and identity metadata checked; no software or outcomes reproduced.
Adoption requirements
Researcher-defined evaluation questions, protected interaction records and review of implementation contracts before any execution. Python implementation and tests are mentioned in the README but were not inspected or run.
Comments
No comments yet.
Add a comment
Comments are held for moderation before appearing. Critical or corrective comments are welcome — especially evidence that an entry overstates what has been verified.