Lesson 19 of 34 · Module 6 · Shark forward map
Write falsifiers before you fall in love
If nothing can prove you wrong, you are not studying.
People fall in love with a tip and stop looking for reasons to be wrong. Falsifiers are the divorce papers you write early: the provision spike, the gas shock, the missing filing, the dilution notice that would weaken your base path. If nothing can prove you wrong, you are not studying; you are believing. This lab makes you write two concrete kill-conditions before you let a map stand.
About 16 min · desk walk + key terms · Shark methodology
People fall in love with a tip and stop looking for reasons to be wrong. Falsifiers are the divorce papers you write early: the provision spike, the gas shock, the missing filing, the dilution notice that would weaken your base path. If nothing can prove you wrong, you are not studying; you are believing. This lab makes you write two concrete kill-conditions before you let a map stand.
After this lesson, you can…
- ✓Explain write falsifiers before you fall in love 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
If nothing can prove you wrong, you are not studying.
- 2
Check
What did this lesson train?
- 3
Apply
Use one real desk or calculator
Key knowledge
Terms you will use on the desk
- Falsifier
- What would make your map wrong — written before Broker talk.
falsifiers — study, not tip
This lab trains falsifiers 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 falsifier is
A falsifier is a specific, checkable event or number that, if it appeared, would make you weaken or abandon your base path. It is written in advance, before you are emotionally attached, and it points to a place you can look: a filing type, a Books line, an auditor wording, a governance signal. A good falsifier is uncomfortable because it names a way you could be wrong.
Compare 'market crashes' with 'provisions rise faster than interest income for two consecutive periods in Books'. The first is cosmic and lazy: it applies to everything and is not specific to your thesis. The second is concrete, belongs to a bank's drivers, and can be checked. Aim for the second kind. Two concrete falsifiers are better than five vague ones.
02
Where falsifiers live on a PSX desk
Look at the places that carry bad news early. Filings may show rights issues, restructuring, board resignations, delayed accounts, or regulatory notices. Books may show operating cash falling while profit rises, debt climbing faster than equity, or receivables ballooning. Auditor wording in annual reports may include qualified opinions, emphasis of matter, or going-concern language. Each of these can be written as a falsifier with a clear trigger.
Also consider falsifiers tied to drivers from your tree. If your driver is gas availability for a fertilizer name, a falsifier might be 'a dated notice of reduced gas supply or curtailment in Filings'. If your driver is demand for a cement name, a falsifier might be 'sales volumes falling for two consecutive quarters in Books'. A falsifier that points back to a driver keeps the whole map consistent.
Pause and predict · free
Getting check ready…A forward map is…
03
Worked mini-example: two falsifiers for HBL
Take HBL as a teaching example. Your base path might be: 'margins stay roughly stable and loan quality does not worsen sharply.' Falsifier one: 'Provisions for bad loans in Books rise sharply relative to income over two periods.' Falsifier two: 'A Filings notice discloses a qualified auditor opinion or a significant regulatory action that affects the bank.' Both are checkable, and both point at different parts of the business.
Add what you would do if one appears: not 'sell' or 'buy', but 'downgrade the base weight and move the decision toward Need evidence or Wait until I understand'. That keeps the falsifier connected to your process. Check them again whenever a new filing arrives. A falsifier you wrote and never looked at again is a decoration, not a discipline.
04
Common Pakistan falsifiers: rights and auditor language
Rights issues and auditor language are classic falsifiers on PSX. A rights notice can signal a cash need and dilution, which may weaken a bullish path that assumed no new capital would be needed. An auditor's qualified opinion, emphasis of matter, or going-concern note signals that the audit found something material that readers should weigh. Both are worth writing as triggers in advance.
Other practical falsifiers include delayed financial statements, repeated restatements, large related-party transactions flagged in notes, and sudden changes in key management. None of these alone proves a problem, but each is a reason to slow down and read. A good map names which of these would matter most for the particular business, rather than listing every possible bad event.
05
Tip-culture trap: confidence without kill-conditions, and the fork
The scar is 'no falsifier because I am confident'. Confidence feels like evidence, but it is a feeling. Tip groups sell confidence precisely because it silences the part of you that would ask what could go wrong. If you cannot write two concrete falsifiers, your map is not complete, and the most honest decision is usually Wait.
Wait means you cannot name two concrete kill-conditions. Need evidence means you can name them but cannot yet check one because the required Books or Filings are missing. Broker talk requires falsifiers that you have actually checked against the latest desk data, together with the rest of the map. Even then the map is not a forecast, and a falsifier appearing is a reason to revisit, not to panic.
Check your understanding · free
Getting check ready…Scenario weights mean…
Scar · refuse this
Trap: No falsifier because ‘I am confident’.
Refuse: Refuse confidence without kill-conditions.
Rights and auditor opinions are classic falsifiers on PSX.
Required lab
Do this on the desk now
Lab · Forward map
Build your map: drivers, catalysts, BBB, falsifiers, exit, decision.
Loading forward map lab…
Or practice on live desk with Study Mode
Open HBL Study ModeWorked example
FFC Falsifiers: Gas + Subsidy
Step-by-step walkthrough on FFC. Open the desk alongside to follow.
Steps (3)▼
1. Look at your base case
Base: 'Normal agri cycle; subsidy delayed but eventual'. What kills this?
💡 Falsifier = what makes your base case wrong.
2. Write CONCRETE falsifiers
Falsifier 1: 'Gas price hike >10% without urea price pass-through within 60 days'. Falsifier 2: 'Subsidy receivable grows > OCF for 2 consecutive quarters'.
💡 Specific, dated, checkable. Not 'gas goes up' — 'gas hike >10% without pass-through in 60 days'.
3. Classify each falsifier
Gas hike = macro driver. Subsidy receivable = filing/book line. Both are checkable.
💡 Falsifier types: filing, book_line, governance, macro. Tag them.
Show completed forward map
Drivers: Fertilizer volumes/pricing; Gas feedstock cost; Subsidy receivable collection
Catalysts: Gas price notification (unknown); Subsidy release circular (unknown)
Bull: Volumes hold; gas manageable; subsidy flows
Base: Normal agri cycle; subsidy delayed but eventual
Bear: Gas spike + subsidy stall + volume drop
Weights: Bull 25% / Base 50% / Bear 25%
Rationale: Base until dated gas/volume/subsidy shock. Subsidy receivable is the swing factor.
Falsifiers: Gas price hike >10% without urea price pass-through within 60 days; Subsidy receivable growth > OCF growth for 2+ quarters
Exit: FFC liquid — lot 500 shares, avg vol ~1M/day. Check volume around subsidy news.
Decision: need_evidence
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 name two concrete things that would kill or weaken my thesis.
- →‘Market crashes’ is too lazy to count.
Worth keeping
- Veterans keep scars next to every step.
- A complete map still is not a price call.
- A falsifier that is easy to check, like a filing type, is more useful than a clever one you cannot verify.
- Reviewing falsifiers each time a new filing arrives takes minutes and prevents most slow-motion surprises.
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.
Why write falsifiers before I decide anything?
Because after you hold an opinion, it is much harder to see evidence against it. Writing kill-conditions early keeps you honest.
Can a falsifier be a price level?
No. This course keeps falsifiers on business and evidence, such as filings and Books lines, not on price targets.
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.