Skip to content

feat(readiness): add verified evidence ledger - #375

Merged
VarshithReddy2006 merged 1 commit into
mainfrom
codex/issue-344-evidence-ledger
Nov 16, 2026
Merged

VarshithReddy2006 merged 1 commit into
mainfrom
codex/issue-344-evidence-ledger

Conversation

@vbtgongithub

Copy link
Copy Markdown
Collaborator

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.

Signed-off-by: VBTG <vuppubhanu18@gmail.com>
@vbtgongithub

Copy link
Copy Markdown
Collaborator Author

@VarshithReddy2006 I have implemented the changes for this issue. Please review my changes and merge this PR if everything looks good.

@VarshithReddy2006 VarshithReddy2006 added enhancement New feature or request help wanted Extra attention is needed nsoc26 level3 10 points - core logic, database changes, and complex features. labels Nov 16, 2026

@VarshithReddy2006 VarshithReddy2006 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

LGTM! Verified verified evidence ledger schema with compound uniqueness on ResumeEvidenceClaim and ledger migration with all tests passing.

@VarshithReddy2006
VarshithReddy2006 merged commit c4e0ffe into main Nov 16, 2026
5 checks passed
@VarshithReddy2006
VarshithReddy2006 deleted the codex/issue-344-evidence-ledger branch November 16, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request help wanted Extra attention is needed level3 10 points - core logic, database changes, and complex features. nsoc26

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(readiness,m6): implement verified evidence ledger schema with compound uniqueness on ResumeEvidenceClaim

2 participants