About
Hadrek teaches a process. It does not tell anyone what to buy, and it never will, because the moment it does it becomes a different product with different laws attached to it.
The person behind the desk — Hadrek
Hadrek is the voice in the daily notes and the screen-and-voice sessions. No face is used. The connection is built the slower way: one person, one desk, one clear explanation, arriving at the same time every day.
Hadrek is a handle. There is no photograph, no CV and no public record attached to it, and none is coming. Judge the work by whether the reasoning holds when you read it back a week later.
- →Every note is dated and stays up, including the ones that read the conditions wrongly.
- →The journal schema and the regime detector are published openly. You can read the code.
- →Sessions are screen and voice. You watch the work happen rather than hear it described.
- →No number on this site describes anyone's account, because none could be verified by you.
What is published, and what is not
There is no return record on this site. Not because it would be unflattering, but because a published record cannot be verified by you, and an unverifiable number is worth less than nothing when it is the thing being used to sell you something.
There is no member count, no testimonials and no logos. Every one of those is trivially fabricated in this market, so none of them are used here as proof.
What is published instead is the work: a dated build log, an open journal written before outcomes exist, one free teardown a week, and one open-sourced component with real commits. Those can be checked. That is the point.
Shipped versus planned
Live
- 2026-08-14Weekly teardown, issue three
- 2026-08-07Journal schema published openly
- 2026-07-28Modules one to four written
Planned
- NextModules five to eight
- NextReplay harness, first public version
- LaterRegime detector reference implementation