Lesson 32 of 34 · Module 11 · Capstone colds
Cold exam: map a name without lesson chrome
No coaching chrome - only the desk and your map.
Pick a name you did not over-train on. Start a timer. Write the weather line, open the desk, check as_of, read Filings, read Books, then build the forward map with weights and falsifiers, without lesson hints on the screen. Prophecy language fails the exam. A thin desk that ends in a calm Wait is a pass, because honest process is the point.
About 30 min · desk walk + key terms · Shark methodology
Pick a name you did not over-train on. Start a timer. Write the weather line, open the desk, check as_of, read Filings, read Books, then build the forward map with weights and falsifiers, without lesson hints on the screen. Prophecy language fails the exam. A thin desk that ends in a calm Wait is a pass, because honest process is the point.
After this lesson, you can…
- ✓Explain cold exam: map a name without lesson chrome in plain words
- ✓Apply the idea to one real PSX company
- ✓Recognise the most common beginner mistake
Visual mental model
A calm learning loop
- 1
Understand
No coaching chrome - only the desk and your map.
- 2
Check
What did this lesson train?
- 3
Apply
Use one real desk or calculator
Key knowledge
Terms you will use on the desk
- Cold start
- Run SOP without looking at your old notes first.
cold SOP exam — study, not tip
This lab trains cold SOP exam on a live desk. Write dated evidence, refuse undated tip calendars, and keep scenario weights as business-path opinion — never as % chance the price moves.
In-depth teaching
5 sections
01
What a cold exam is and why it exists
Guided labs have hints, prompts, and gold maps nearby. The real world has none of those. A cold exam removes the chrome and asks you to run the SOP on a name you did not drill, so you find out whether the habits live in your head or only on the lesson page. It is a skills check, not a prediction contest.
Choose a name from the stock list that you know little about, with enough desk data to study, rather than a famous teaching name. Avoid a name you have strong feelings about, since feelings are the thing the SOP is designed to contain. Write the ticker and the time you start so you can reflect afterwards on pacing.
02
The pass rules in plain words
A passing map is complete: weather line, as_of, Filings summary, Books anchors, drivers, catalysts or none known, three business scenarios, weights summing to 100, at least two concrete falsifiers, an exit line, and a decision. It contains no price targets, no up-or-down odds, and no prophecy language such as 'will double' or 'sure shot'. Weights express opinion on business paths only.
If the data is thin, the pass can still be achieved by writing honest unknowns and ending at Wait. A map that says 'Books not ready; relying on Filings; drivers partly unknown; decision Wait' is a stronger exam than a confident map that invents missing data. The checker looks for evidence discipline, not for optimism.
Pause and predict · free
Getting check ready…A forward map is…
03
Worked mini-example: pacing and structure
A teaching timeline might look like this. Minutes 0 to 3: weather line and ticker choice. Minutes 3 to 8: desk, as_of, Filings, notes of the latest dated notices. Minutes 8 to 15: Books anchors and cash line, with unknowns marked. Minutes 15 to 22: drivers, catalysts, scenarios, weights. Minutes 22 to 27: falsifiers and exit. Minutes 27 to 30: decision and a read-through for prophecy words.
The final read-through matters. Scan for phrases like 'will rise', 'target', 'guaranteed', or percentage odds on price. Replace them with business-path wording or remove them. Also check that weights add up to 100 and that each falsifier points to a place you could check. Submitting a clean, slightly incomplete map is better than a polished one with invented lines.
04
Common failure modes
The usual failures are predictable. One is prophecy language slipped in under pressure. Another is a missing falsifier, because the map felt convincing. A third is invented numbers when Books are empty. A fourth is skipping the exit line on a thin name. A fifth is a map that always ends at Broker talk because the writer wanted that answer. Knowing these in advance helps you catch them.
Another subtle failure is copying the gold map's structure for a different company without adapting the drivers. A bank driver tree does not fit a textile mill. If you notice yourself reusing phrases, stop and read the desk again for what this company actually sells. The cold exam is designed to expose borrowed thinking, which is useful information, not a punishment.
05
Tip-culture trap, and the fork
The trap is treating the exam as a performance and writing what sounds impressive. Tip culture rewards confident language; the exam rewards calibrated language. If you feel an urge to sound sure, that is a signal to add an unknown or a falsifier. Calm, specific, modest wording is the target voice.
Wait is a pass when the evidence is thin and you say so. Need evidence is a pass when the business is clear but a key line is missing and you state exactly what. Broker talk is a pass only when the whole map is complete and checked, and it remains a discussion, not a forecast. After submitting, note what you would do differently next time.
Check your understanding · free
Getting check ready…Scenario weights mean…
Common slip
Skipping the lab and calling the lesson done.
Required lab
Do this on the desk now
Submit one cold forward map via Study Mode on a research desk (?study=1).
Done when: Map submitted without prophecy language
Open →
Lab · Cold SOP exam
45-minute timed forward map. Evidence lock → map. No prophecy.
Loading cold exam…
Failed map examples — learn from scars
Real mistakes that fail the validator. See the error, understand the fix.
These are real beginner mistakes that the MapValidator catches. Study them so you don't repeat them.
PROPHECYProphecy Language in Rationale
HBL · 5 error(s)
▼
Prophecy Language in Rationale
HBL · 5 error(s)
❌ Failed map — 5 validation errors
- Rationale contains prophecy: 'will go up', 'target 200'
- Scenarios describe price targets, not business paths
- Weights reflect price odds (60/30/10), not business path opinions
- Falsifiers are vague ('market crashes')
- Decision 'broker_talk' without completing evidence steps
💡 Teaching note
Prophecy veto is automatic. Every field must describe business paths, not price predictions. Weights are your opinion on business outcomes — not % chance price moves.
VAGUE-FALSIFIERVague Falsifiers
FFC · 4 error(s)
▼
Vague Falsifiers
FFC · 4 error(s)
❌ Failed map — 4 validation errors
- Falsifiers are generic ('market crashes', 'economy gets bad') — not checkable
- Bear scenario 'things go wrong' is not a business path
- Weights rationale 'until something changes' is not a working case explanation
- Catalyst 'unknown' without falsifier for 'no gas notification in 90 days'
💡 Teaching note
Falsifiers must be specific, dated, and checkable: filing events, book lines, governance signals. 'Market crashes' is lazy — name the filing or book line that kills your base case.
WEIGHT-ERRORWeights Don't Sum to 100
LUCK · 3 error(s)
▼
Weights Don't Sum to 100
LUCK · 3 error(s)
❌ Failed map — 3 validation errors
- Weights sum to 110 (40+40+30), not 100
- Decision 'broker_talk' with invalid weights
- Rationale 'bullish on demand' doesn't explain base/bear weights
💡 Teaching note
Weights must sum to exactly 100. The validator catches this automatically. Your rationale must explain why base is the working case, not just 'bullish on X'.
MISSING-DRIVERMissing Key Driver (Circular Debt)
OGDC · 4 error(s)
▼
Missing Key Driver (Circular Debt)
OGDC · 4 error(s)
❌ Failed map — 4 validation errors
- Missing critical driver: circular debt receivables / cash collection
- OGDC is an E&P — cash collection from refineries is the real driver, not just oil price
- Falsifiers don't mention receivables aging or government payment delays
- Liquidity exit ignores that OGDC shares can be thin in panic
💡 Teaching note
Every sector has hidden drivers. For E&P: cash collection = production × price × collection rate. Missing receivables driver = incomplete map. Always ask: 'What kills cash flow even if price is good?'
NO-EXITNo Exit Plan for Thin Name
THIN · 4 error(s)
▼
No Exit Plan for Thin Name
THIN · 4 error(s)
❌ Failed map — 4 validation errors
- Liquidity exit 'will figure out later' is not a plan
- Decision 'broker_talk' on thin data with no exit = dangerous
- Drivers 'unknown' but decision not 'wait'
- No lot size, volume, or free float analysis
💡 Teaching note
Thin data → Wait is the only valid decision. If you don't know lot size, volume, and free float, you cannot size a position. 'Broker talk' on unknown liquidity = gambling.
THIN-DATA-INVENTEDInventing Numbers on Thin Coverage
THIN · 4 error(s)
▼
Inventing Numbers on Thin Coverage
THIN · 4 error(s)
❌ Failed map — 4 validation errors
- Drivers invented ('Revenue growth 15%') — Books are empty, no data to support
- Catalyst date invented — no filing confirms Dec 15
- Weights reflect optimism, not evidence
- Liquidity exit 'assume liquid' on unknown name = dangerous
💡 Teaching note
Thin coverage → Wait. Honesty beats invented drivers. If Books are empty, write 'unknown — need filings/books'. Never invent numbers to make a map look complete.
What you can say now
Evaluation language — not a price call.
- →I can brief this name: drivers, catalysts, business paths, falsifiers, exit, decision.
- →I can evaluate a prediction claim: where is the evidence, and what would prove it wrong?
- →I still refuse price targets and up/down odds — judgment, not prophecy.
Worth keeping
- Veterans keep scars next to every step.
- A complete map still is not a price call.
- A short, honest map often scores better on process than a long one that hides its unknowns.
- Reading your map aloud once before submitting helps catch prophecy words you did not notice writing.
Write Wait when evidence is thin — that is skill, not weakness.
Try it on a live desk
Practice · support fades as you go
Practice with support
Write Wait when evidence is thin — that is skill, not weakness.
Need a hint?
A scar-backed habit on the live desk — not a tip.
Done when: You can explain what you checked and what remains uncertain.
Now without hints
Try it independently
What did this lesson train?
A strong answer: A scar-backed habit on the live desk — not a tip.
Lesson FAQ
What did this lesson train?
A scar-backed habit on the live desk — not a tip.
Does a strong map mean buy?
No. It means homework. Decision may still be Wait.
Are weights price odds?
No. They are opinion on business paths only.
Can I fail by choosing a name with thin data?
No. Thin data with honest unknowns and a calm Wait can pass. Inventing data to fill gaps is what fails.
Are weights on the cold exam price odds?
No. They are opinion weights on business paths and must sum to 100. Any wording that treats them as price odds fails the exam.
Mark this lesson complete
What did this lesson train?
Show calm answer
A scar-backed habit on the live desk — not a tip.
A scar-backed habit on the live desk — not a tip.
Tick every required lab step above before you mark complete.
Sign in before completing lessons if you want them counted toward the certificate.
Optional: graded test (sign-in)
Member lesson tools
Full lesson test & member tools
Checking sign-in…
Ask coach
LockedAsk: review my map gaps
Share drivers and falsifiers — coach checks process.
Sign in to unlock →
Stay on the course path
Follow the Shark Methodology path. How-tos and metrics are optional reference.
- Shark Methodology course
Main beginner path: evidence, forward maps, and evaluating claims — not competing starts.
- Learn PSX hub
Start Lesson 1, then optional guides and tools when you need them.
- PSX today
Pakistan stock market today in plain words - breadth, gainers, losers.
- PSX companies list
Browse all Pakistan Stock Exchange listed companies by name or sector.
- KSE 100 index today
Educational constituent board - not the official index level on psx.com.pk.
- PSX gainers today
Biggest % rises among ordinary listed shares - homework, not a buy list.