FAQs

A verified identity means the object identity and the authority to maintain it were checked. It does not establish technical or legal conformity. A separate scoped assessment may be verified only after all applicable controls are closed, independent review is complete and an authorised decision is recorded.

The ecosystem has valuable tools, but they are fragmented:

• VIN remains an external identifier that AUTOID preserves with its source and validity context; it is not altered or replaced.
• Safety tests provide a limited performance snapshot and do not function as a cross-domain identity layer.
• Homologation and approval records remain authoritative for their legal scope; AUTOID records their source, configuration applicability and check time.
• Manufacturer declarations vary in structure and comparability.

AutoID™ is designed to unify these elements into a clear identity and traceability layer — without creating new authority.

The accountable AUTOID operator and authorised functions defined by the adopted framework control allocation, assessment, decision and publication. A provider or regional node may act only within written authorisation and cannot issue an independent positive result beyond its delegated scope. Publication of the proposed First Edition alone does not activate the service.

AutoID™ is designed to avoid unbounded “everything” claims. A record covers only what is declared in scope. If deeper coverage is required, it can be represented through additional scoped records (e.g., a vehicle variant record plus a battery record), each with its own boundaries and evidence references.

AutoID™ is not designed to judge commercial quality, brand value, or market competitiveness. It also does not replace legal compliance decisions or act as enforcement. It focuses on identity, traceability, evidence logic and lifecycle status — within declared boundaries.

The assessment plan determines document checks, source authentication, sampling, site work, witnessing or physical verification according to the object, jurisdiction profile, risk and claimed outcome. Existing competent test evidence may be used when its provider, method, specimen, configuration and limitations are verified; AUTOID does not imply that IAF independently retested every requirement.

Yes. Unresolved identity evidence may leave identity disputed; an assessment may remain in_review, be refused, suspended or withdrawn. Missing evidence is not a pass, and a positive result requires every applicable control to be conforming or justified not applicable with blocking findings closed.

A single status would hide important distinctions. AUTOID therefore shows:

• Identity: draft, verified, disputed, suspended or retired
• Scoped assessment: not_assessed, in_review, verified, refused, suspended, withdrawn or superseded
• External legal source: separately reported with source and checked-at time
• Currency and safety: current, review_due or stale, plus separately recorded safety alerts

Without versioning, identity becomes confusing and trust becomes narrative-based. Versioning protects traceability, prevents silent change, and enables consistent interpretation.

Full evidence may include confidential technical detail, IP-sensitive documentation or restricted third-party reports. AutoID™ prioritises clarity and traceability: public summaries can indicate the nature of evidence references, while access layers protect sensitive content.

Homologation/type approval is a legal mechanism for market entry and compliance. AutoID™ does not make those decisions. It complements the ecosystem by providing a neutral identity and traceability layer that can improve clarity and comparability beyond minimum legal thresholds.

Safety ratings provide performance snapshots focused on safety. AutoID™ is not a safety score; it is an identity and traceability layer. AutoID™ can coexist with safety results by referencing them as evidence where relevant to scope — but it is broader and structurally different.