Skip to content

feat(step-up): approve a step-up from a trigger link, as the person (VTI-LNK-125 – VTI-LNK-131) - #427

Merged
stormer78 merged 1 commit into
mainfrom
feat/step-up-flow
Nov 8, 2026
Merged

stormer78 merged 1 commit into
mainfrom
feat/step-up-flow

Conversation

@stormer78

Copy link
Copy Markdown
Contributor

Why

A person's assistant over vtc-mcp acts with a key they delegated. That key can redeem a VTC step-up but never make one. Since OpenVTC/verifiable-trust-infrastructure#2490, the community refuses such a party with a single-use handle, and the party shows the person a step-up link (trustoverip/dtgwg-vti-spec#106). This PR is the wallet's reader for that link.

What

  • Core
    • Pins auth/step-up/requests/show/0.1 and adds the step-up flow with its four reasons.
    • vtc/step-up-handoff.ts reads the step-up from a fresh key with the handle.
    • It checks that the request inside the reply was signed by the community, is addressed to its subject, is unexpired, and is bound to the operation returned (VTI-LNK-130).
  • Extension
    • step-up-flows.ts runs in the offscreen document. It reads a step-up only for a community the wallet holds an identity at, and checks that the subject is one of them. It sends the answer, signed by the agent as the subject, to the community directly (VTI-LNK-131).
    • The background reuses approveStepUp's check, approver prompt and signature.
    • The prompt shows the identity from the wallet's record. It labels the community's reason as signed by the community.
  • Entry points
    • A paste field in the popup, accepted from extension pages only.
    • A click on a page, which handleTriggerLink now routes away from the sign-in window.
    • The outcome is shown as a notification, because the popup closes when the prompt opens.
  • CLAUDE.md gains a section on the flow and what breaks it.

Checks

Run Result
npm run lint clean
npm run build MV3 bundles built
npm test every workspace green

New tests:

  • core/tests/vtc.step-up-handoff.mjs, 7 tests.
  • extension/tests/step-up-flows.test.mts, 7 tests.

Two existing tests changed. The parser's unknown-flow example now uses another flow name. The task-surface census gains an entry for the read, because it goes to the VTC, not the VTA.

Not yet run live against a community.

…VTI-LNK-125 – VTI-LNK-131)

Someone acting for the person with a key they delegated, such as their
assistant over vtc-mcp, can redeem a VTC step-up but never make one. The
community now refuses such a party with a single-use handle beside the
inline request, and the party shows the person a `step-up` link
(trustoverip/dtgwg-vti-spec#106, OpenVTC/verifiable-trust-infrastructure#2490).
This is the wallet's reader for that link.

core:
- Pins `auth/step-up/requests/show/0.1` and adds the `step-up` flow to the
  reader's flows.
- Adds the flow's four reasons: `not-in-records`, `not-the-subject` and
  `binding-mismatch` (outcome `invalid`), and `step-up-gone` (outcome
  `expired`).
- vtc/step-up-handoff.ts builds the read from a fresh key with the handle. It
  checks the reply's request is an approve-request the community signed, to
  its subject, unexpired, and bound to the returned operation. It also builds
  the subject's approve-response.

extension:
- step-up-flows.ts, in the offscreen document, reads the step-up only for a
  community the wallet holds an identity at. It checks that the subject is one
  of them, and sends the answer, signed by the agent as the subject, to the
  community directly.
- The background runs the same check, approver prompt and signature as
  approveStepUp. The prompt shows the identity from the wallet's own record
  and the community's signed reason.
- The person opens a link by pasting it into the popup (extension pages only)
  or by clicking it on a page. The outcome is shown as a notification.

Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
@stormer78
stormer78 merged commit 2856b51 into main Nov 8, 2026
4 checks passed
@stormer78
stormer78 deleted the feat/step-up-flow branch November 8, 2026 12:52
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