Repository navigation
Add research behind the thirdshift explainer videos - #845
Merged
Merged
Conversation
Six notes in docs/research: what makes a narrated explainer clear, music and loudness, the terms and misconceptions a newcomer needs, tailoring by audience (engineers versus executives), a sound-off marketing cut, and a getting-started tutorial with the exact commands and real output to show.
Merged
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.
Summary
Research that shaped a set of thirdshift explainer videos (an executive cut, engineering cuts, a getting-started tutorial and a sound-off marketing cut). Docs only.
Each follows the folder's convention (research date, Question, Method, Out of scope, TL;DR, cited sections) and ends with checkable rules.
Evidence
prompts/fresh.md:12tells the opening session to open the pull request "marked ready for review", so the note now says the agent never decides whether the pull request stays ready, or merges (ADR 0004).in-progressat 04:21Z (00:21 −0400) and PR Refresh homepage for current factory workflows #665 merged at 05:22Z, matchingsite/index.html. That Run used codex, which the notes record so videos don't caption it as Claude Code.rgfor scratch paths, API key names and email addresses in the six files finds nothing.Merge Danger
Door: two-way
Blast Radius: none
Markdown under
docs/research/only; nothing generated, built or shipped reads it.