secryst crystals: native SECRYST_* env vars (rename outright, pre-publication) - #14
Merged
Conversation
added 3 commits
August 20, 2026 14:12
The strict release gate requires anchored RESULTS.md sources; record the gate numbers in docs/RESULTS.md and point metadata + metrics-sources.yaml at the anchor.
…che/secryst default (unpublished, rename outright)
ronaldtse
force-pushed
the
feat/secryst-native-env
branch
from
August 20, 2026 06:13
d0b0c3a to
628875b
Compare
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.
What
The secryst crystal family gets native environment variables, from scratch:
Nothing was published under the old names (interscript-ml 0.1.0 unpublished,
npm names unregistered), so this renames outright with no aliases.
Why
Contract vs implementation split: the interscript-ml contract (models.yaml,
IMF v1, model IDs) keeps its descriptive name; the three crystals that
implement it (Python secryst, Ruby secryst gem, TS @secryst/ml) carry the
secryst brand, so their env vars are SECRYST_*. runtime/README.md now names
the crystal family and notes the upcoming home repo secryst/secryst-py.
Verification
python3 -m pytest runtime/tests -> 12 passed, 1 skipped (E2E requires a
real IMF zip via SECRYST_E2E_ZIP, unchanged behavior).