Clarify config/environment as sealed inputs in design spec#42
Merged
WhatsYourWhy merged 1 commit intoJan 28, 2026
Merged
Conversation
WhatsYourWhy
deleted the
codex/document-repository-structure-and-entry-points
branch
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
1 participant
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.
Motivation
Stateis the runtime-mutable representation while configuration and environment inputs (e.g.config.json,env.json) are sealed, hashed, and referenced from theledgerso contributors don't argue about whether config belongs inState.Description
docs/DESIGN.mdunder section 2.2 (Explicit State Invariant) specifying that configuration and environment inputs must be fully serialized, hashed, and referenced from theledgerand must not change during a run.Testing
Codex Task