Skip to content

Use unknown sentinel for missing model provenance - #114

Merged
NovasPlace merged 3 commits into
masterfrom
fix/honest-unknown-model-provenance
Sep 18, 2026
Merged

NovasPlace merged 3 commits into
masterfrom
fix/honest-unknown-model-provenance

Conversation

@NovasPlace

Copy link
Copy Markdown
Owner

Summary

When a memory write has no caller-supplied model identity, MemoryManager currently persists:

source_model_id = "default"

That looks like an attribution value even though no model identity was actually known.

This changes the fallback to the runtime's existing explicit sentinel:

source_model_id = "unknown"

Caller-supplied model IDs continue to win unchanged.

Scope

  • one production fallback literal
  • existing public/base provenance tests updated to require unknown
  • no historical rewrites
  • no schema changes
  • no governance eligibility changes in this PR

The provenance audit from #113 keeps separate counts for historical default placeholders and unknown values.

@NovasPlace
NovasPlace merged commit 9c7cfb2 into master Sep 18, 2026
8 checks passed
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