Terminology and Concepts to look out for

Folder 4 · final compressed proto-spec · reproducibility · durable artifact · form-as-repo

Relevance to Me

Your project's repo — your Google Form — has four days of writing in it. Today you take the reproducibility test. You open a fresh MuggsOfVibes session, paste folders 1, 2, and 3 from your form into the tool's boxes, and hit Compile. If the game returns as you built it this week, your spec is durable. Then you tighten those folders into one running paragraph, paste it into Folder 4.1 of the form, and submit.

The form is what gets graded. The paragraph in Folder 4.1 is what Mr. Muggivan pastes into an empty MuggsOfVibes to grade you.

Board Question

Chromebooks open to /vibes — click the link on Deck 2. No code, no password. Open your Google Form and hit "Edit your response" to see your running spec. Friday's test needs a clean session — no leftover HTML in memory — so open MuggsOfVibes in a new tab. A new tab always starts empty. Copy your complete proto-spec out of the form's Section 5, click Paste full spec, click Load into folders, and hit Compile once. Look hard at what came back. If the game returns as you built it, you have passed. If it does not, the gap between what you see and what you built is exactly what your writing is missing. Fix the folder that owns it, save, and run the test again. Then finish Section 5 — the assembled spec, what worked, and what you would change. Friday's exit ticket is the last thing you touch today.

You have four days of writing in your repo. Today you take the reproducibility test. Then you ship.

The test.

Your Google Form has four folders filled in — Overview, Playing Canvas, NPCs, Scripts — and Section 5 waiting. Today you check whether your spec, as it stands right now, actually produces your game. Here is how.

1. Open your Google Form and go to Section 5. Assemble your complete proto-spec there if you have not already: in the tool, click Copy full spec (all folders), then paste it into Section 5.
2. Copy that complete spec out of the form.
3. Open MuggsOfVibes in a new tab. A new tab always starts empty — that is what makes this a cold read.
4. Click Paste full spec, paste your spec in, and click Load into folders.
5. Hit Compile.

What comes back is what your repo produces, cold. Not what you accumulated across four days of iteration — what your final written spec, read alone, generates. This is the same thing Mr. Muggivan will do when he grades you.

Three things can happen.

1. The game comes back looking and playing like the game you built this week. Your spec is durable. You have passed the reproducibility test. Move to Folder 4 and reflect.

2. The game comes back close, but wrong in a specific way. A missing element. A color that is off. A behavior that does not fire. This is the most common outcome, and it is a gift — the specific wrongness tells you what your spec is missing. Go to the section of your form that owns that piece (Folder 3 for a missing element or a wrong color, Folder 4 for a missing verb), add a sentence that fixes it, save, and run the test again.

3. The game comes back looking nothing like what you built. This means your spec drifted — during the week, the tool built up detail your spec never captured. That is the pedagogy of this week. Chat is disposable; spec is durable. Whatever the tool added Wednesday that you did not write into your form, your form does not have. Which means Mr. Muggivan does not see it either. Rewrite the folders of your form that are missing the durable detail, save, and run the test again.

Compression, not rewriting.

If your form's spec is producing the game with the right shape, you are close to done. Read all four folders. Are there duplicated sentences? Sentences that could be tighter? An NPC note that repeats itself under Behavior? Tighten.

Compression is different from rewriting:

• Compression keeps intent, removes noise. "A paddle at the bottom, and a paddle just below the play area" becomes "A paddle, at the bottom of the play area." Same intent, tighter.
• Rewriting invents. Do not throw out four days of writing and start over. The specific words you wrote across the week are what actually landed in the tool. Keep them.

Use the tool to compress. Once your tree looks tight, click Copy full spec (all folders) at the bottom of the tool's Explorer. That button dumps every folder — Overview, NPCs, Interactive Components — as one Markdown block, with dividers between them. That block is what you paste into Folder 4.1 — Final compressed proto-spec.

Folder 4's three items.

• 4.1 Final compressed proto-spec. The whole game, as one block. This is what gets graded — Mr. Muggivan pastes exactly this into an empty MuggsOfVibes session and looks at what comes back.
• 4.2 What worked and what did not. One paragraph. Where did your writing produce what you meant? Where did it not?
• 4.3 What would you change if you had another week. One paragraph. Not a list of features; a reflection on how your writing skill grew.

Submit. That is the last edit your form takes.

What just happened this week.

You built a video game in English. You did not touch code. You wrote a specification into a form, refined it over five days, and along the way used a tool that turned your writing into a working page. The tool was temporary — every day it forgot what you did. The form was durable — every day it remembered. The tool is chat. The form is spec.

Any real engineering project you work on — for a class, for a job, for yourself — has this same shape. The chat around a project is disposable; the specification is what survives. You just built one of those specifications, and you have the paragraph to prove it works.

Submit. Reflect. Show up Monday for what comes next.