Skip to content

feat(ml-api): stamp predictions with model version and audit reloads - #1018

Open
pavsoss wants to merge 2 commits into
Userunknown84:mainfrom
pavsoss:feat/1007-model-provenance
Open

feat(ml-api): stamp predictions with model version and audit reloads#1018
pavsoss wants to merge 2 commits into
Userunknown84:mainfrom
pavsoss:feat/1007-model-provenance

Conversation

@pavsoss

@pavsoss pavsoss commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Summary

Completes the provenance story from part 1/2 by tying runtime activity to the model version.

  • /predict and /importance responses carry an additive model_version.
  • A model hot-swap emits a structured audit line model reloaded vN -> vN+1 with old/new checksums.

Test plan

Coverage that /model-info version increments after /reload-model and that a prediction reports the new version.

Dependency

Builds on #1007 part 1/2 (feat/1007-model-registry); merge after it. Until then this PR's diff includes part 1's commit.

Part 2/2, Closes #1007.

@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

@pavsoss is attempting to deploy a commit to the Aditya Sharma's projects Team on Vercel.

A member of the Team first needs to authorize it.

@Userunknown84 Userunknown84 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.

Merge Conflict Show Kindly fix this.

@pavsoss
pavsoss requested a review from Userunknown84 July 29, 2026 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Model registry & provenance — /model-info, artifact checksums, and per-prediction version stamping

2 participants