Point the wiki at the repository's current name
Twenty-six links still said object-digital-passport/object-digital-passport.
GitHub redirects a renamed repository, which is exactly why nobody noticed: the
links worked, they were just wrong, and a redirect is not something to build a
front door on.
One was genuinely broken rather than merely stale — REQUIREMENTS_FIELDS_V0.6.md
moved under docs/ru/ and the link had not followed it.
Links to object-digital-passport.github.io are untouched: that is a different
repository whose name happens to start the same way.
Stop telling readers that Android support works today
This page said, in both languages, 'Full support today: reading, EV2
challenge-response, TagTamper status, and chip provisioning via the Android
companion app', and concluded that the cryptographic chip check 'currently
requires an Android device'. None of that is true. The Android verifier was
started and never finished, it is not published, and no ODP application
performs the chip check on any platform.
This is the friendliest document the project has — the one a person reads
before deciding whether to buy tags. It was the worst place for that claim.
Rewritten around what a reader actually needs to decide with:
- A warning up front. Of every anchor type ODP defines, nfc is the only one
with nothing installable, and someone about to order NTAG 424 DNA tags for a
run should learn that from us, before the invoice.
- What already works with no app at all — the chip carries a URL, so a tap
opens Verify and the document-level check runs. That is most of the value
and it was buried under the false part.
- Each platform separately: iOS is where the reference implementation is being
built and Core NFC makes it possible; Android is equally capable and its
attempt is unfinished; no Mac has ever had an NFC reader, so a Mac receives a
verified result from the phone and cannot scan.
- Provisioning honestly: there is no ODP tool anywhere. NXP's TagWriter writes
the carrier and Tag TrustLink authenticates a chip, but neither binds a chip
to a passport, which is the whole missing step.
The high-assurance sentence now names a verifier rather than the companion,
matching SPEC §6 after object-digital-passport#112.
Align wiki with the actual v0.6 model (card, anchors[], events, seals, assurance tiers)
wiki: fix demo/spec links (valid before and after Pages split)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
wiki: flags in language bars and sidebar
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
wiki: English-primary language convention
Translations renamed to lowercase ISO codes (Home-ru, ...); standard
language bar on every page; sidebar links only each language's Home
so it scales to many languages; RU intro removed from English Home.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
wiki: friendly bilingual docs (EN + RU)
Home, Quick Start, How Verification Works, NFC Seals, Object ID
Profile, FAQ — each in English and Russian, with a language sidebar.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>