Librarian
Changes, 2026-09-20
18 changes. Basis: sgit.ai version log and new-pages list; riskmandate.ai version record (no earlier snapshot to diff).
| Site | Kind | What changed | Type | Concepts |
|---|---|---|---|---|
| sgit.ai | release v0.2.96 | The vault named after the concept was not on the concept's page↗ The Fractal Semantic Graphs page gains a section citing the VoiceDebrief vault where the idea was first worked, and that vault's page records its plaintext GitHub mirror, checked file for file on 20 September. | update | fractal-graphs, provenance |
| sgit.ai | release v0.2.97 | The article that introduces Fractal Semantic Graphs, published here with its pictures↗ The article introducing Fractal Semantic Graphs, written for LinkedIn, is published under /articles/ as the canonical copy with nine figures LinkedIn cannot carry. | update | fractal-graphs |
| sgit.ai | release v0.2.98 | We published read keys under a prefix that declares them secret, and an agent refused to open them↗ After an agent refused to open two AIUC-1 vaults because their published read keys carried the private read prefix, seven keys were relabelled to the public form, the validator now bans private prefixes, and a credentials page explains the five prefixes. | update | read-keys, vault-key-management, lessons-learned |
| sgit.ai | release v0.2.99 | The newest vaults were at the bottom of the table, and at the top of the machine list↗ One newest-first order for the vaults table, llms.txt and everything else, with build assertions on ordinals and dates; the read-key extractor also learns the public prefix it had been stripping. | update | read-keys, lessons-learned |
| sgit.ai | release v0.3.0 | The em-dash is gone from the prose, and so is the legacy key prefix↗ About 3,200 em-dashes are rewritten by context across the site with a validator guard to keep them out, and 102 legacy-prefixed and 24 bare published read keys move to the public read prefix. | update | em-dashes-and-style, read-keys |
| sgit.ai | release v0.3.1 | Vault #31 reaches the same conclusion about fractality, in its own words↗ Vault #31, an independent reference edition of the UK DSIT AI Risk Management Toolkit, is published: four worlds with named bridges, curated and lexical edges labelled, hashed source snapshots, and six gaps it publishes about itself. | update | fractal-graphs, provenance, read-keys, security-audits |
| sgit.ai | new-page | Start with an AI decision, then trace it back to the guidance: the DSIT AI Risk Toolkit vault↗ The vault page for the DSIT AI Risk Toolkit: a use-case journey over the official guidance, the worlds and bridges underneath, the pre-publication audit, and a dated snapshot of the 20 September edition (617 nodes, 694 edges). | vault | fractal-graphs, provenance, security-audits, read-keys, vault-apps |
| sgit.ai | new-page | Vault #31 reaches the same conclusion about fractality, in its own words↗ Update announcing vault #31, the first submission under the public read prefix, which states that containment alone is not fractality. | update | fractal-graphs, read-keys |
| sgit.ai | new-page | The em-dash is gone from the prose, and so is the legacy key prefix↗ Update describing the two site-wide normalisations: em-dashes rewritten rather than deleted, and every published read key moved to the public prefix. | update | em-dashes-and-style, read-keys |
| sgit.ai | new-page | The newest vaults were at the bottom of the table, and at the top of the machine list↗ Update explaining the three bugs behind the vaults table showing #26 first and #30 last, and the single asserted order that replaced them. | update | lessons-learned |
| sgit.ai | new-page | Vault credentials: what each one can do, and what its prefix declares↗ New reference page: two capabilities (vault key and read key, derived one way), five prefixes with publish-or-not per row, classification by declaration rather than shape, and revocation that is never retroactive. | doc | read-keys, vault-key-management |
| sgit.ai | new-page | We published read keys under a prefix that declares them secret, and an agent refused to open them↗ Update on the agent's refusal, the relabelling of the AIUC-1 keys, and the build guard added so a private-prefixed credential fails the build. | update | read-keys, lessons-learned |
| sgit.ai | new-page | Fractal Semantic Graphs: everything connects to everything, and nobody has to share a schema↗ The founder's introduction to the term: the jump test at a link, every file format as a graph, the five-rule grammar, eleven altitudes across seven live vaults, and what is still modelled rather than imported. | article | fractal-graphs, eu-ai-act, provenance |
| sgit.ai | new-page | The article that introduces Fractal Semantic Graphs, published here with its pictures↗ Update announcing the canonical copy of the Fractal Semantic Graphs article, with its diagrams and screenshots. | update | fractal-graphs |
| sgit.ai | new-page | The vault named after the concept was not on the concept's page↗ Update on adding the reverse link from the Fractal Semantic Graphs page to the VoiceDebrief vault and its fifteen-principle register. | update | fractal-graphs, provenance |
| riskmandate.ai | release v1.27.0 | Writing, and a barrier gains a holder↗ A Writing section opens with the article 'An approval prompt is not a human in the loop', and every vault's barriers now record who holds them: not_reachable is replaced by a blocked list that must name its blocker. | update | agent-behaviour-policy, grants-and-mandates |
| riskmandate.ai | release v1.27.1 | An introduction to the Agent Behaviour Policy↗ A second article introduces the Agent Behaviour Policy (mandate, grant, delta, barrier) with one Gmail-connector deployment worked through; the local check now runs all of CI's checkers after a stale hash turned CI red. | update | agent-behaviour-policy, grants-and-mandates |
| riskmandate.ai | release v1.27.2 | The section is called Articles, and a session carries every approval you ever gave↗ Writing is renamed Articles, and a third article argues that a session holds the union of every scope and approval ever granted, with a table of four questions the vendor's help page leaves silent. | update | agent-behaviour-policy, grants-and-mandates |