contract identity: README system map + normative SPEC.md - #18
Merged
Conversation
…s; SPEC.md normative v1; runtime sample imports secryst
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 contract repo needs an identity README: the current one still says
interscript/ml-models and describes a training framework that was
superseded by interscript-ml-train. This PR gives the repo its actual
role description:
depends on nothing; crystals depend only on the contract; engines
depend on crystals optionally; training is consumed by the zoo),
repository table incl. archived rababa origins.
index schema, resolution algorithm, IMF v1, byte tokenizer, env)
that the secryst.org spec page renders for users.
(from secryst import Model) instead of interscript_ml.
Docs-only; no code paths touched.