Repository navigation
docs: simplify the 14-second batch demo into two messages - #269
Merged
Merged
Conversation
This branch was successfully deployed
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.
The loop required viewers to track ten work letters and changing captions before understanding its benefit. Keep two large messages visible for all 14 seconds: “Passing work lands first” and “Keep building during checks.” Emphasize passing work during repair, then turn the next-task message blue when overlapping work begins. Label actual new work “Next task” in the same agent lanes and group applied receipts by batch. The still poster uses the same layout. Stagger the opening return paths so cards do not cover headings or passing work.
Preserve the original 3.5.0 execution evidence, both overlaps, all three approvals, default rechecks, four persistent agent identities and replay continuity. Align README and landing copy with the same messages; distinguish batch landing policy from development shared by both modes.
Validation: 33 playback/evidence/story/geometry tests and three landing-page tests pass. Exports remain 14 seconds with 280 GIF frames and 336 H.264 frames. Keyframes, poster, EN/KO copy and desktop/mobile layout were reviewed. Full final train gates and production verification follow.