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.
Explain how to publish a profile ID so software can read it The wiki told people to publish their ID and left it there. Two things were missing: where software looks, and what a directory listing them is allowed to claim. New page in both languages covers the /.well-known/odp.json file, why scraping a rendered page is not good enough, directories and their limits, the rules an app must follow when evidence stops checking out, and affiliation for organizations with divisions. Quick Start now points at it from the step where a profile is registered. The part worth keeping: a site that fails to load is missing data, not a forgery. An app that shows those the same way accuses honest organizations over routine downtime.
Point readers at the second wiki, and say what each one answers The website got its own wiki. Nothing here mentioned it, so a reader whose actual question was 'the wallet button does nothing' had no route to the page that answers it, and would keep re-reading Quick Start, which does not. Quick Start now says at the top what it is: one worked example, using the reference website, of rules that hold for any implementation. The site-specific half — screens, buttons, wallet failures — lives in the site's wiki and is linked from the banner, from the sidebar, and from the table on Home. Both languages. Nothing was moved. Quick Start is still a complete walkthrough; a reader who only wants to issue one passport can stay here and finish. The link is for the reader whose question turned out to be about the tool rather than the standard.
Point at the live site, and say which version these pages describe Two things had gone stale since the 0.7 line, in opposite ways. Nine links still used the doubled path — object-digital-passport.github.io/ object-digital-passport/verify.html — from when the site was a subdirectory of the protocol repository. They resolve, but only through redirect stubs the protocol repository's Pages build keeps alive; the site itself has lived at the bare host since the split. Rewritten to the live addresses, all four checked for 200. And the wiki said nothing about v0.7 at all. It is not wrong to describe v0.6 — v0.6 is what is deployed and what every client talks to. But a reader who saw a v0.7 tag on the repository had no way to learn from here that it is a pre-release deployed nowhere, with no issuer tooling and no activation page. Home now says so in both languages, and says why the wiki will not grow v0.7 pages until v0.7 is deployed. Also retired the word 'demo' for the reference website. It stopped being a demonstration when it became the implementation the apps talk to.
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>
Initial Home page