Date: 2026-02-23
Scope: Evidence tracking for completed checklist items in ISIS_TODOS_2.md.
Purpose#
Provide a strict format that links each completed task to verifiable delivery evidence:
- code change reference (commit/PR),
- executed verification commands,
- generated artifacts.
Authoritative Files#
- Machine-readable ledger:
docs/domains/isis/remediation-v2/ISIS_V2_EVIDENCE_LEDGER.json - Optional schema:
docs/domains/isis/remediation-v2/ISIS_V2_EVIDENCE_LEDGER.schema.json
Required Fields per Entry#
| Field | Type | Required | Description |
|---|---|---|---|
checklistId |
string | yes | Checklist ID from ISIS_TODOS_2.md (e.g., WS00-001). |
ticketKey |
string | yes | Generated remediation ticket key (e.g., ISIS2-00009). |
status |
enum | yes | DONE or VERIFIED. |
completedAt |
date-time | yes | ISO timestamp when task moved to done. |
commitSha |
string | yes | Commit containing implementation evidence. |
pullRequest |
string | no | PR reference if applicable. |
verificationCommands |
array[string] | yes | Commands run to validate implementation. |
verificationSummary |
string | yes | Concise summary of command outcomes. |
artifacts |
array[string] | yes | Artifact file paths proving completion. |
owner |
string | yes | Accountable owner/team. |
reviewedBy |
string | no | Reviewer/approver. |
notes |
string | no | Additional context/constraints. |
Usage Rules#
- Every
DONEchecklist task must have exactly one ledger entry. - Evidence entries must use immutable references (commit SHA + artifact path).
- Verification commands must be reproducible from repository state.
- If an entry is superseded, append a new entry and mark old one via notes; do not delete historical evidence.
Initial Example Entries#
See:
docs/domains/isis/remediation-v2/ISIS_V2_EVIDENCE_LEDGER.json
Traceability#
Primary checklist item:
WS00-009
Related:
WS00-001WS00-006