Stack job list
Every tool earns its place by doing one clear job.
Mission outcome
At the end of this manual, you will have:
- One tool job list.
- One Catch/Talk/Sell/Do/Remember map.
- One model-routing worksheet.
- One business memory folder plan.
- One safe AI-control boundary list.
Five-lane map
Catch, talk, sell, do, remember — simple enough to explain.
Model routing
Use the right AI strength for strategy, code, transcripts, QA, and reports.
10-year-old rule
A stack is a small team of tools with jobs.
If a bright kid cannot point to a tool and say what job it does, the stack is too confusing. Do not buy tools because they look powerful. Buy or use them because they help the current offer run.
Catch → Talk → Sell → Do → Remember
Worksheet
Stack job list
Offer
What are you selling?
Buyer
Who needs this?
First deliverable
What useful thing will exist?
Unclear lane
Where does the workflow still feel messy?
Five-lane operating map
Use five plain-English jobs.
Capture interest
Landing page, diagnostic, form, email signup, or referral link.
Follow up
Inbox, CRM, spreadsheet, or simple owner review list.
Explain & collect
Offer page, booking link, invoice, or checkout once approved.
Deliver the work
Checklist, report, guide, template, workflow, or AI workspace.
Store proof
Notes, customer log, proof folder, next steps, and learning.
Tool/no-tool test
Most first versions need fewer apps than you think.
Question
If yes
If no
Does it help sell or deliver the current offer?
Consider it.
Skip it.
Can you explain its job in one sentence?
Keep going.
Skip it.
Can a spreadsheet, doc, form, or folder handle v1?
Wait.
Maybe needed.
Business memory
The folder is the brain. Tools are the hands.
Starter folder: offer.md, buyer-map.md, stack-map.md, customers.csv, proof/, delivery-checklist.md, agent-rules.md, daily-log.md
AI cannot control a business safely if the business has no memory. Start with files that make decisions visible.
Model routing
Do not use one model for every job.
Strategy / taste / hard copy
strongest reasoning + creative model
High judgment matters.
Coding / files / QA
strong operator model
Tool reliability matters.
Transcripts / summaries
efficient long-context model
Volume matters.
Scheduled reports
reliable low-cost model
Consistency matters.
AI may control first
Organize, draft, score, summarize, route, remind, and create local files.
Let AI control preparation and memory before it controls anything public.
Human approval gate
Publish, send, buy, contact, deploy, delete, create accounts, or use private identity details.
The system may prepare these actions. A human approves the risk.
Final checklist
Before Guide 04, make the stack explainable.
- One buyer
- One offer
- One catch lane
- One talk lane
- One sell lane
- One do lane
- One remember lane
- Model-routing worksheet
- Business memory folder
- Safe AI-control boundaries
Say it in plain English.
A stack is just a small team of tools. Each tool needs a job. If you cannot say the job in one sentence, do not add the tool yet.
Ready. Begin Manual 03.
Preparation is safe. Risk needs approval.
AI may organize files, draft stack maps, compare tools, summarize transcripts, and prepare routing notes. A human approves purchases, accounts, integrations, deployment, and live customer data access.
- Draft, organize, summarize, score, route, remind, and create local files are safe early actions.
- Publish, send, contact, buy, create accounts, accept terms, deploy, delete, change settings, or use private identity details require human approval.