Repository navigation
Plan content epochs — slices S129–S135 - #586
Merged
Merged
Conversation
Seven vertical slices against the Revision 2 contract: resolve-by-state first, then logged adoption proven on a test kind (the replay-exactness risk) before the archive, the story-graph rule, the session store's adoption points, saves and branches, and the replay oracle.
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.
Appends seven slices to
design/30-slices.mdfor content epochs (16-content-epochs.md, Revision 2, #584). This PR changes the plan only. No code changes.(campaignId, campaignVersion). AddsEngineHost.archiveandcreateGame(config, version?), anddeserializenow rejects a version that does not resolve (closes S125.5)LoggedEntry,Engine.adoptContentsteps 0–8,formatVersion: 2, the C26 checks, and §14 harness replay across an epoch, proven on a test kindcreateContentArchive: validated publish, content digest,content_version_conflict, frozen copies, and the channeladoptContent: the §8.1 additive rule, including the F2 node conditionSessionHost.content: adoption atsubmitActionandresumeSession, and the C27getStringsunionloadGameof an archived epoch without migration,LoggedMigration, andbranchSessionacross epochsAdoptionSubmissionandAdoptionDecision, the widenedcampaign_version_missing, and one corpus fixture that crosses an epochOrdering. S129 comes first because adoption needs resolve-by-state. S130 carries the riskiest assumption, that replay stays byte-identical across an epoch while v1 states are unchanged. It is proven before any shipped kind or host depends on it.
Verified:
./build/ConvertTo-HumanDocumentation.ps1regeneratedengine/TODO.md../build/Test-Documentation.ps1passed, including the drift check.git diff --checkis clean. The engine suite did not run because no code changed.