what we build · part seven · closing
What just happened
Six phases. The brief was signed on a Tuesday. A few weeks later, a story is ready to pull. Between those two moments, the meaning the brief carried has crossed six gates — Epic kickoff, design shaping, technical shaping, the story map and walking skeleton, INVEST, and amigos. At each gate the team has had to choose: carry the meaning, or substitute it with the artifact's natural shape.
If they carried it, the story now in JIRA contains Gal's Tuesday afternoon as faithfully as text can. The Epic is named after the activity — and Gal is named in its description as the person whose situation it serves. The release the story belongs to is the smallest version of the change the brief predicted. The wireframe states — named for the moments the brief witnessed — reflect what was observed. The API contract enforces the brief's intent. The Gherkin Givens place the developer in Gal's situation. The scenario names will travel from the amigos session to the test file to the production incident, six months from now, when something breaks.
If they substituted instead — if the Epic became "Teacher Dashboard," if the story lost the named person, if the schema dropped the column that would have answered the question, if the Given started with "Given the Teacher is on the Results page" — the story now in JIRA looks fine. It will be built. It will pass review. It will ship. And nothing about Gal's Tuesday afternoon will change.