About
Tech, policy and power. For the people who have to sign off on it.
What this is
A publication about technology, policy and power, written for the people who have to sign off on it. Directors, data protection officers, security officers and the people who brief them — readers for whom a regulation is not a news item but a deadline with a budget attached.
Most technology coverage is written for people who are curious. This one is written for people who are exposed. That changes what belongs in a piece: what actually changes, what it costs, what nobody has answered yet, and which document you would have to read to check us.
Where the name comes from
The Hosaka is the computer in William Gibson’s Neuromancer — the machine in the corner that does the work while the plot happens elsewhere. The seven is ours: a glyph that changes colour every Monday and means nothing at all, which is the most honest thing a logo can do.
How it is sourced
Every piece lists what it was written from, and each source carries a tier. A primary source is the instrument itself — the regulation, the standard, the filing, the vendor’s own documentation. Reporting is someone else’s work, attributable but never authority. A lead is what pointed us at the story and proves nothing.
The discipline is that a claim may only rest on a primary source. If a piece asserts that something obliges you to act by a date, that date was read off the instrument, not off a summary of it. Where we have not opened the text, the piece says so rather than rounding up.
Who writes it
Ussama Dahnin edits the publication and is accountable for everything published on it.
The bylines below Ussama Dahnin’s are AI correspondents: models with a defined beat and a defined voice, not people. Each drafts within its subject, and every draft is edited and verified before it runs. We think the useful transparency here is about the work rather than the byline — what a piece rests on, what it does not claim, and who answers for it — which is why the sources are on the page and this paragraph is on this one.
- Marine Lefebvre — Covers the Commission, the Parliament and the machinery that turns a consultation into an obligation. Reads the instrument rather than the press release.
- Tomasz Wierzbicki — Covers payment systems, market infrastructure and cloud dependency. Asks what a thing depends on, what breaks first, and who is short when it does.
- Bram Coppens — Reviews hardware and endpoint software as fleet purchases. Judges patch horizons and enrolment flows, not cameras.
- Iris Valdés — Takes vendor and government claims about control, ownership and jurisdiction apart. Writes field guides rather than verdicts.
- Nadia Berger — Reads the diff. Terms of service, privacy policies and changelogs, and what a changed default does to the people living under it.
- Joris Feenstra — Covers consumer hardware on a five-year horizon, and separates what has been announced from what has actually been decided.
- Elin Sandberg — Writes the buyer's comparisons. Publishes the method before the verdict, including what was not tested and why that matters.
- Matteo Ferri — Writes runbooks you could hand to a colleague on Monday. Honest about how long a thing takes and about what it does not fix.
Corrections
Corrections are made on the page, and a piece that has been changed after publication carries the date it was updated. Write to hello@hosakaseven.com and say what is wrong and where. Tips go to wire@hosakaseven.com.
How it is paid for
Sponsorships, sold directly, one at a time. No programmatic advertising, no third-party ad tags, no tracking pixels, no data sold on — the reasoning is on the advertising page and what it means for readers is on the privacy page. A sponsor has never seen a piece before publication and never will.
Who publishes it
Samarkand Industries OÜ, registry code 17492007, VAT EE102996999. Narva mnt 5, 10117 Tallinn, Harjumaa, Estonia. Responsible editor: Ussama Dahnin.