Local evidenceFormat and character rules + Checksum/control replay
Browser-checkable work only
BoundaryNo live source proof
Official state remains external
Why this exists
Know what can be trusted before wiring the value into production.
Switzerland AHV / AVS pages in ValidoHub are tool-first. This reference layer explains the checks, fixtures, developer handoff, and source-system limits so teams can integrate the live workbench output deliberately.
Use forImplementation planning
Choose normalization, storage, masking, and fixture strategy.
Use forQA and CI fixtures
Keep pass, review, malformed, and edge examples beside the code.
Use forDeveloper handoff
Copy the live tool JSON instead of reverse-engineering display text.
Browser checks
Local evidence the workbench can expose.
CheckFormat and character rules
Use the workbench for current evidence.
CheckChecksum/control replay
Use the workbench for current evidence.
CheckField anatomy and parser evidence
Use the workbench for current evidence.
CheckBatch and import debugging
Use the workbench for current evidence.
Official boundary
Where local validation must stop.
BoundaryOfficial existence or legal status still belongs to the authority or source system.BoundaryInputs stay browser-local; treat copied output as developer test data.
Integration traps
Small mistakes that create expensive debugging later.
TrapDo not treat a valid checksum as proof that the value exists in an official registry.TrapKeep display strings, compact storage values, masked output, and exported JSON separate.TrapNever log raw personal, payment, or secret values when masked output is enough.
Run the workbench
Open AHV validator
Validate, generate, inspect, copy, or export the current value in the browser.