What changed in the knowledge bundle, a day to an entry, newest first. https://noelmcloughlin.github.io/ai-linkmo/knowledge/log 2026-10-27T18:46:21Z Noel McLoughlin CC BY 4.0 https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-10-27 2026-10-27T01:16:59Z 2026-10-27T18:46:21Z <ul> <li><strong>Changed</strong>: the source map's exclusions name <code>ai-risk-ontology-linkmo/docs/elements</code> and the project's <code>scripts/gen_examples.py</code>, where 0.5.0 moved them, and are split into shorter sentences and a list.</li> <li><strong>Changed</strong>: the FastAPI backend names the file of count cases, <code>expected_counts.yaml</code>, as <code>lib/api/README.md</code> now does, in place of the README.</li> <li><strong>Prose</strong>: reworded 3 concept bodies in plain English: <code>services/cli</code>, <code>services/fastapi-backend</code> and <code>services/datasette-browse</code>. No fact, link, number or frontmatter changed.</li> <li><strong>Changed</strong>: the FastAPI backend names the linkmo project's folder and its answers file as sources, so the coverage sweep counts them.</li> <li><strong>Changed</strong>: <code>./ai</code> now runs the linkmo project's generated command line, so the CLI concept cites <code>ai-risk-ontology-linkmo/src/ai_linkmo/cli.py</code> and <code>AI_LINKMO_MODE</code>; <code>lib/cli/</code> and <code>lib/api/api.yaml</code> are gone.</li> <li><strong>Changed</strong>: the FastAPI backend is the linkmo project's app over ai-linkmo's handlers since 0.5.0; <code>api.yaml</code>, <code>exposure.py</code> and <code>server_kernel.py</code> are gone, and the store switch is <code>AI_LINKMO_BACKEND</code>.</li> <li><strong>Changed</strong>: the linkmo project builds the browse databases, under <code>ai-risk-ontology-linkmo/browse</code> and <code>browse-byod</code>, since <code>lib/browse/</code> was removed.</li> <li><strong>Changed</strong>: the web UI's entity list is written from the linkmo project's exposure file, which replaced <code>lib/api/api.yaml</code>.</li> <li><strong>Changed</strong>: BYOD names the exposure file, which now declares the <code>byod</code> parameter.</li> <li><strong>Changed</strong>: the store switch is <code>AI_LINKMO_BACKEND</code> since 0.5.0, as <code>lib/store/source.py</code> says.</li> <li><strong>Changed</strong>: the source map names the linkmo project's files in place of <code>lib/cli/</code>, <code>lib/api/api.yaml</code>, <code>exposure.py</code>, <code>server_kernel.py</code> and <code>lib/browse/</code>.</li> <li><strong>Changed</strong>: the browse database with your files is built by <code>just build-browse-byod</code>, since <code>just build-browse</code> builds the packaged data alone.</li> <li><strong>Changed</strong>: the source map's exclusions name <code>docs/threat-model.md</code> and <code>.github/workflows/lint-and-docs.yaml</code>, both added in #123, so every tracked file keeps a place in the map.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-10-18 2026-10-18T00:31:39Z 2026-10-18T00:31:39Z <ul> <li><strong>Changed</strong>: the source map names the three generator scripts beside the rows they serve, the sync's pull request template beside the sidecar, and the repository plumbing and <code>llms.txt</code> it leaves out, so every tracked file has a place in it.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-10-17 2026-10-17T00:53:26Z 2026-10-17T00:53:26Z <ul> <li><strong>Changed</strong>: EU AI Act requirements dataset lists <code>byo/data/eu_ai_act.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: FFIEC IT Handbook dataset lists <code>byo/data/ffiec_it_handbook.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: FINOS AI Governance Framework dataset lists <code>byo/data/finos-aigf.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: ISO/IEC 42001 controls dataset lists <code>byo/data/iso_42001.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: Knowledge-graph export (YAML + Cypher) lists <code>graph</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: NIST AI 600-1 GenAI profile dataset lists <code>byo/data/nist_ai_600_1.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: NIST AI RMF crosswalks lists <code>graph</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: NIST SP 800-53 r5 controls dataset lists <code>byo/data/nist_sp_800_53_r5.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: OWASP Top 10 for LLM Applications dataset lists <code>byo/data/owasp_llm_top_10.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: OWASP ML Security Top 10 dataset lists <code>byo/data/owasp_ml_top_10.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: DuckDB record store lists <code>lib/store</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: SR 11-7 model risk management dataset lists <code>byo/data/sr_11_7.yaml</code> under <code>sources</code>, so the work list compares it; <code>resource</code> keeps its URL, because <code>lokf export</code> reads a relative <code>resource</code> as a concept id.</li> <li><strong>Changed</strong>: the <code>resource</code> of Risk is now the repository path <code>docs/key-concepts.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Obligation is now the repository path <code>docs/key-concepts.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Taxonomy is now the repository path <code>docs/key-concepts.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Evaluation is now the repository path <code>docs/key-concepts.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Control / Action is now the repository path <code>docs/key-concepts.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Incident is now the repository path <code>docs/key-concepts.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Bring Your Own Data is now the repository path <code>docs/key-concepts.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Crosswalk is now the repository path <code>docs/key-concepts.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Neo4j Graph Database is now the repository path <code>graph</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of AI-LinkMO CLI is now the repository path <code>lib/cli</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of FastAPI Backend is now the repository path <code>lib/api</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Datasette browse UI is now the repository path <code>lib/browse</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> of Svelte Web UI is now the repository path <code>lib/frontend</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> and the 2 <code>sources</code> entries of Why linked AI governance are now repository paths, <code>docs/architecture.md</code> first, in place of GitHub addresses, so the work list sees when they move.</li> <li><strong>Changed</strong>: the <code>resource</code> and the 3 <code>sources</code> entries of What AI-LinkMO adds to AI Atlas Nexus are now repository paths, <code>docs/for-the-curious.md</code> first, in place of GitHub addresses, so the work list sees when they move.</li> <li><strong>Changed</strong>: the <code>resource</code> of Bring your own data (BYOD) is now the repository path <code>docs/working-with-the-data.md</code>, in place of its GitHub address, so the work list sees when it moves.</li> <li><strong>Changed</strong>: the <code>resource</code> and the 7 <code>sources</code> entries of Install and run AI-LinkMO are now repository paths, <code>docs/install.md</code> first, in place of GitHub addresses, so the work list sees when they move.</li> <li><strong>Changed</strong>: the <code>sources</code> entry of DuckDB record store is now the repository path <code>docs/working-with-the-data.md</code>, in place of its GitHub address, so the work list sees when it moves. Its <code>resource</code> keeps the GitHub address, since <code>lokf export</code> reads a path there as a concept id when it writes <code>datasets.jsonld</code>.</li> <li><strong>Provenance</strong>: FINOS AI Governance Framework dataset, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against <code>byo/data/finos-aigf.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: ISO/IEC 42001 controls dataset, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against <code>byo/data/iso_42001.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: NIST AI 600-1 GenAI profile dataset, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against <code>byo/data/nist_ai_600_1.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: NIST SP 800-53 r5 controls dataset, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against <code>byo/data/nist_sp_800_53_r5.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: OWASP Top 10 for LLM Applications dataset, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against <code>byo/data/owasp_llm_top_10.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: OWASP ML Security Top 10 dataset, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against <code>byo/data/owasp_ml_top_10.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: SR 11-7 model risk management dataset, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against <code>byo/data/sr_11_7.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: NIST AI Risk Management Framework, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against its NIST page and the crosswalk files and needed no change.</li> <li><strong>Provenance</strong>: NIST AI 600-1 (Generative AI Profile), which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against the publication its DOI resolves to and needed no change.</li> <li><strong>Provenance</strong>: NIST SP 800-53 Revision 5, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against the publication its DOI resolves to and needed no change.</li> <li><strong>Provenance</strong>: OWASP Top 10 for LLM Applications, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against genai.owasp.org and needed no change.</li> <li><strong>Provenance</strong>: FINOS AI Governance Framework, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against the framework's site and <code>byo/data/finos-aigf.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: EU Artificial Intelligence Act, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against the AI Act Explorer and <code>byo/data/eu_ai_act.yaml</code> and needed no change.</li> <li><strong>Provenance</strong>: ISO/IEC 42001, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against the Internet Archive's copy of its ISO page from 2026-10-06, since iso.org refuses automated reads, and needed no change.</li> <li><strong>Provenance</strong>: FFIEC IT Examination Handbook, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against the Internet Archive's copy of the handbook's home page from 2026-05-12, since the site refuses automated reads, and needed no change.</li> <li><strong>Provenance</strong>: The FINOS concept, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against finos.org and the <code>byo/data/</code> file headers and needed no change.</li> <li><strong>Provenance</strong>: The IBM concept, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against the ai-atlas-nexus site and <code>pyproject.toml</code> and needed no change.</li> <li><strong>Provenance</strong>: The Noel McLoughlin concept, which a librarian run created on 2026-08-05, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>. It was re-read today against <code>pyproject.toml</code>, <code>LICENSE</code> and the GitHub profile and needed no change.</li> <li><strong>Changed</strong>: NIST AI RMF crosswalks says the IBM Risk Atlas file names its mapping columns <code>closeMatch</code> and the like, as its header row does. The <code>fields</code> list matches the other two files only. The concept, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>.</li> <li><strong>Changed</strong>: AI Risk Ontology names the two views its source names, an AI risk view and an AI model view, where it said a System view and a Risk view. The concept, which the librarian wrote at the bootstrap on 2026-07-13, now has a <code>generated</code> record in place of the OKF v0.1 <code>timestamp</code>.</li> <li><strong>Open question</strong>: OWASP ML Security Top 10: <a href="https://owasp.org/www-project-machine-learning-security-top-10/">https://owasp.org/www-project-machine-learning-security-top-10/</a> now redirects to <a href="https://owasp.org/projects/machine-learning-security-top-10">https://owasp.org/projects/machine-learning-security-top-10</a>, which answers 404 (checked 2026-10-17). The project page is at <a href="https://owasp.org/projects/machine-learning-security-top-ten">https://owasp.org/projects/machine-learning-security-top-ten</a>. <code>byo/data/owasp_ml_top_10.yaml</code> still cites the first address, and the source map asks that the two match. Which address should this reference cite?</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-10-16 2026-10-17T00:53:26Z 2026-10-17T00:53:26Z <ul> <li><strong>Prose</strong>: reworded 17 concept bodies in plain English. No fact, link, number or frontmatter changed.</li> <li><strong>Changed</strong>: What AI-LinkMO adds names what the library loads, which the earlier change today had left two sentences away.</li> <li><strong>Changed</strong>: BYOD no longer says every access pattern picks up your files. The Cypher export refuses <code>--byod</code>, as <code>docs/neo4j.md</code> and <code>docs/working-with-the-data.md</code> say.</li> <li><strong>Changed</strong>: Why linked AI governance gets a description that names the four doors, as the README and the architecture page now do, and cites both pages it draws on.</li> <li><strong>Changed</strong>: Taxonomy says a catalogue of risks and controls, as the table in <code>docs/key-concepts.md</code> says, where it said risks or controls.</li> <li><strong>Rewrite</strong>: Why linked AI governance follows <code>docs/architecture.md</code> as it now reads: the missing catalogue, the four doors with the stakeholders the page names, and the couplet. Claims the page does not make were dropped, and <code>docs/working-with-the-data.md</code> is cited for the BYOD paragraph.</li> <li><strong>Changed</strong>: What AI-LinkMO adds says curate mode adds, edits and deletes records and that the lookups follow the packaged relationships through the library, as <code>docs/for-the-curious.md</code> says. It now cites its sources, among them <code>docs/cli-examples.md</code> for the CLI examples run as tests.</li> <li><strong>Changed</strong>: Install and run cites <code>docs/install.md</code> as its resource, where the README's install steps moved in #62, and lists every page its steps come from. The steps still match those pages.</li> <li><strong>Changed</strong>: Bring your own data says curate mode adds, edits and deletes records, as <code>docs/working-with-the-data.md</code> says.</li> <li><strong>Changed</strong>: AI-LinkMO CLI no longer says it is built from the OpenAPI specification, which #57 replaced with <code>lib/api/api.yaml</code> and the schema, and says the tests run most of the listed commands, as <code>docs/cli-examples.md</code> says.</li> <li><strong>Changed</strong>: FastAPI Backend's documentation link names <code>lib/api/README.md</code>, since <code>lib/api/openapi.yaml</code> was deleted in #57, and its description no longer says the endpoints come from an OpenAPI specification.</li> <li><strong>Changed</strong>: the source map places the §What it looks like examples on the architecture page, where #62 moved them from the README.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-10-14 2026-10-14T02:18:30Z 2026-10-14T16:49:18Z <ul> <li><strong>Changed</strong>: the source map's exclusions name <code>.assets/</code>, where the screenshots and logos moved from <code>byo/images/</code>.</li> <li><strong>Migration</strong>: <code>base_iri</code> moved from <code>https://github.com/noelmcloughlin/ai-linkmo/knowledge/</code>, a path space GitHub owns, to <code>https://noelmcloughlin.github.io/ai-linkmo/knowledge/</code>, where the knowledge-website workflow now publishes each concept, so every concept <code>id</code> resolves to its page. The publisher <code>id</code>, every concept <code>id</code> and every typed-relation target moved with it; <code>resource</code> and <code>distribution</code> links are unchanged.</li> <li><strong>Prose</strong>: reworded 10 concept bodies in plain English. No fact, link, number or frontmatter changed.</li> <li><strong>Removal</strong>: DuckDB record store, recreated in the same run without a key a Dataset does not take.</li> <li><strong>Added</strong>: DuckDB record store, from <code>https://github.com/noelmcloughlin/ai-linkmo/tree/main/lib/store</code>.</li> <li><strong>Changed</strong>: DuckDB record store cites <code>docs/working-with-the-data.md</code> under <code>sources</code>, since a Dataset takes no <code>documentation</code> key.</li> <li><strong>Changed</strong>: AI-LinkMO CLI rewritten for the CLI generated from <code>lib/api/api.yaml</code> and the schema since #57; it said the CLI read <code>lib/api/openapi.yaml</code>, which is gone.</li> <li><strong>Changed</strong>: FastAPI Backend rewritten for the kernel that registers endpoints from <code>lib/api/api.yaml</code> and the schema since #57; <code>server_dynamic.py</code> and <code>openapi.yaml</code> are gone, and the listings can read the DuckDB store.</li> <li><strong>Changed</strong>: Svelte Web UI says the entity list and the record form are generated, from <code>lib/api/api.yaml</code> and the JSON Schema, as <code>lib/frontend/README.md</code> says since #57.</li> <li><strong>Changed</strong>: Neo4j Graph Database says the Cypher is fetched from ai-atlas-nexus with <code>just fetch-cypher</code>, not generated here, and that <code>--byod</code> is refused, as <code>docs/neo4j.md</code> says since #57.</li> <li><strong>Changed</strong>: Knowledge-graph export says the Cypher distribution is ai-atlas-nexus's own, fetched at the installed version's tag, since #57 removed <code>graph/cypher/export.py</code>.</li> <li><strong>Changed</strong>: Install and run now derives from <code>docs/install.md</code>, where #62 moved the README's install steps; the graph step fetches the Cypher, and a step for the store, search and Datasette is added.</li> <li><strong>Changed</strong>: Bring your own data says the Cypher export refuses <code>--byod</code> and that the store and browse UI load your files, as <code>docs/working-with-the-data.md</code> says since #57.</li> <li><strong>Changed</strong>: Why linked AI governance now cites <code>docs/architecture.md</code>, where #62 moved the README's two sections; the argument is unchanged.</li> <li><strong>Changed</strong>: BYOD names <code>lib/api/api.yaml</code> for the <code>byod</code> parameter, since <code>openapi.yaml</code> was removed in #57.</li> <li><strong>Added</strong>: DuckDB record store, from <code>lib/store/</code>, the justfile and <code>docs/working-with-the-data.md</code>; #57 added it and no concept covered it.</li> <li><strong>Added</strong>: Datasette browse UI, from <code>lib/browse/</code>, the justfile and <code>docs/working-with-the-data.md</code>; #57 added it and no concept covered it.</li> <li><strong>Changed</strong>: the source map follows #57 and #62: the API and CLI rows name <code>lib/api/api.yaml</code> and <code>exposure.py</code>, the graph row the fetched Cypher, the install and rationale rows <code>docs/install.md</code> and <code>docs/architecture.md</code>; rows added for the store and the browse UI, and <code>website/</code> and <code>docs/elements</code> left out on purpose.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-09-25 2026-09-25T20:35:35Z 2026-09-25T20:35:35Z <ul> <li><strong>Glossary follows the README split</strong>: the six terms now cite <code>docs/key-concepts.md</code>, where the table moved, and <code>glossary/incident</code> and <code>glossary/evaluation</code> are new drafts for the two rows the table gained, each checked against its endpoint and an example id in the packaged data.</li> <li><strong>Cypher export scope corrected</strong>: <code>datasets/knowledge-graph-export</code>, <code>services/graph-db</code> and <code>playbooks/bring-your-own-data</code> said BYOD files reach every door; the Cypher export runs <code>graph/cypher/export.py</code>, which loads packaged data only, so only the YAML export includes them.</li> <li><strong>Install and BYOD playbooks re-walked</strong>: <code>install-and-run</code> follows the new README, install notes and Neo4j page (<code>uv sync --extra test</code>, <code>npm ci</code>, <code>--isDefinedByTaxonomy</code> in place of a <code>--taxonomy</code> flag that does not exist, the CI test command), and the BYOD validation path gains its missing <code>schema/</code> segment.</li> <li><strong>SR 11-7 superseded</strong>: SR 26-2 replaced it on 2026-04-17 and its URL now returns 404, so <code>references/sr-11-7</code> says so, cites SR 26-2, and is a draft with an open question for the curator.</li> <li><strong>New explanation</strong>: <code>explanations/what-ai-linkmo-adds</code> records what the repository adds over AI Atlas Nexus and the provenance its records lack, from the README and <code>docs/for-the-curious.md</code>.</li> <li><strong>Source map updated</strong>: <code>playbooks/knowledge-sources</code> names the <code>docs/</code> pages the README now delegates to, and re-decides the exclusions; 35 concepts re-confirmed against their sources, while FFIEC, ISO and OWASP ML keep their older check because their sites refused or broke the fetch.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-09-23 2026-09-23T22:48:00Z 2026-09-23T22:48:00Z <ul> <li> <p><strong>The docent records a reader's gap without reading the file it goes in.</strong> The sidecar now carries <code>knowledge-feedback.sh</code>, so ktl-docent hands over its own entry and never opens <code>.lokf/feedback.md</code>, where other readers' free text would enter its session (Snyk W011).</p> </li> <li> <p><strong>The scheduled librarian installs its skill from a tag that has it.</strong> The pin read <code>v0.19.7</code>, where the skills are named <code>lokf-*</code>, so the install step (not gated on <code>KNOWLEDGE_LIBRARIAN_ENABLED</code>) failed on every run. It moves to <code>v0.23.0</code>. The scripts under <code>.lokf/scripts/</code> and <code>knowledge-registrar.yaml</code> now match that release's templates: the gate runs <code>lokf validate --check-refs</code>, and every bundle path is read with <code>core.quotePath</code> off.</p> </li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-09-18 2026-09-18T00:26:39Z 2026-09-18T00:26:39Z <ul> <li><strong>Sidecar brought up to the skills templates</strong>: the wrapper here predated the <code>EXIT</code>-trap restore and the registrar gate still read confirmations by their <code>by:</code> line. Synced all five scripts - the conventions pair is new to this repository - added <code>.gitattributes</code>, and bumped <code>LOKF_SKILLS_REF</code> from <code>v0.9.0</code> to <code>v0.19.2</code>. The release workflow now checks release notes and the pull request title on a releasing pull request.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-09-12 2026-09-12T23:34:04Z 2026-09-22T23:29:48Z <ul> <li><strong>Toolkit upgrade 0.6.0 -&gt; 0.7.0</strong> (minor - PyPI shows no breaking-change notice; the bundle validated unchanged both before and after): bumped the <code>lokf</code> floor in <code>pyproject.toml</code> to <code>lokf[build]&gt;=0.7.0</code> and ran <code>uv sync</code>.</li> <li><strong>Steady-state refresh - no drift.</strong> Drift surface since the 2026-08-28 run is empty: <code>git diff</code> between that run's commit (<code>36354c4</code>) and current HEAD (<code>350d533</code>) touches no file outside <code>.lokf/</code>, <code>.claude/skills/</code>, <code>.agents/</code>. Spot-verified against the live tree: <code>byo/data/</code> still 9 files with unchanged AUTOGENERATED headers/bodies (the <code>eu_ai_act.yaml</code>/<code>ffiec_it_handbook.yaml</code> header-vs-body class-name mismatch noted 2026-08-28 is still present, still a repo bug outside this bundle's write scope); <code>graph/*.csv</code> still 3 crosswalk files; <code>openapi.yaml</code> still 28 paths; <code>lib/cli</code>, <code>lib/api</code>, <code>lib/frontend</code> (Svelte 5.55 + Vite 8, port-5173 proxy) unchanged; README §Key concepts table still backs all six <code>glossary/</code> terms; <code>org/finos</code> and <code>org/ibm</code> resources unchanged. All 39 concepts re-confirmed against their <code>resource</code>/<code>derivedFrom</code>/<code>source</code> and given a fresh <code>verified: [{by: process:ktl-librarian, at: 2026-09-12T00:00:00Z}]</code> event (none of them had ever recorded one before this run). No concept content changed, none deleted, no <code>human:</code> text touched.</li> <li><strong>Source map updated.</strong> Two new repo-root artifacts from an unrelated skill-tooling change (the <code>.claude/skills/*</code> -&gt; <code>.agents/skills/*</code> move, still uncommitted) needed a call: <code>.agents/</code> (skill definitions - same exclusion as <code>.claude/</code>) and <code>skills-lock.json</code> (skill-install lockfile). Both added to <code>playbooks/knowledge-sources.md</code>'s conscious-exclusion list - they are tooling, not project knowledge.</li> <li><strong>Still pending from 2026-08-05</strong>: the <code>base_iri</code> migration finding (<code>github.com/...</code> -&gt; a namespace the project controls, proposed <code>https://w3id.org/ai-linkmo/knowledge/</code>) remains unresolved, awaiting human sign-off.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-08-28 2026-08-28T09:52:57Z 2026-09-22T23:29:48Z <ul> <li><strong>Toolkit upgrade 0.4.0 -&gt; 0.6.0</strong> (0.6.0 realizes the LOKF v0.2 format; no breaking schema changes surfaced - the bundle validated unchanged before any edits): bumped the <code>pyproject.toml</code> dependency to <code>lokf[build]&gt;=0.6.0</code> (the <code>[build]</code> extra now supplies <code>linkml</code>, so the independent <code>linkml</code> pin was dropped per the step-5 rule) and lowered <code>requires-python</code> to <code>&gt;=3.10</code> to match the toolkit's own floor. Declared the bundle's target format accordingly: root <code>index.md</code> <code>lokf_version</code>/<code>okf_version</code> <code>"0.1"</code> -&gt; <code>"0.2"</code>.</li> <li><strong>Steady-state refresh</strong> (drift surface since the 2026-08-12 run is exactly commit <code>36354c4</code>, "updated files for latest ai-atlas-nexus schema"): two dataset concepts had drifted and were corrected, both now carrying v0.2 <code>generated</code> provenance (<code>by: process:ktl-librarian</code>) in place of the superseded <code>timestamp</code>: <ol> <li><code>datasets/eu-ai-act</code> - the encoding's taxonomy row is now <code>type: RiskTaxonomy</code> (was <code>Taxonomy</code>); Format line updated.</li> <li><code>datasets/ffiec-it-handbook</code> - the taxonomy row is now <code>type: RiskControlGroupTaxonomy</code>, and each of the 11 booklet groups is now <code>type: RiskControlGroup</code> wired to the taxonomy via <code>isDefinedByTaxonomy</code>; Format line updated. <code>datasets/finos-aigf</code> was re-verified against the same commit (its <code>hasStakeholder</code> slot went single- to multivalued) - the concept records the file at knowledge_graph-YAML level, so no recorded fact drifted and it is untouched. All other sources: unchanged in git since the last run; <code>byo/data</code> still 9 files with AUTOGENERATED headers and matching <code>url:</code> fields, <code>openapi.yaml</code> still 28 paths (<code>/taxonomy</code>, <code>/risk</code>, <code>/crosswalk</code> endpoints confirmed). No new concepts, no orphans, source map unchanged (the knowledge geography is the same). <strong>Repo bug found, outside the bundle's write scope</strong>: the AUTOGENERATED 3-line headers of <code>byo/data/eu_ai_act.yaml</code> and <code>byo/data/ffiec_it_handbook.yaml</code> still name the old classes (<code>Taxonomy</code>) while their bodies carry the new ones - the concepts record the body truth; the headers need regeneration upstream. <strong>Still pending from 2026-08-05</strong>: the <code>base_iri</code> migration finding (<code>github.com/...</code> -&gt; a namespace the project controls, proposed <code>https://w3id.org/ai-linkmo/knowledge/</code>) remains unresolved, awaiting human sign-off.</li> </ol> </li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-08-12 2026-08-12T00:52:22Z 2026-08-12T00:52:22Z <ul> <li><strong>Toolkit upgrade 0.3.0 -&gt; 0.4.0</strong> (minor, additive - Diátaxis support, a CLI <code>--version</code> option, and an Apache-2.0 licence change; no breaking schema changes, so no human sign-off needed per the librarian's step-5 rule): bumped the <code>lokf</code> floor in <code>pyproject.toml</code> to <code>&gt;=0.4.0</code> and ran <code>uv sync</code>. The bundle validated unchanged against the new schema before any edits.</li> <li><strong>Diátaxis facet applied</strong> to all 32 existing concepts (<code>genre</code>, new in LOKF 0.4.0): 2 how-to (<code>playbooks/install-and-run</code>, <code>playbooks/bring-your-own-data</code> - both terse numbered recipes that assume competence, so how-to rather than tutorial), the remaining 30 <code>reference</code>. Judgement call worth flagging for review: <code>playbooks/knowledge-sources</code> is typed <code>Playbook</code> but tagged <code>genre: reference</code>, because its body is a per-source lookup table rather than an ordered procedure - type and genre are orthogonal by design, so this is legal, but a reviewer may prefer <code>how-to</code>.</li> <li><strong>Two gaps promoted from the conscious-exclusion list</strong>, both re-opened by 0.4.0 making understanding-oriented prose a first-class type. The 2026-08-10 run excluded README §The Problem, §What AI-LinkMO Does and its glossary subsection as "restating facts already captured in <code>services/*</code> and <code>references/*</code>"; that reasoning held for <em>mechanics</em> but not for <em>rationale</em> or <em>vocabulary</em>: <ol> <li>Six <code>glossary/</code> GlossaryTerms from README §Key concepts, in plain English (Taxonomy, Risk, Control / Action, Obligation, Crosswalk, BYOD), each <code>definedBy</code> the AI Risk Ontology and each verified code-backed (<code>/taxonomy</code>, <code>/risk</code>, <code>/control</code>, <code>/action</code>, <code>/obligation</code>, <code>/crosswalk</code> endpoints and the <code>byod</code> parameter in <code>openapi.yaml</code>). Control and Action are kept as one term because the README defines them jointly - splitting them would have meant inventing two definitions the source does not give.</li> <li><code>explanations/why-linked-ai-governance</code> (<code>type: Explanation</code>, <code>genre: explanation</code>) capturing the README's opening argument - framework fragmentation, manual mapping, the governance/engineering language gap, and why one shared ontology is what makes the traceability auditable. Bundle grew 32 -&gt; 39 concepts. Updated <code>playbooks/knowledge-sources.md</code> with two new source rows and rewrote the exclusion paragraph to record what was promoted and what stays out (§About Trustworthy AI, "What that looks like in practice", §Roadmap - all unchanged).</li> </ol> </li> <li><strong>Steady-state refresh</strong> (same run, no drift found): re-verified all 32 pre-existing concepts against recorded provenance - <code>byo/data/*.yaml</code> still 9 files with matching AUTOGENERATED headers and <code>url:</code> fields, <code>graph/</code> and <code>graph/cypher/</code> unchanged, <code>openapi.yaml</code> still 28 paths, all four services still match current code, README section structure still matches the source map. No concepts deleted.</li> <li><strong>Validation</strong>: <code>just lokf-validate</code> -&gt; <code>OK — 39 concepts in knowledge validate against KnowledgeBundle</code>. <code>lokf convert --format ttl</code>: 424 triples, 39 subjects, all inside the knowledge namespace, zero dangling internal relation targets; genre distribution 36 reference / 2 how-to / 1 explanation. All relative markdown links in the bundle resolve. <strong>Still pending from 2026-08-05</strong>: the <code>base_iri</code> migration finding (<code>github.com/...</code> -&gt; a namespace the project controls) remains unresolved, awaiting human sign-off. The seven new concepts were minted under the existing base for consistency and will need rewriting along with the rest when it moves.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-08-10 2026-08-10T10:34:38Z 2026-08-10T10:34:38Z <ul> <li><strong>Steady-state refresh</strong> (triggered by a README rewrite in the same session): re-verified all 32 concepts against recorded provenance - <code>byo/data/*.yaml</code> still 9 files, <code>graph/</code> and <code>graph/cypher/</code> contents unchanged, all four service concepts (<code>cli</code>, <code>fastapi-backend</code>, <code>web-ui</code>, <code>graph-db</code>) still match current code and commands. The README rewrite added business-framing narrative (§The Problem, §What AI-LinkMO Does incl. a plain-English glossary, §About Trustworthy AI reframed) and a new §Roadmap section naming <a href="https://github.com/asago-ai/asago-policy-mapper">asago-policy-mapper</a> as a possible future upstream integration, and reorganized existing content under new headers (§Quick Start, §Working With the Data) without changing any facts - also fixed a <code>./ai graph cyper</code> -&gt; <code>./ai graph cypher</code> typo, which already matched <code>services/graph-db</code>'s recorded command, so no concept drift. Updated <code>playbooks/knowledge-sources.md</code>: retitled the install/BYOD source-map rows to the new section names, and added the new narrative sections plus §Roadmap to the conscious-exclusion list - Roadmap's asago-policy-mapper mention is not code-backed in this repo (no dependency, no integration point), so no <code>references/</code>/<code>services/</code> concept was minted; promote it once a real integration lands. No new concepts, no orphans found. <code>lokf validate</code> (run via <code>.venv/bin/lokf</code> with <code>.venv/bin</code> on PATH, since neither <code>uv</code> nor <code>just</code> are on PATH in this environment): <code>OK — 32 concepts in knowledge validate against KnowledgeBundle</code>. Toolkit version-floor check (step 5): completed later the same day via the PyPI JSON API (<code>uv</code> is unavailable in this environment) - latest release is 0.3.0, equal to the <code>&gt;=0.3.0</code> floor in <code>pyproject.toml</code>, so no bump needed.</li> <li><strong>Audit</strong> (same day, second run): full section-2 audit on top of the refresh - projected the bundle to RDF (<code>lokf convert --format ttl</code>): 32 subjects, all internal typed-relation targets resolve (zero dangling), no subjects minted outside the knowledge namespace. Verified all nine <code>byo/data/*.yaml</code> AUTOGENERATED headers and <code>url:</code> fields against the datasets' recorded formats and the references' <code>resource</code> URLs (all match, incl. dual-URL cases nist-sp-800-53-r5 and finos w3id), crosswalk CSV header row matches the <code>fields</code> list, <code>openapi.yaml</code> still 28 paths, orphan sweep of the repo tree found nothing unaccounted for. No knowledge changes from the audit itself. <strong>Still pending from 2026-08-05</strong>: the <code>base_iri</code> migration finding (<code>github.com/...</code> -&gt; a namespace the project controls) remains unresolved, awaiting human sign-off.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-08-05 2026-08-05T17:53:58Z 2026-08-05T18:35:20Z <ul> <li><strong>Steady-state refresh</strong>: re-verified all 31 concepts against their recorded provenance (all 9 <code>byo/data/*.yaml</code> files present, all graph files present, <code>openapi.yaml</code> unchanged at 28 paths, all 4 services stable). Swept for orphans: no new concepts warranted. Fixed one bug from the audit: the bundle-root <code>index.md</code> declared <code>publisher.id = .../org/noel-mcloughlin</code> with no backing concept and the wrong <code>type: Organization</code>. Created <code>org/noel-mcloughlin.md</code> (<code>type: Person</code>, <code>resource: https://github.com/noelmcloughlin</code>, <code>timestamp: 2026-08-05T00:00:00Z</code>); corrected publisher type to <code>Person</code>; updated <code>org/index.md</code> and the root TOC. Bundle now has 32 concepts; <code>lokf validate</code> passes. <strong>Finding for review</strong>: <code>base_iri: https://github.com/noelmcloughlin/ai-linkmo/knowledge/</code> violates Rule 2 — GitHub owns that path space, so these identifiers can never be made to resolve. Proposed migration target: <code>https://w3id.org/ai-linkmo/knowledge/</code> (requires a w3id.org redirect PR). Migration touches every concept <code>id</code>, publisher <code>id</code>, and typed-relation target — needs human sign-off before proceeding.</li> <li><strong>Schema migration (lokf toolkit upgrade)</strong>: upgraded the lokf toolkit, which ships <code>lokf validate</code> (was previously unavailable). Running <code>lokf validate knowledge</code> against the upgraded schema (now backed by <code>linkml-validate</code>) revealed three breaking changes from the old <code>convert</code>-only validation: <ol> <li><code>timestamp</code> — changed from date-only (<code>YYYY-MM-DD</code>) to ISO 8601 datetime with timezone (<code>YYYY-MM-DDTHH:MM:SSZ</code>). Fixed across all 31 concepts.</li> <li><code>distribution</code> — changed from a plain list of URL strings to a list of <code>Distribution</code> objects (<code>access_url</code>, <code>name</code>, <code>media_type</code>). Fixed in <code>datasets/knowledge-graph-export</code> and <code>datasets/nist-ai-rmf-crosswalks</code>.</li> <li><code>fields</code> — changed from a plain list of strings to a list of <code>Field</code> objects (<code>name</code>). Fixed in <code>datasets/nist-ai-rmf-crosswalks</code>. Result: <code>OK — 31 concepts in knowledge validate against KnowledgeBundle.</code></li> </ol> </li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-07-27 2026-07-29T15:07:17Z 2026-07-29T15:07:17Z <ul> <li><strong>Steady-state refresh</strong>: re-verified all 31 concepts against their recorded provenance (source-map paths, CLI/API OpenAPI wiring, frontend Svelte 5 + proxy config, graph export tooling, all 9 <code>byo/data/*.yaml</code> headers and <code>url:</code> fields, index completeness) and projected the bundle to RDF (278 triples, 31 subjects, no dangling internal relation targets). One drift fixed: the sidecar was renamed <code>lokf/</code> -&gt; <code>.lokf/</code> since the last run, so <code>playbooks/knowledge-sources.md</code> now names the <code>.lokf/</code> sidecar in its exclusion list (and makes <code>lib/frontend/STATUS.md</code> and the <code>knowledge-*.yaml</code> automation workflows conscious exclusions); the root README's LLM-visitors pointer to the bundle was repaired to <code>.lokf/</code>.</li> </ul> https://noelmcloughlin.github.io/ai-linkmo/knowledge/log#2026-07-13 2026-07-13T18:01:20Z 2026-09-22T23:29:48Z <ul> <li> <p><strong>Steady-state refresh</strong>: re-verified all 31 concepts against their recorded <code>resource</code>/<code>derivedFrom</code> provenance (manifest identity, CLI/API OpenAPI wiring, frontend constants, graph CSV headers, all 9 <code>byo/data/*.yaml</code> headers and <code>url:</code> fields, org/reference facts) - no drift found. Swept the full README table of contents for orphans: confirmed <code>/ares</code> and LLM inferencing are real, code-backed endpoints (<code>handlers.py</code>, <code>cli.py</code>, <code>vite.config.ts</code>) but already covered generically by the dynamic OpenAPI-driven CLI/API service concepts, so no new concept was minted. Extended <code>playbooks/knowledge-sources.md</code> with the consciously-excluded README sections (§LLM Inferencing, §ARES Evaluation, §ADOPT?, §Curate your own Open Data, §Building Python Applications, §Research) so future refreshes don't need to re-investigate them.</p> </li> <li> <p><strong>Bootstrap discovery</strong> (ktl-librarian): swept the repository and replaced the scaffold's placeholder services with 31 real concepts - 4 services (CLI, FastAPI backend, Svelte web UI, Neo4j graph DB), 11 datasets (knowledge-graph export, NIST AI RMF crosswalks, and the nine <code>byo/data/*.yaml</code> framework encodings), 11 references (the external authorities those datasets encode), 3 playbooks (knowledge-sources map, install-and-run, BYOD), and 2 organizations (FINOS, IBM). Recorded the scrape map as <code>playbooks/knowledge-sources.md</code>; rebuilt all section indexes and the root TOC.</p> </li> <li> <p><strong>Initialization</strong>: Scaffolded the LOKF bundle for AI-LinkMO with placeholder services. Real concepts to follow.</p> </li> <li> <p><strong>Validation skipped</strong>: <code>lokf validate</code> is not yet available in the toolkit (PyPI 0.2.0 and git main both lack the command). As a substitute, <code>lokf convert --format ttl knowledge</code> ran clean. Re-run validation once a toolkit release ships <code>validate</code> (the CI gate in <code>.github/workflows/knowledge-validate.yaml</code> will catch it).</p> </li> </ul>