What's due, and what Satisfactory means.

Individual work

Graded per person. Your teammates' work doesn't help or hurt you here.

1. № 01

   Venture Log

   Weekly · Fridays 11:59pm · Google Form · 500–800 words · 11 entries

   • Evidence this week documented: interviews (with the team's running total), experiments, observations
   • Key decisions and pivots stated, with the reason
   • Assumptions tested: which one, how, result
   • Harness change this week: what you added or changed in your agent, and why
   • Touch-point status: which of the three run on real inputs
   • What's working, what's not, one thing you'd do differently
   • Reading-to-doing connection made
   • AI audit trail: tools, what you delegated, what you verified
   • Every field concrete. "Nothing this week" is Needs Revision.

   Named entries (all go in Key decisions, and why): 1 gift plan · 2 gift response · 6 pivot-persevere-abandon after the alumni panel · 9 post-competition synthesis · 10 go-to-market and unit economics.

2. № 02

   Gift-giving exercise

   Due Fri Sep 18 · Individual

   • A gift planned for a specific person for a specific reason, recorded in Entry 1
   • Delivered; the response recorded in Entry 2
   • One paragraph on what it taught you about giving before asking
3. № 02b

   Three inefficiencies (evidence)

   Due Fri Sep 11, 11:59pm, with Log 1 · Canvas · Individual

   • Three inefficiencies, each with: who does it (named organization and role), what the hands do, how often and how long, how you know, which bucket
   • At least one from a person you talked to, with a quote
   • None from a campus organization
   • Brought on paper Wed Sep 16 for team formation
4. № 03

   Harness Checkpoints (4)

   Mondays, Weeks 2–5 · Individual · skill, hook, rule, memory

   • The piece exists in your agent's configuration and runs without errors
   • You can state the design decision behind it in one sentence: what it does that a one-off prompt doesn't
   • Demoed to a classmate before you leave; classmate's name on the log entry
   • Written up in that week's Venture Log under "harness change"
   • The hook fires on its own in front of a witness. The rule shows an observable before/after. The memory design says what's kept and what's forgotten.
5. № 04

   Harness v1

   Due Mon Oct 19 · Individual

   • Skills, hooks, rules, and memory assembled into one system that runs your team's automation end to end
   • Runs on sample inputs at all three touch points
   • States which of gather, synthesize, sense-make, disseminate the agent owns at each touch point, and where the human decides
   • Prototype 1's hypothesis written down: the assumption, the result that would prove you wrong
   • Passes the evaluator's functional check
6. № 05

   Video Pitch Competition

   Thu Nov 19 · Individual · required event

   • Present with your team
   • Answer the judges' questions; any teammate may be asked anything
   • Feedback captured and synthesized in Entry 9
7. № 06

   Book-to-Venture Memos (2)

   Co-Intelligence: Fri Oct 30 · Minimalist Entrepreneur: Fri Nov 13 · 500–1,000 words · one for B, both for A

   • Two or three key ideas from the book, identified
   • Connected to your project with concrete examples
   • One specific action you'll take because of it
   • One question the book raised that you can't answer yet
   • Not a book report
8. № 07

   Final Reflection

   Due Fri Dec 11, noon · 1,500–2,500 words

   • Your journey mapped against the seven entrepreneurial thinking skills
   • Your most significant failure and what it taught you
   • Three moments your judgment about your agent changed, each cited to a specific Venture Log entry
   • Assumptions that changed from Week 1 to now
   • What you'd do differently
   • Where this applies beyond the course
   • Specific examples throughout, not generic learning statements
9. № 08

   Peer and Self Evaluation

   Due Fri Dec 11, noon · confidential Google Form

   • Ratings 1–5 for each teammate and yourself: contribution, reliability, collaboration, initiative
   • What each teammate did well
   • One change you'd make to how the team worked
   • Workload distribution, honestly
   • Your primary role and one improvement area

Team work

Shared credit. Two or three of you, one inefficiency, one design partner.

1. № 09

   Inefficiency Brief

   Due Fri Sep 25 · 2–3 pages

   • Design partner named; process owner named and their agreement to three meetings recorded
   • The inefficiency in two sentences: who does it, how often, what it produces
   • What it costs them now, in their words and their estimate
   • The ten-more-customers list: ten organizations that do this the same way, with a reason each would pay to stop
   • First sketch of three touch points
   • Initial assumptions ledger: every belief the project rests on, each marked untested
   • Data agreement with the process owner: what the harness may read, what it may send, who checks
   • Research plan: eight planned conversations and one observation session, each with an owner and a date
2. № 10

   Discovery Pack

   Due Fri Oct 9 · PDF plus raw notes

   • Eight conversations with real people who do or depend on this work. Not roommates, classmates, friends, or family.
   • Each conversation: date, who (anonymized), three or more verbatim quotes, surprises, follow-up questions. Recording with permission or typed notes.
   • Sixty minutes of observation of the process with field notes that record behaviors, not interpretations
   • Synthesis: needs, surprises, what changed your mind
   • Baseline numbers in the process owner's own terms: minutes per week, error rate, how often it's late
   • Assumptions ledger updated: what's now confirmed, what's killed
3. № 11

   Business Case

   Due Fri Oct 16 · one page

   • Who pays, and what the work is worth to them, in dollars or hours with the arithmetic shown
   • What it costs to run: tokens, tools, your time
   • Value proposition in one paragraph
   • Lean canvas
   • The ten, revisited: which of them you've talked to since the Brief
4. № 12

   Validation Report

   Due Fri Oct 30

   • Process owner has used prototype 1 and prototype 2; both sessions documented
   • Three or more test sessions with a plan: the question, who, the success criterion
   • Each prototype's hypothesis and what happened to it
   • What changed between prototypes and why, with the evidence
   • Evaluation results on twenty real inputs: pass, fail, and why
   • Assumptions ledger updated
5. № 13

   Pitch video

   Due Tue Nov 17, 11:59pm · three minutes maximum

   • The problem, in the process owner's words if you can get them
   • The automation running, on real inputs, on screen
   • The evidence: baseline, what changed, what the process owner said
   • The ten: why this is a business and not a favor
   • The ask
   • Every teammate on camera
6. № 14

   Deployment Log

   Due Fri Dec 4

   • The harness ran on the live process for at least five working days by the end of Week 11
   • What it caught, what it broke, what a person had to step in on
   • Baseline numbers from Week 5 next to the same numbers now
   • The process owner's signed statement of what it did
7. № 15

   Final Dossier

   Due Fri Dec 11, noon · 10–15 pages plus appendices

   • Executive summary (one page)
   • The inefficiency: who, what, why it matters
   • Discovery: methods, findings, quotes
   • Business case
   • Harness evolution: prototype 1 to deployed, with the touch-point diagram
   • Evidence of learning: what worked, what failed, pivots
   • Current state: what runs today and who runs it
   • What's next: roadmap, open questions
   • Team reflection: roles, conflicts, how you resolved them
   • Appendices: interview notes summary, eval results, deployment log, judges' feedback
   • Complete, evidence-based, specific, iterative, honest

Mastery options

Team work, shared credit, due Fri Dec 11 with the Final Dossier. Two for a B, four for an A. Each has hard minimums; "we tried" is Needs Revision.

1. M1

   External validation

   • Six or more conversations with organizations from your ten-more-customers list
   • Notes in the Discovery Pack format
   • Two-page synthesis: what confirms the market claim, what breaks it, what you'd change
   • Diverse organizations, not six branches of the same one
2. M2

   Second deployment

   • The harness runs in a second organization for five working days
   • What transferred unchanged, what didn't, what you changed and why
   • The second process owner's statement
3. M3

   Sell it

   • A real transaction of at least $5 with a real stranger for work your harness does
   • Stranger means not a roommate, classmate, friend, family member, or anyone who'd pay out of obligation
   • The pricing conversation, the transaction record, and the follow-up documented
4. M4

   Go-to-market experiment

   • Live landing page with a clear value proposition and a working sign-up
   • An outreach campaign you actually ran: channels, number reached, the scripts
   • Metrics report: visitors, sign-ups, conversion, response rates, what you learned about demand
   • Honest numbers, even if disappointing
5. M5

   Technical hardening

   • An eval suite of forty or more real inputs with pass/fail criteria
   • Run before and after a change to the harness; both result sets reported
   • Every failure explained; the ones you chose not to fix, justified
6. M6

   Handoff manual

   • Documentation good enough that the process owner's colleague can run and maintain the harness without you
   • Tested: they do it while you watch and don't help. What they got stuck on, recorded and fixed.
7. M7

   Operations plan

   • Three potential partners: who, what you need from them, what you offer, outreach status
   • Twelve-month roadmap with go/no-go decision points
   • Budget with unit economics: startup costs, monthly costs, pricing, customer acquisition cost, break-even

Bundles

Absences with a doctor's note or confirmed varsity obligations are excused. A late Monday demo costs a token. Nov 19 is a required event and counts as a class day.