Skip to content

fix: Move DID anchoring provenance to registration#704

Merged
macterra merged 1 commit into
mainfrom
agent/issue-702-registration-provenance
Jul 9, 2026
Merged

fix: Move DID anchoring provenance to registration#704
macterra merged 1 commit into
mainfrom
agent/issue-702-registration-provenance

Conversation

@macterra

@macterra macterra commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

Fixes #702.

  • omits method-specific anchoring provenance from conformant /1.0/identifiers/{did} metadata
  • removes didDocumentMetadata.confirmed and didDocumentMetadata.timestamp from the conformant DID Resolution result
  • exposes confirmed and timestamp through /1.0/identifiers/{did}/registration alongside the registration resource
  • keeps TypeScript and Rust Gatekeeper surfaces aligned
  • updates Gatekeeper docs and generated Gatekeeper OpenAPI descriptions

Validation

  • node --experimental-vm-modules node_modules/.bin/jest tests/gatekeeper/api.test.ts --runInBand --verbose
  • cargo test --manifest-path rust/services/gatekeeper/Cargo.toml --test http_contract -- --nocapture
  • npm run generate-openapi

Note: the Rust test run still reports the existing unused import warning for queue_outbound_operation in rust/services/gatekeeper/src/lib.rs.

@macterra macterra changed the title Move DID anchoring provenance to registration fix: Move DID anchoring provenance to registration Jul 9, 2026
@macterra macterra requested a review from Copilot July 9, 2026 14:09
@macterra macterra marked this pull request as ready for review July 9, 2026 14:09

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates Gatekeeper’s standards-conformant DID Resolution surface to keep /1.0/identifiers/{did} “fixture-friendly” by removing method-specific anchoring provenance from didDocumentMetadata, and instead exposing that provenance via the dereferenceable registration resource at /1.0/identifiers/{did}/registration. It aligns the TypeScript and Rust implementations and updates the Gatekeeper documentation/OpenAPI output accordingly.

Changes:

  • Remove didDocumentMetadata.confirmed and didDocumentMetadata.timestamp from conformant /1.0/identifiers/{did} responses (TS + Rust) and adjust tests to lock this in.
  • Augment /1.0/identifiers/{did}/registration to include confirmed and timestamp alongside the registration resource (TS + Rust).
  • Update Gatekeeper docs and generated OpenAPI description to document the new provenance location and rationale.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
tests/gatekeeper/api.test.ts Updates Jest expectations to ensure conformant resolution omits anchoring provenance and /registration returns it.
services/gatekeeper/server/src/identifiers-router.ts Removes confirmed/timestamp from conformant didDocumentMetadata and builds an augmented registration resource for /registration.
rust/services/gatekeeper/tests/http_contract.rs Updates Rust HTTP contract test to assert provenance is omitted from conformant resolution and exposed via /registration.
rust/services/gatekeeper/src/api.rs Mirrors the TS behavior: strips provenance from conformant metadata and augments /registration output.
docs/services/gatekeeper/README.md Documents the provenance move: conformant resolution stays “boring”; /registration carries confirmation/timestamp details.
docs/gatekeeper-api.json Updates generated OpenAPI descriptions to reflect the provenance move and registration augmentation.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@macterra macterra merged commit b074893 into main Jul 9, 2026
29 checks passed
@macterra macterra deleted the agent/issue-702-registration-provenance branch July 9, 2026 14:20
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.

Move or document anchoring timestamp provenance in conformant DID resolution output

2 participants