content: six real code exhibits, rendered by the panel (AUD-152)
This commit is contained in:
@@ -8,13 +8,13 @@ confidence: running
|
||||
period: "2026–"
|
||||
tech: [Nix, NixOS]
|
||||
metrics: [{label: "pinned version", value: "0.10.1"}, {label: "nixpkgs version it overrides", value: "0.7.0"}]
|
||||
artefacts: []
|
||||
artefacts: [{type: repo, label: "Nix derivation — tuios 0.10.1 override with a removal condition", url: "content/assets/code/06-nix-derivation.nix"}]
|
||||
public: true
|
||||
last_verified: 2026-10-26
|
||||
last_verified: 2026-10-28
|
||||
tags: [platform, nix, packaging, artefact]
|
||||
---
|
||||
|
||||
The whole file is short enough to publish verbatim; it lands in Phase 7.
|
||||
**Status: published.** The whole file is shown verbatim.
|
||||
|
||||
## What the artefact is
|
||||
|
||||
@@ -24,6 +24,10 @@ A package definition for the agent operations console: `fetchurl` against a rele
|
||||
|
||||
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
|
||||
|
||||
Phase 7. The file is in the infrastructure repository; source fact: content spine section 4.2.
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user