Repository navigation
docs: installed-build samCommit/runnerCommit hold the SAM_Deploy revision (S06) - #16
Merged
michaldengusiak merged 2 commits intoOct 20, 2026
Merged
Conversation
…sion (S06) Owner-accepted S06 limitation: document that SAM_Deploy installer builds report the SAM_Deploy build revision in both fields, how to recover the repository revisions from its gitlinks, and that existing records keep their meaning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…st (S06) Review fix: provenance.application.sourceRevisionOf is explanatory text. The full stamp is in entryAssembly.informationalVersion and components[].informationalVersion; sourceRevision holds the extracted SHA. Verified against the committed genuine-installer manifests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
S06: revision fields in installer builds (docs only)
This is the documentation part of roadmap S06's accepted provenance limitation (owner decision, 2026-10-20). No new stamping is implemented.
docs/benchmark/SCHEMA.mdnow states that a producer run from a SAM_Deploy installer build, without overrides, writes the SAM_Deploy build revision intosamCommitandrunnerCommit. It does not write the SAM or producer repository revision there. The reason is that every assembly is stamped<year>.<quarter>.<run>.0+<SAM_Deploy revision>.The new section also covers:
git ls-tree <SAM_Deploy revision> SAM SAM_Tas SAM_OpenStudio.<year>.<quarter>.<run>.0+<revision>. SAM_UI's run manifest records it underprovenance.application: the full stamp inentryAssembly.informationalVersionand eachcomponents[].informationalVersion, and the extracted SHA insourceRevision.sourceRevisionOfis explanatory text only. Headcb84fd9wrongly said the stamp was insourceRevisionOf;ed7a878corrects this. The values were checked against the committed genuine-installer manifests in SAM_Deploy#66.SAM_COMMIT(S05 and earlier) hold repository revisions, and no historical value is redefined.Evidence: SAM-BIM/SAM_Deploy#66. The installed S06 candidate
717533creportedsamCommit=runnerCommit=717533c. Its gitlinks give SAMdf27563b, SAM_Tase84aeff6and SAM_OpenStudio1f4bf60c.Record:
docs/benchmark/S06-INSTALLED-PROVENANCE-PR.md.cb84fd9ed7a878(current)Do not merge before owner approval. SAM_Deploy's SAM_Validation gitlink stays at
68eded00, because this change ships no binary.🤖 Generated with Claude Code