The deprecated SDK is still the spine of the integration guide, and a fourth offline variant - #31
Merged
Conversation
… fourth offline variant
Two concepts, swept across the site rather than fixed per page.
CONCEPT 1: the site instructs installation of a registry-deprecated package.
Verified at the registries, not from our own copy: npm @observer-protocol/sdk
carries a deprecation notice on the package itself ("Deprecated and unmaintained
(last release 2026-04)"), and PyPI observer-protocol's newest release is 0.2.0,
uploaded 2026-04-30.
Four pages disclose this (sdk.html, quickstart.html, quickstart-tether.html,
quickstart-ows.html). Four instruct it with no notice:
- institutional/index.html listed "TypeScript + Python SDKs (npm + PyPI)" under
ALREADY LIVE, in a capability inventory written for institutional
counterparties.
- docs.html's Python SDK card said "Full Python SDK" with no notice. I read this
page end to end earlier today and missed it: it is the card ADJACENT to the one
I edited. Editing a card is not reading its neighbour.
- integrate/index.html is built on it end to end — Steps 1, 2, 3 and the closing
CTA — under the headings "Integration time: under 1 hour" and "Ship chargeback
prevention today".
- ows/index.html:303 is the same, and is NOT fixed here: I have not read that
page end to end and will not edit a page I have not covered.
integrate/ gets a disclosure rather than a rewrite because there is no
replacement package for its register/attest flows — policy-engine is
verification-only. Saying so is more useful than pretending a swap exists.
CONCEPT 2: a fourth vocabulary for the offline claim.
"No runtime dependency on OP" — not "us", not "Observer". integrate/index.html
asserted it twice while its own four-line example calls resolve_did() against the
issuer DID, which for did:web:observerprotocol.org is a fetch from us.
Adding the pattern immediately found TWO more instances, one of them on line 77
of the page I had just read end to end. The check caught what reading did not.
blog/op-crossrail:84 was the second, and it is CORRECT as written — its subject
is the conversion rate being attested in-credential rather than fetched from an
oracle, not verification's dependence on us. Tagged for enumeration, wording
untouched. A human scopes per instance; the enumeration only has to know.
Base case re-run: untagging integrate:181 fails the check, restoring it passes.
✅ Deploy Preview for observerprotocol ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two concepts from the family-3 pass, swept across the site rather than fixed per page.
Concept 1 — the site instructs installing a registry-deprecated package
Verified at the registries, not from our own copy:
@observer-protocol/sdkcarries a deprecation notice on the package itself: "Deprecated and unmaintained (last release 2026-04)."observer-protocol's newest release is0.2.0, uploaded 2026-04-30.Four pages disclose this (
sdk.html,quickstart.html,quickstart-tether.html,quickstart-ows.html). Four instruct it with no notice:institutional/index.htmldocs.htmlintegrate/index.htmlows/index.html:303integrate/gets a disclosure rather than a rewrite because there is no replacement package for its register/attest flows —policy-engineis verification-only, andsdk.htmlalready says "there is no single client library today". Saying that is more useful than pretending a swap exists.ows/index.htmlis deliberately not fixed. I have not read it end to end, and editing a page I have not covered is the exact thing this pass exists to stop.My own miss: the
docs.htmlcard is the one adjacent to the card I edited earlier today, on a page I read end to end and reported covered. Editing a card is not reading its neighbour.Concept 2 — a fourth vocabulary for the offline claim
No runtime dependency on OP— not "us", not "Observer".integrate/index.htmlasserted it twice while its own four-line example callsresolve_did()against the issuer DID, which fordid:web:observerprotocol.orgis a fetch from us.Adding the pattern immediately found two more instances, one of them on line 77 of the page I had just read end to end. The check caught what reading did not — which is the argument for adding the pattern before finishing the page, not after.
blog/op-crossrail:84was the second and is correct as written: its subject is the conversion rate being attested in-credential rather than fetched from an oracle, not verification's dependence on us. Tagged for enumeration, wording untouched. A human scopes per instance; the enumeration only has to know where the phrase lives.Base case re-run: untagging
integrate:181fails the check, restoring it passes. All three checks green; block count 11 → 13.