FAQ¶

Is AR a database?¶

No. AR is an export, profile, verification, and conformance contract. A system may store data however it chooses.

Is AR an API standard?¶

No. AR does not define runtime APIs. It defines accountable exports and the structures needed to verify them.

Does AR decide truth?¶

No. AR preserves structure so claims, sources, evidence, interpretations, mappings, and verifier results remain inspectable. It does not decide truth.

Does AR replace domain standards?¶

No. AR is designed to work with existing standards through mappings and profiles.

Does a system need full conformance immediately?¶

No. AR supports incremental maturity levels. A system may start with bundle shape and add stronger structure over time.

Can proprietary systems use AR?¶

Yes. A proprietary system may use private packages and profiles while preserving AR identity, package, lock, digest, verification, and conformance semantics.

When is AR useful?¶

AR is useful when records must remain usable under persistent disagreement.

When ordinary schema validation is enough, AR may be more structure than the system needs.