1.8 KiB
id, area, level, title, claim, confidence, period, tech, metrics, artefacts, public, last_verified, tags
| id | area | level | title | claim | confidence | period | tech | metrics | artefacts | public | last_verified | tags | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| platform-tuios-package | platform | 3 | Artefact — A hand-written Nix package with an exit plan | Twenty-five lines of Nix that pin a tool at 0.10.1 over nixpkgs' 0.7.0 — with a verified hash · a written reason and a written condition for deleting the file. | running | 2026– |
|
|
|
true | 2026-10-28 |
|
Status: published. The whole file is shown verbatim.
What the artefact is
A package definition for the agent operations console: fetchurl against a released artifact with a verified hash, a documented reason for overriding nixpkgs, an installPhase that stages the binary, and a comment stating the condition under which the file should be deleted.
What it proves
More than knowing Nix exists. The signals are that someone noticed a version gap, fixed it locally instead of waiting, pinned it so the fleet is reproducible, and wrote down when to remove their own patch. Knowing when to delete your own override is the senior part.
Why this exhibit is good code
The override records why it exists and the exact condition under which it should be deleted, which is the part of a local patch that usually goes missing. Pinning a released binary by fetchurl with a verified hash keeps the result reproducible without waiting for nixpkgs.
When it is delivered
Published. The file is in this repository at content/assets/code/06-nix-derivation.nix; the infrastructure repository remains the source. Source fact: content spine section 4.2.