# Who signs for this? Accountability maps from the hardware to the business, what is measured and what is declared, and why the parts nobody signs are the blind spots worth paying to see: what changed in v1.1.0, sgit.ai > The changes to the article "Who signs for this? Accountability maps from the hardware to the business, what is measured and what is declared, and why the parts nobody signs are the blind spots worth paying to see" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [Who signs for this? Accountability maps from the hardware to the business, what is measured and what is declared, and why the parts nobody signs are the blind spots worth paying to see](../../who-signs-for-this.md) / [Versions](../who-signs-for-this.md) / v1.1.0 # Who signs for this? Accountability maps from the hardware to the business, what is measured and what is declared, and why the parts nobody signs are the blind spots worth paying to see: what changed in v1.1.0 From v1.0.0 (2026-10-24, `8011d773e`) to v1.1.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph. 0 paragraphs added, 0 removed, 3 changed in place, 51 unchanged. About 0 words added and 174 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../who-signs-for-this.md) 2 unchanged paragraphs !shot ky-map.webp | images/ | Who signs for each layer: anAn accountability map from the business to the hardware. Each line says what is claimed, whether it is measured or declared, andhardware: who signs it:each layer, with the business owner for the contract, the product owner for what was delivered, a maintainer for the code that goes live and the release, the platform team for the process, the cloud provider for the platform, a hardware root and a verifier for the device. The building, who can reach it and what is plugged in, isbuilding signed by nobody: a blind spot. An illustration of the argument, not an audit of any system.nobody. | concept 9 unchanged paragraphs, under In short {#in-short}, The thread {#thread} !shot ky-thread.webp | images/ | The LinkedIn thread under my post sharing "Who maintains the PHP you run?", 24 October 2026: Andrey Lazarev on what a maintainer's signature does and does not prove, my replies, and his split between what a device can measure and what an operator or auditor has to declare.2026. | small | aside 18 unchanged paragraphs, under Somebody has to be accountable {#accountable}, Signers define the gaps {#gaps}, What is measured, and what is declared {#measured}… !shot ky-fractal.webp | images/ | Every signed line is a graph of its own: the device line "the device: this is what actually booted", signed by a verifier, opens into the measurement, the reference it should match, thereference, verifier who checked one against the other, and the endorsement of the hardware root. The same holds in every domain: the business, the product, the code, the release, the platform, the device. Each opening ends in somebody who signed, or in a blind spot.endorsement. | concept 22 unchanged paragraphs, under The blind spots {#blind-spots}, The experts sign, and get paid {#experts}, When the person who signed leaves {#leaves}… [all versions](../who-signs-for-this.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/who-signs-for-this/v1.1.0.html)*