Skip to content

Reframe Why VCALM as complementary to OID4, not a rival#10

Merged
djscruggs merged 1 commit into
mainfrom
fix/why-vcalm-framing
Jun 8, 2026
Merged

Reframe Why VCALM as complementary to OID4, not a rival#10
djscruggs merged 1 commit into
mainfrom
fix/why-vcalm-framing

Conversation

@djscruggs

Copy link
Copy Markdown
Collaborator

What

Rewrites the Why VCALM page (and fixes overlapping copy on what-is-vcalm) to drop the combative "VCALM vs. OID4" framing in favor of a "yes, and…" positioning.

Why

Editorial feedback on the page flagged that it was both too combative and not quite accurate:

  • "VCALM is an alternative to OID4VCI / OID4VP" is misleading — you can run OID4 over VCALM.
  • "one exchange loop" is misleading and not the point.
  • The "user vs. vendor" / them-vs-us framing forces a false choice.
  • OID4 is really only about the delivery phase; a credential-lifecycle diagram would show what OID4 covers vs. what VCALM covers.
  • Tone should highlight VCALM's strengths without turning the OID4 community away.

Changes

  • New lede leads with the real thesis: VCALM resists vendor lock-in across every phase of the credential lifecycle, and it can carry OID4VCI / OID4VP — a "yes, and," not an "instead of."
  • Added a lifecycle diagram: ISSUE → DELIVER → PRESENT → STATUS → REFRESH, showing OID4 covering the delivery hand-off and VCALM spanning all phases.
  • Added a "Real protocol choice — OID4 included" section; reframed the other sections from combat into VCALM-positive (OID4 as a subset you keep, not a rival).
  • Dropped the "one exchange loop" claim everywhere; changed "the user, or the vendor" → "you, or the vendor."
  • Updated the at-a-glance table, FAQ, and structured data to match.
  • Applied the same factual corrections to the overlapping copy + FAQ schema on what-is-vcalm.
  • Retitled the page from "VCALM vs OID4VCI / OID4VP" to "Why VCALM — vendor-lock-free credentials (works with OID4, too)" to match the new framing.

Notes

  • The page isn't linked from anywhere yet, so this is low-risk and easy to iterate on.
  • A broader editorial pass on the use-case pages was flagged separately and is out of scope here — deferred pending more direction.

🤖 Generated with Claude Code

The page positioned VCALM as an alternative to OID4VCI / OID4VP and
leaned on a "user vs. vendor" / "one exchange loop" framing that was
combative and not quite accurate.

Lead instead with the real thesis: VCALM resists vendor lock-in across
every phase of the credential lifecycle, and it can carry OID4VCI /
OID4VP over its exchanges — a "yes, and" rather than an "instead of."
Add a lifecycle diagram showing OID4 covering the delivery hand-off while
VCALM spans issue, deliver, present, status, and refresh. Soften the
comparisons to highlight VCALM's strengths without dismissing OID4, drop
the "one exchange loop" claim, and apply the same corrections to the
overlapping copy and FAQ schema on the what-is-vcalm page.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jun 8, 2026

Copy link
Copy Markdown

Cloudflare Pages preview

Deployed this PR to a live preview:

https://fix-why-vcalm-framing.learnvcorg.pages.dev

This deploy: https://9d46b56a.learnvcorg.pages.dev

Updated for commit 1d762f1.

@djscruggs djscruggs merged commit 64d8d7d into main Jun 8, 2026
1 check passed
@djscruggs djscruggs deleted the fix/why-vcalm-framing branch June 9, 2026 15:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant