What we built before this
Athren is the second product, not the first. The one before it is stacklink.nl, still up and readable. The engineering carried over. Where that site’s marketing outran what it had built is most of why this one reads the way it does.
The product before this one, measured rather than remembered.
The first was measured on the live site on 3 August 2026, the other two read out of the repository the day before. None says how well it sold.
- 36
indexable pages, with a sitemap, canonical links and structured data
stacklink.nl
- 114
routes in the application behind it
read from the repository
- 248
migration files, numbered 0000 to 0151, each with its rollback
no ORM, raw SQL
What carried over is the engineering, not the copy.
Two decisions came across whole, and both are written down, so changing one is a new record and not a commit.
- ADR-0002
A provider is a config row
The connector engine is written here rather than bought in. Adding a tool is a declarative row: auth mode, base address, rate limit class, and the exact capabilities it may call.
- ADR-0001
One door for every model call
Every model and embedding call leaves through a single module we own. Where inference runs is a configuration change rather than a rewrite.
What we published then, and what this site does instead.
Quoted rather than characterised, because a mistake paraphrased is a mistake being managed.
Published then"Setup in 5 minutes", on 29 generated pages, for a product with no setup a customer could do.
HereNo setup-time claim anywhere here, and a standing refusal in the file that gates publication.
Published then"The average knowledge worker spends 9.3 hours per week searching for information", set as a pull quote with no source under it.
HereTwo figures are cleared for the whole site, each naming its study.
Published then"All systems operational", hardcoded as a string, under a green dot that suggested a feed.
HereEvery figure here is counted at build time from the file that defines it.
Published thenVendor logos copied from a third-party aggregator, which grants no rights from anyone.
HereA provenance record per directory, and six marks deleted rather than shipped.
None of that is evidence for this product. These three are.
Every claim about the software is written in one file with the test that would falsify it.
- 01
A write with no permission behind it
A connection whose grant was none was given the same write a granted connection takes. The server refused it before anything reached the provider: HTTP 409, grant_denied, recorded in the trail like any other event.
Run 2026-08-01
- 02
An audit entry edited in the database
One committed entry was altered directly in storage, not through the software. A verifier that re-derives every hash from the raw rows went from unbroken to broken, and a byte-exact restore healed it.
Run 2026-08-01
- 03
Another tenant sweeping for your data
Two workspaces on one database, the second driven against every endpoint the first uses. Nothing came back that belonged to the other.
Run 2026-08-02
Finish the client call with the work already mapped.
Send one recent client meeting. Leave with the actions, follow-ups and exceptions a person can approve.