[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73GCREK9JV0K9ZP703T5A2R":3,"skill-same:01M73GCREK9JV0K9ZP703T5A2R":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M73GCREK9JV0K9ZP703T5A2R","evidence-ledger",null,"Fixed-column evidence ledger that traces every claim a decision depends on to a source, a reference, and a verification state. Use when: building or updating an evidence or citation ledger, verifying claims ahead of a gate ruling, or linking evidence into a decision record (ADR-0061).","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.agents\u002Fskills\u002Fevidence-ledger\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: evidence-ledger\ndescription: >\n  Fixed-column evidence ledger that traces every claim a decision depends on\n  to a source, a reference, and a verification state. Use when: building or\n  updating an evidence or citation ledger, verifying claims ahead of a gate\n  ruling, or linking evidence into a decision record (ADR-0061).\nversion: 1.1.0\nowner: pm\nstatus: active\nlast_reviewed: 2026-08-25\nscope: common\nmetadata:\n  type: process\n  triggers:\n    - evidence ledger\n    - citation ledger\n    - claim verification\n    - source verification\n    - evidence tracking\n---\n\n## Purpose\n\nDefines the common base format for evidence ledgers — the Evidence link of the Agent → Skill → Knowledge → Evidence → Rule → Decision chain (ADR-0061). A ledger row is the smallest unit of proof: one claim, where it came from, how it was checked, and whether it stands. Gate rulings and decision records cite ledger rows instead of re-deriving facts from prose.\n\n## Ledger Format\n\nEvery ledger uses the same five fixed columns:\n\n```\n| claim | source | url\u002Fref | verification | status |\n```\n\n| Column | Content |\n|--------|---------|\n| `claim` | The single assertion being evidenced — one claim per row, never a bundled paragraph |\n| `source` | Who or what asserts it (publication, filing, dataset, interviewee) |\n| `url\u002Fref` | The retrievable reference — URL, receipt number, docket ID, or file path |\n| `verification` | How the claim was checked, by whom, and when |\n| `status` | Current standing — e.g. `VERIFIED`, `UNVERIFIED`, `CONTESTED`, `SUPERSEDED` |\n\nRows are never rewritten to change history — see Append vs Supersede below.\n\n## Evidence Location Convention\n\n- `docs\u002Fevidence\u002Fledger.md` — the ledger itself (one table, or one section per topic)\n- `docs\u002Fevidence\u002Ffindings\u002F` — per-topic finding files holding detail too long for a row (methodology notes, excerpts, calculations); the ledger's `url\u002Fref` column links into them\n\n## Variant Overlays\n\nThe five columns are the common base. Variants MAY add requirements on top — stricter sourcing, extra columns, jurisdiction-specific citation rules — in the variant's own assets, never by editing this skill.\n\nCanonical overlay example: co-news requires **2+ independent sources per material claim** (`NEWS-R1`, registered inline in its context file) and instantiates the base format with claim \u002F source 1 \u002F source 2 \u002F receipt number \u002F status columns in its `source-verification-ledger` skill. The two source columns and the receipt-number column are the overlay; the row-per-claim, fixed-column, status-tracked discipline is the base.\n\nDocument-form overlay (co-consult, T-20261007-014): the `industry-research-pack` skill satisfies the same 2+ independent sources requirement in document shape — one document per source with a five-section per-source skeleton and figure-by-figure cross-validation against a named second source; a figure that lacks its second source carries the `⚠ SINGLE-SOURCE` warning mark instead of a ledger row. The pack is also a **citable substrate**: consumer deliverables cite its per-source documents per section rather than restating claims (the co-deck PR #135 contract — 114 slides citing per-slide source docs). Variants reaching the same discipline independently should teach one of these overlay forms rather than inventing a third convention.\n\n### Registry-backed overlays (formal-var form)\n\nSome registry-backed variants carry their evidence plane as FORMAL VARIABLES instead of a prose ledger — machine-checked rows in a schema-governed registry (e.g. an evidence-variable registry with run-scoped snapshots), with calibration corpora or finding files attached as provenance. That is a legitimate overlay form of this skill: the row-per-claim discipline becomes row-per-VARIABLE, `verification` becomes the registry's verification metadata, and supersession happens through the registry's own reversal\u002Famendment protocol. Whichever form a variant uses, decision records `evidence_refs[]` must resolve inside it — a registry key name for formal-var overlays, a ledger row ID for prose ledgers.\n\n## Append vs Supersede\n\n- **Append** when adding new evidence or a new verification pass — new rows, new finding files.\n- **Supersede** when a claim's standing changes (a source retracts, a verification fails, a stronger source arrives): keep the original row, set its `status` to `SUPERSEDED`, and add a new row whose `verification` notes what replaced it.\n- Never delete a row or overwrite a `verification` entry — the ledger must show what was believed, when, and why it changed.\n\n## Linking Evidence to Decision Records\n\nDecision records (see the `decision-record` skill) cite evidence through their `evidence_refs[]` frontmatter. Every entry must resolve to a ledger row (quote the claim text or a stable line ID) or a finding file under `docs\u002Fevidence\u002Ffindings\u002F`. A ruling that cites no evidence is incomplete; evidence that no ruling cites is unexamined background.\n","## Purpose\n\nDefines the common base format for evidence ledgers — the Evidence link of the Agent → Skill → Knowledge → Evidence → Rule → Decision chain (ADR-0061). A ledger row is the smallest unit of proof: one claim, where it came from, how it was checked, and whether it stands. Gate rulings and decision records cite ledger rows instead of re-deriving facts from prose.\n\n## Ledger Format\n\nEvery ledger uses the same five fixed columns:\n\n```\n| claim | source | url\u002Fref | verification | status |\n```\n\n| Column | Content |\n|--------|---------|\n| `claim` | The single assertion being evidenced — one claim per row, never a bundled paragraph |\n| `source` | Who or what asserts it (publication, filing, dataset, interviewee) |\n| `url\u002Fref` | The retrievable reference — URL, receipt number, docket ID, or file path |\n| `verification` | How the claim was checked, by whom, and when |\n| `status` | Current standing — e.g. `VERIFIED`, `UNVERIFIED`, `CONTESTED`, `SUPERSEDED` |\n\nRows are never rewritten to change history — see Append vs Supersede below.\n\n## Evidence Location Convention\n\n- `docs\u002Fevidence\u002Fledger.md` — the ledger itself (one table, or one section per topic)\n- `docs\u002Fevidence\u002Ffindings\u002F` — per-topic finding files holding detail too long for a row (methodology notes, excerpts, calculations); the ledger's `url\u002Fref` column links into them\n\n## Variant Overlays\n\nThe five columns are the common base. Variants MAY add requirements on top — stricter sourcing, extra columns, jurisdiction-specific citation rules — in the variant's own assets, never by editing this skill.\n\nCanonical overlay example: co-news requires **2+ independent sources per material claim** (`NEWS-R1`, registered inline in its context file) and instantiates the base format with claim \u002F source 1 \u002F source 2 \u002F receipt number \u002F status columns in its `source-verification-ledger` skill. The two source columns and the receipt-number column are the overlay; the row-per-claim, fixed-column, status-tracked discipline is the base.\n\nDocument-form overlay (co-consult, T-20261007-014): the `industry-research-pack` skill satisfies the same 2+ independent sources requirement in document shape — one document per source with a five-section per-source skeleton and figure-by-figure cross-validation against a named second source; a figure that lacks its second source carries the `⚠ SINGLE-SOURCE` warning mark instead of a ledger row. The pack is also a **citable substrate**: consumer deliverables cite its per-source documents per section rather than restating claims (the co-deck PR #135 contract — 114 slides citing per-slide source docs). Variants reaching the same discipline independently should teach one of these overlay forms rather than inventing a third convention.\n\n### Registry-backed overlays (formal-var form)\n\nSome registry-backed variants carry their evidence plane as FORMAL VARIABLES instead of a prose ledger — machine-checked rows in a schema-governed registry (e.g. an evidence-variable registry with run-scoped snapshots), with calibration corpora or finding files attached as provenance. That is a legitimate overlay form of this skill: the row-per-claim discipline becomes row-per-VARIABLE, `verification` becomes the registry's verification metadata, and supersession happens through the registry's own reversal\u002Famendment protocol. Whichever form a variant uses, decision records `evidence_refs[]` must resolve inside it — a registry key name for formal-var overlays, a ledger row ID for prose ledgers.\n\n## Append vs Supersede\n\n- **Append** when adding new evidence or a new verification pass — new rows, new finding files.\n- **Supersede** when a claim's standing changes (a source retracts, a verification fails, a stronger source arrives): keep the original row, set its `status` to `SUPERSEDED`, and add a new row whose `verification` notes what replaced it.\n- Never delete a row or overwrite a `verification` entry — the ledger must show what was believed, when, and why it changed.\n\n## Linking Evidence to Decision Records\n\nDecision records (see the `decision-record` skill) cite evidence through their `evidence_refs[]` frontmatter. Every entry must resolve to a ledger row (quote the claim text or a stable line ID) or a finding file under `docs\u002Fevidence\u002Ffindings\u002F`. A ruling that cites no evidence is incomplete; evidence that no ruling cites is unexamined background.\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":35,"last_reviewed":36},"pm","common","active","1.1.0",{"type":28,"triggers":29},"process",[30,31,32,33,34],"evidence ledger","citation ledger","claim verification","source verification","evidence tracking","Fixed-column evidence ledger that traces every claim a decision depends on to a source, a reference, and a verification state. Use when: building or updating an evidence or citation ledger, verifying claims ahead of a gate ruling, or linking evidence into a decision record (ADR-0061).\n",1787616000000,"main","1162ccc568cf90c01b3886d6143cbfd851a37883","templates\u002Fcommon\u002F.agents\u002Fskills\u002Fevidence-ledger",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill evidence-ledger",{"tool":51,"command":52},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill evidence-ledger",{"tool":54,"command":55},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill evidence-ledger","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fcommon\u002F.agents\u002Fskills\u002Fevidence-ledger\u002FSKILL.md",true,[],[60,68,73,78,83,88],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":69,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":67},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":74,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":67},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":79,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":67},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":84,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":67},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":89,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":67},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]