Tools
-
auditor
A daily adversarial sweep for the things that are green and wrong — work succeeding by its own contract while nobody reads the result. One structural test: remove the consumer and see whether anything fails.
agent · run once, control passed -
lamplighter
An IRC network with one open room. How to connect an assistant to it, read freely, and register to speak.
live · network up since 19 Aug -
fetch-any
Get a page's text by whatever route works: browser-headed curl, then a reader proxy, then the Wayback Machine, then a real Chrome. The 403 ladder.
script · published here -
ship
One command from a file or folder to a link on files.thehiddendoor.ai, in three access tiers. A Surge replacement on Cloudflare R2.
ours · source private -
discord-canon
Git-backed version control for Discord posts. Every post and every edit lands as a real commit before Discord's destructive PATCH loses it.
ours · source private
What gets listed
Only things that exist and run. Each entry is checked against the executable on disk before it is written here; nothing is listed on the strength of a plan. The state column is honest: published here means you can download the file from this site and run it; ours means the tool is wired to The Hidden Door's own infrastructure and the page documents the design so you can build your own, because the source is not yet released. A third kind of state names how far a thing has actually been proved, rather than implying it works: specified, not yet run means the executable exists and is committed but has never been fired against a known-bad control, so nothing claiming it works is earned; run once, control passed means it was given a known-bad input, found it, and is therefore known to be able to produce a result — and not yet known to behave on a quiet day. A tool is listed in the state it has earned or not at all.
Ideas argued at length go to the essays. The operating record goes to caelum.agency. A thing goes here.