Repository navigation
feat(readiness): add verified evidence ledger - #375
Merged
Merged
Conversation
Signed-off-by: VBTG <vuppubhanu18@gmail.com>
Collaborator
Author
|
@VarshithReddy2006 I have implemented the changes for this issue. Please review my changes and merge this PR if everything looks good. |
VarshithReddy2006
approved these changes
Nov 16, 2026
VarshithReddy2006
left a comment
Owner
There was a problem hiding this comment.
LGTM! Verified verified evidence ledger schema with compound uniqueness on ResumeEvidenceClaim and ledger migration with all tests passing.
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
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.
Closes #344
I extended ResumeEvidenceClaim into a verified evidence ledger. Platform claims can be stored without a resume profile, and a compound unique MongoDB index gives concurrent upserts one row per user, subject type, and subject key. I added an authenticated GET /api/v1/evidence/claims endpoint with subject and verification-status filters. Existing resume reads stay scoped to resume claims and include rows from before the migration.
I added migration 0011 to backfill stable keys by document ID, preserving legacy rows with duplicate claim text. The README includes the migration and rollback commands.
Validation
I ran 41 targeted tests, including migration replay and rollback, concurrent upserts, legacy resume regressions, and HTTP ownership and filtering checks against disposable MongoDB. The backend typecheck passed.
Deployment and limitations
I did not run the migration in production. It should run with evidence writers paused. Rollback removes the index and the migration's changes to legacy rows while retaining newly written claims. If the application is also rolled back to a pre-ledger release, older resume queries can surface retained platform claims. Platform data producers still need to call the new upsert service.