Week 4, Operationalize · Day 23 of 30
Day 23: The anti-signal, when 6/6 is wrong
Some orgs game every signal. Building your false-positive list is week 4 work.
Day 23 in one paragraph: Frameworks are gameable, especially public ones. A devtools agency, a YC alum farming OSS contributions, a team running a single-customer consultancy that looks like a startup, all can score 6/6 on the public composite. Your false-positive list is the personal antibody. You will spend about five minutes, end with a concrete artifact, and the whole curriculum stays free at this URL permanently.
Where this day sits in the 30
Week 4 wires the system into alerts, sharing, and agent integrations so it runs without you. Day 23 of 30 sits 77% of the way through, in week 4, operationalize, one of four one-week phases. This day also carries a bonus exercise for anyone with extra time. Everything in this challenge is built from public GitHub signals, the same data that powers the weekly deal-flow feed, and the day's lesson is worth roughly €89 in equivalent consulting time by the anchoring we use across the curriculum.
Yesterday
Yesterday you set alerts. Today: the override layer that catches the orgs where the alerts will lie to you.
Why this signal matters
Frameworks are gameable, especially public ones. A devtools agency, a YC alum farming OSS contributions, a team running a single-customer consultancy that looks like a startup, all can score 6/6 on the public composite. Your false-positive list is the personal antibody.
The 5-minute exercise
- 1List 3 archetypes you've seen game public-data signals (agencies, single-customer consultancies, OSS-funded research labs).
- 2For each, note the signal that betrays it on closer reading (e.g. agency → look at customer-named repos).
- 3Add a manual 'sanity check' step to your Monday rhythm: top 1 from watchlist gets the 5-minute archetype check.
- 4Save the archetype list. Update quarterly.
What you’re filtering for
A written, dated false-positive list with at least 3 archetypes and the manual check that catches each. The list is private, it's competitive advantage, not content.
Edge case
A single high-trust founder you've already met can override a low score the same way an archetype can override a high score. Both are personal-judgment overrides on top of the framework, not replacements.
Bonus
The archetype list is the most personal artifact in this whole challenge. It encodes your specific bias-correction. Two investors with the same 6-signal framework will produce different deal flow because their archetype lists differ.
Tomorrow
Tomorrow: making the score legible to a co-investor, the share template that turns a number into a paragraph.
Common questions about day 23
- How long does day 23 take?
- About five minutes of hands-on work against the org you picked on day one. The reading adds another two or three. If you are short on time the exercise alone still delivers the day's point.
- Do I need any tools or paid data for the anti-signal, when 6/6 is wrong?
- No. Every exercise in the challenge runs on public GitHub data and a browser. The feed that automates the same checks is available, but the curriculum itself is deliberately tool-free so the habit lands before the tooling.
- What if I miss a day?
- Every day is permanent at its own URL, so you can pick up exactly where you stopped. The sequence matters, each day builds on the previous one's artifact, but the pace is yours. Many people run the 30 days across six or seven weeks instead of four.
Curriculum: /challenge · Methodology: /methodology · Paper: ssrn.com/abstract=6606558