docs: add schema migration rfc#234
Open
dmcilvaney wants to merge 22 commits into
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new developer RFC documenting a proposed “lazy schema migration” approach for component lock-file fingerprints, aiming to prevent repo-wide lock churn when config schema or fingerprinting logic evolves.
Changes:
- Introduces RFC 002 describing the problem (lock-file drift on additive schema changes) and a layered solution (omitempty-by-default inclusion + versioned fingerprint replay + future schema-version migration).
- Documents design rationale, alternatives considered, incremental delivery plan, and open questions for future implementation.
dmcilvaney
force-pushed
the
damcilva/schema_version
branch
from
a2712d3 to
4ee9260
Compare
…emission probe The coverage-invariant paragraph said the one maximal golden config 'doubles as the emission-probe input'. That holds only at the cutover: a golden vector freezes a config's digest, so the maximal config cannot grow, while the emission probe needs an every-measured-field-set input that grows with each additive field. Note the two-config split (frozen maximalConfig + growing emissionProbeConfig) and the additive-field workflow (set in the probe input, pin with a new <toml-key>-set vector, never edit the frozen maximal digest).
…ctuation Replace the stale 'extend the maximal vector' loop with the frozen-maximal / growing-probe workflow, and state which steps are hard CI gates (mandatory tag, projectV1 emission probe) versus the recommended-but-ungated golden vector. Also replace horizontal-ellipsis characters with ASCII '...' and one stray loanword accent; intentional diagram/math notation is left as-is.
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.
Possible implementation at #243