docs
patch
docs/track-agent-model-stale-plan
#1 / 2
docs: explain model_id mutability + why it's unvalidated (issue #132)
Added a new subsection to /muse/profiles (docs_muse_profiles.html) -- gabriel asked where the reasoning behind #132's fix approach should live, and this is the actual doc that already covers profile-page anatomy including the model field, just without explaining the semantics.
Documents: model_id reflects the most recently used model, not a genesis label frozen at first registration (the same agent identity legitimately spans multiple model versions over its lifetime as providers ship upgrades); why it's recorded per-commit rather than once on the identity; and why it's deliberately unvalidated free text rather than an enum (validation would block real commits referencing brand-new model releases the registry doesn't know about yet).
sha256:60c225c3bdb87131193431da383b289b435160cad9c901a2da437698267be4b8
sha
~4
symbols
sha256:3db196d00480465d2c7d938fc18375a222587f410e1577bf0da6ec03fb846375
snapshot
~4
symbols modified
0
dead code introduced
Semantic Changes
4 symbols
Older
docs: track issue #132's plan doc in-repo, not /tmp
sha256:4daf6fd53253770e2965c521fc1a56853d5516ac28aac4b10cb466ffc8ddf76d
All commits
Newer →
Latest on docs/track-agent-model-stale-plan
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:60c225c3bdb87131193431da383b289b435160cad9c901a2da437698267be4b8 --body "your comment"
No comments yet. Be the first to start the discussion.