AnyValid
Research prototype on validation against authoritative sources
Can a claim, an identifier or a status be validated against an authoritative source, and is that validation still current?
Overview
20tests in the repository
AnyValid asks an authority, through an adapter, whether a claim holds, and records the answer as a validation with a lifetime. Validations expire, and revalidation opens a new case that supersedes the old one instead of editing it.
Its discipline is keeping non-answers apart from answers. An authority that did not respond is not a negative result, and neither is an authority for which no adapter exists. Both open a task for a person.
The six prototypes share one application kernel in the AnyLAI repository: cases, a hash-chained event timeline, evidence with provenance and three timestamps, tasks and authority acts. Each prototype adds only its own vocabulary and rules.
Validation lifecycle
Company registration number
answers
not answers
↻ revalidation: new case
PENDING
Six states, not interchangeable. Only VALID and INVALID are answers.
Text description of the diagram
A validation starts as PENDING. The authority can answer VALID or INVALID. If the authority did not answer, the state is ERROR. If no adapter exists for that authority, the state is UNAVAILABLE. ERROR and UNAVAILABLE each open a task for a person. A VALID validation becomes EXPIRED when its lifetime ends, and revalidation opens a new case that supersedes the old one.
Building blocks
Validation request
A claim to check, and the authority that is competent for it.
Adapter
The connection to one authority, in live or reference mode.
Validation state
PENDING, VALID, INVALID, EXPIRED, ERROR or UNAVAILABLE.
Lifetime
When a validation stops being valid, and when it should be revalidated.
Human fallback
A task opened whenever the authority cannot give an answer.
A registration number
- 1
A supplier's registration number is sent to the competent registry through its adapter.
- 2
The registry does not answer in time: the state is ERROR, and a person is asked to check by hand.
- 3
A later request succeeds: VALID, with a lifetime of one year.
- 4
After a year the validation is EXPIRED, and revalidation opens a new case.
How it differs
AnyValid ≠ AnyVerifyResearch prototype · unpublished
AnyVerify compares evidence already at hand. AnyValid asks an authority from outside.
AnyVerifyAnyValid ≠ Trust ArchitectureImplemented platform architecture
In the Trust Architecture, a validation is one kind of evidence; it does not replace review.
Trust Architecture
Status
Research prototype in the AnyLAI repository. The lifecycle runs over one reference adapter that reads a fixture; no real authority is integrated. Unpublished and not deployed.
Limitations
- No real authority is connected; records are marked as reference mode.
- Nothing expires or revalidates on a timer yet, because there is no scheduler.
- A validation reflects what an authority said at a moment, not a permanent truth.