Skip to content

Clarify config/environment as sealed inputs in design spec #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
WhatsYourWhy merged 1 commit into from
Jan 28, 2026
Merged

Clarify config/environment as sealed inputs in design spec #42

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/DESIGN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,10 @@ If this is not true, the runtime is broken.

All mutable information must be represented in the State object.

Configuration and environment inputs are considered sealed execution inputs and must be
fully serialized, hashed, and referenced from the ledger. They may influence execution,
but they must not change during a run.

Forbidden:

Hidden globals
Expand Down