1c0ffeecourse(launchpad):curriculum preview · demo
First Automations
Turn one repeated task into a small script you understand, with a person in charge of the last step.
- track
- Launchpad
- level
- Starter
- length
- 5 modules · about 10 hours
Your progress dot moves to this branch
Prerequisites
- No coding experience
- A spreadsheet or inbox task you repeat weekly
1c0f011docs:outcomes and build
You will be able to
- Describe a task as inputs, steps and outputs
- Read and edit JSON without fear
- Run a short script on a schedule
- Add a model step that drafts, never sends
Hands-on build
Weekly triage helper
Sorts a week of real items into buckets and drafts replies you approve one by one.
1c0f022feat:5 modules
Modules.
- module 1
Map the task before the tool
Outcome: A one-page task map with the judgement steps marked.
Lessons: Inputs, steps, outputs · Where people make calls · What a wrong result costs
- module 2
Data you can see
Outcome: Move rows between a sheet and a script and back.
Lessons: CSV and JSON side by side · Breaking JSON on purpose · Reading error messages
- module 3
Your first script
Outcome: A script that runs on a schedule and writes a log line.
Lessons: Variables and loops for real tasks · Running on a timer · Logs you will actually read
- module 4
Add a model step
Outcome: A step that drafts a label and a reply in a fixed shape.
Lessons: Asking for a shape, not prose · Rejecting bad output · Keeping a person in the loop
free Tool calls need contracts covers this module interactively.
- module 5
Run it for a week
Outcome: A miss log and a decision: keep, change or stop.
Lessons: Shadow mode · Counting misses honestly · When not to automate
1c0f033docs:sample lesson
Sample lesson · Breaking JSON on purpose
JSON is a way to write data so a program can read it: names in quotes, values after a colon, items separated by commas. Most beginner errors are a missing comma or a missing quote.
Copy the example, delete one comma, and paste it into the Lab validator. Read the error. Then put it back. Doing this five times teaches more than a page of rules.
{ "from": "billing@example.com", "subject": "Invoice 4471 overdue", "bucket": "finance", "needs_reply": true}1c0f044test:assessment rubric
Ready to merge when
| Criterion | Ready to merge | Not yet |
|---|---|---|
| Task map | Every step has an owner and the judgement steps are marked. | Steps are vague or the hard part is missing. |
| Safety | Nothing is sent or changed without a person approving it. | The script can act on its own. |
| Evidence | A week of results with misses written down. | Tested on two examples. |