Resolve ROOT-TODO-05: add source_audit_run + Generation Audit Ledger

Contributed from real-world use in the JLDN-Dev-Ecosystem project, which
extends this schema as part of a larger ecosystem. That project needed a
way to distinguish "never audited" from "audited, clean" -- a formal
audit pass that finds nothing previously left no artifact anywhere.

Adds an optional companion dataset (.dev/[GEN]/audit-log.json, Mode 2,
Section 2) written unconditionally including zero-finding runs, and a
new optional source_audit_run Object property on ISSUE tasks (Section 4)
that's bidirectional with the ledger's own finding_ids array, so a
claimed audit source is verifiable rather than merely asserted.

Author: JLDesignNetwork

.dev/backlog.json

@@ -64,5 +64,17 @@
     "target_files": [
       "docs/specification.md"
     ]
+  },
+  {
+    "id": "ROOT-TODO-05",
+    "title": "Add source_audit_run property and Generation Audit Ledger companion dataset",
+    "status": "completed",
+    "priority": "medium-1",
+    "protection": "protected",
+    "created_at": "2026-08-25T00:00:00+02:00",
+    "details": "Contributed from real-world use in the JLDN-Dev-Ecosystem project, which extends this schema as part of a larger ecosystem. That project built an audit-run ledger (.dev/[GEN]/audit-log.json) so a formal audit pass that finds nothing still leaves a record -- previously, a clean run left no artifact anywhere, making 'never audited' indistinguishable from 'audited, clean'. Codified here as an optional companion dataset (Mode 2, docs/specification.md Section 2) plus a new optional source_audit_run Object property on ISSUE tasks (Section 4), bidirectional with the ledger's own finding_ids array so a claimed audit source is verifiable rather than merely asserted.",
+    "target_files": [
+      "docs/specification.md"
+    ]
   }
 ]

CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to the **JLDN Backlog Schema Specification** will be documen
 The format is based on [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to the [JLDN Generational Versioning Schema (GVS)](https://github.com/JLDesignNetwork/Generational-Versioning-Schema).
 
+## [2608.22.0-bs] - 2026-08-25
+
+### Added
+- **`source_audit_run` Property**: New optional Object property on `ISSUE` tasks originating from a formal audit pass (`{generation, source, run_at}`). Bidirectional with a new optional companion dataset, the Generation Audit Ledger.
+- **Generation Audit Ledger**: New optional companion dataset, `.dev/[GEN]/audit-log.json` — an append-only record of every formal audit pass against a generation's work, written unconditionally including zero-finding runs, so "never audited" and "audited clean" remain distinguishable. Contributed from real-world use in the JLDN-Dev-Ecosystem project, which now extends this schema as part of a larger ecosystem.
+
 ## [2608.21.0-bs] - 2026-08-20
 
 ### Changed

README.md

@@ -5,7 +5,7 @@
     "rulesetName": "JLDN Backlog Schema",
     "type": "ruleset",
     "platform": "github:public",
-    "version": "2608.21.0-bs",
+    "version": "2608.22.0-bs",
     "backlog": ".dev/backlog.json",
     "changelog": "CHANGELOG.md"
   }

docs/specification.md

@@ -3,7 +3,7 @@
 > **Document:** `docs/specification.md`  
 > **Author:** Jeff Langdon (JL Design Network)  
 > **Standard:** JLDN Task & Backlog Management Protocol  
-> **Version:** `2608.21.0-bs`  
+> **Version:** `2608.22.0-bs`  
 
 ---
 
@@ -29,6 +29,7 @@ For large rulesets and software repositories, tasks are stored in companion JSON
 - Root Project Backlog: `.dev/backlog.json`
 - Generation Master Task Register: `.dev/[GEN]/backlog.json`
 - Generation Conceptual Proposals: `.dev/[GEN]/ideas.json`
+- Generation Audit Ledger *(Optional)*: `.dev/[GEN]/audit-log.json` — append-only record of every formal audit pass against this generation's work, written unconditionally (including zero-finding runs), so "never audited" and "audited clean" remain distinguishable. Referenced bidirectionally via `source_audit_run` (§4) on any `ISSUE` task the pass produces.
 
 ---
 
@@ -85,6 +86,7 @@ Every task adheres to the standard prefix taxonomy:
 * **`relates_to` (String, Optional):** Horizontal context association.
 * **`target_files` (Array of Strings, Optional):** Localized file tracking for isolated environments without git dependency.
 * **`target_version` / `target_component` / `target_repository` (String, Optional):** Optional pointers to eliminate cross-project reference ambiguity.
+* **`source_audit_run` (Object, Optional):** Present on `ISSUE` tasks originating from a formal audit pass (e.g. a Red Team review). Structure: `{generation, source, run_at}` — `generation` (GVS epoch the run occurred in), `source` (identifier for the audit or team that produced the finding, e.g. `"red"`), `run_at` (ISO-8601 timestamp of the run). Bidirectional with the companion audit ledger's own `finding_ids` array (§2) — a task's `source_audit_run` and the ledger entry's `finding_ids` cross-reference each other, so a claimed source is verifiable, not merely asserted.
 
 ---