v2 draft outline
Outline only. Bullets list what this page will eventually cover.
Introduction (unnumbered)
What this page will cover
- Welcome and what the program is: immersive, hands-on, minimal lectures
- Who it is for: engineers and nontechnical learners alike
- What changes from v1 and why (one short list)
The arc
- Recognize good: operate a known-good factory, Emerald Grove Hotels (Module 1)
- Fix bad: convert a bad repo (Chaos Emerald Hotels) to good (Modules 2 and 3)
- Build your own: a factory from scratch for your project (Module 4)
Why start with good
- Analogy: bank tellers train on real currency so they can spot fakes
- You cannot spot what is missing until you have seen what complete looks like
- Short list of what "complete" looks like (previewed, taught in Module 1)
Factory vs. hacktory
- Hacktory: fast, disposable, exploratory
- Factory: reproducible, auditable, gated path to production
- Both are needed; the danger is a prototype that slides to production because it works
- Why it matters: risk, cost of rework, the prototype-to-prod shortcut
- Teach the reasoning, not a rule set
- Learners decide where their own line sits, and are asked to defend it
What you are aiming for
- The instinct to run a quality check before shipping
- Not tool mastery
- Defend your work: be able to explain each choice if questioned
How the program works
- Four weeks, four modules, 5 days each
- Every module ends in a demo of process, not just output
- Anything you approve (a plan, a summary) must be reviewable in a few minutes; otherwise send it back for condensing
Shared vocabulary (preview)
- Factory, hacktory, gate, reviewer, skill, context
- Link to the glossary
Before you start
- Accounts and access checklist
- Vercel org access is granted at Forge join
- Pointer to the Module 1 setup steps
TODO
- TODO: how much v1 setup material (accounts, install verification, MCP and skills setup) sits here vs. Module 1
- TODO: whether the hacktory vs. factory side-by-side rebuild survives as a short intro activity (parked on the overview)
- TODO: format for the "where is your line" exercise (written, discussion, or both)