Releases, findings and decisions, written for someone deciding whether to upgrade. https://orkcom.com/ 2026-08-18T00:00:00Z ORKCOM tag:orkcom.com,2026-08-18:2026-08-18-cogitorium-2-0-everyone-signs-in-including-on-your 2026-08-18T00:00:00Z

A solo install used to feel accountless, and the price was that "this machine" is not one principal: every process on it — a script, a package's install hook, any page in a browser able to reach the port — had the run of it. First run now asks you to choose a password for the admin account, and on an address the network can reach it also asks for the admin token from the startup log. Upgrading, you are asked once. The interface was rebuilt with it. Every control lives on a frame around the work, three stages slide through the hole in it, and drawers grow inward rather than covering what you were reading — the cavity shrinks to make room, so nothing you were working on ends up half underneath something. Appearance became two choices: light or dark, and one colour, with every neutral mixed towards it.

tag:orkcom.com,2026-08-18:2026-08-18-contextverse-is-1-0-and-the-version-now-means-som 2026-08-18T00:00:00Z

From v1.0.0 the commands, the flags, the HTTP API and the on-disk layout are stable within a major version — a minor may add, and will not remove or change the meaning of what is already there. Anything that has to break waits for a major, is called out under Changed, and carries its migration in the same entry. One caveat, because a promise with the awkward part left off is not one: the releases between 0.7.0 and 1.0.0 were cut with no changelog entries at all, so for that stretch the git history is the record. Two things shipped with it that you could not do from the command line before. contextd file delete exists — the capability was in the storage layer and over HTTP the whole time, while file destroy refused a live version by telling you to soft-delete first and gave you no way to do it. It is soft on purpose: the live copy goes, every version stays, file undelete brings it back. And --if-version on put and delete lets a caller name the version it read. Both were always compare-and-swap, but against whatever was current at that instant, which stops two writes racing and does nothing for the case that actually loses work: somebody read a file an hour ago, wrote it back, and buried an edit made in between. An editor holding v4 is now refused once the file has moved past it — and that refusal is the point, because it can tell somebody their copy is stale instead of discarding the other version in silence.

tag:orkcom.com,2026-08-14:2026-08-14-cogitorium-is-apache-2-0-and-it-opens-on-paper 2026-08-14T00:00:00Z

The Business Source Licence allowed production use but not offering Cogitorium to third parties on a hosted basis. That restriction is gone as of v0.5.0: build on it, ship it, charge for it, run it inside a service you sell — none of that needs permission or a conversation with anyone. It is an early arrival rather than a reversal, because the BUSL already named Apache-2.0 as its change licence with a date in 2030, and the date was brought forward to now. ContextVerse is unchanged and still BUSL-1.1. Two things about the product itself changed with it. The work it asks of you finally has a name — graph engineering: agents are nodes, and four kinds of edge are each a permission the runtime checks, so removing one stops the thing it allowed from being possible. And a fresh install now opens on Sketch, a third look with a paper ground and handwriting on the chrome, in light rather than dark. Both existing looks were dark, so the light half of this product had never been examined; twenty-two problems were found in it and each verified in the file before being touched.

tag:orkcom.com,2026-08-09:2026-08-09-cogitorium-is-installable-and-the-products-moved-int 2026-08-09T00:00:00Z

Cogitorium went from a line on the products page to something you can install: Homebrew, Scoop, Docker, .deb / .rpm and a desktop build, with signed archives. It is early — commands, API and on-disk layout are not stable, so pin a release if you depend on them. At the same time the products dropdown became the header itself: five names in the bar, and More for the rest. Two of those names lead to pages that say the product cannot be used yet, which is the point of naming them.

tag:orkcom.com,2026-07-28:2026-07-28-everything-moved-to-orkcom 2026-07-28T00:00:00Z

The repositories, the templates, the Homebrew tap, the Scoop bucket and the documentation site now live under the organisation. If you installed before today, repoint your tap — the old one still resolves but no longer updates, so brew upgrade would quietly keep you behind.

tag:orkcom.com,2026-07-28:2026-07-28-per-space-quotas-and-the-api-can-take-a-token-back 2026-07-28T00:00:00Z

Limits used to be per server, so one machine could not hold a canonical space that stays small and a scratch space that does not. They live per space now. Separately, the API could mint credentials and never revoke them — that is closed, and the call reports how many it revoked.

tag:orkcom.com,2026-07-28:2026-07-28-we-benchmarked-our-own-default-and-it-lost 2026-07-28T00:00:00Z

ContextVerse sends an AI its whole entry set at the start of every session, and whether that beats letting the client fetch what it needs had never been measured. It reaches only three answers in five on our test set — because two of the answering documents are not in the entry set at all. A fixed list cannot deliver what is not on it. The wider question is still open, and the task sets are in the repository so you can disagree with us in public.

tag:orkcom.com,2026-07-27:2026-07-27-the-space-knows-its-own-shape 2026-07-27T00:00:00Z

Links your documents already contain now form a graph, so backlinks, orphans and broken links are facts about what you wrote rather than inferences about it.