# Validation and knowledge-base repair evidence

## Measured document checks

| Check | Before | After |
|---|---:|---:|
| Markdown pages scanned | 4 | 7 |
| Pages without inbound links | 1 (25%) | 0 |
| Pages stale against the 90-day review cadence | 1 (25%) | 0 |
| Pages missing owner metadata | 1 (25%) | 0 |
| Conflicting acronym definitions | 1 | 0 |
| Original runbook steps readable by the validator | 0; validation could not score the document | 3 |

The original ingester identified returns.md as the stale cleanup priority, care.md as the orphan and runbook.md as missing its owner. The original runbook validator stopped because the old page contained no steps; no numeric “before” validity score is claimed. The supplied structured runbook already had six fields per step and scored 100/100, but those instructions were absent from the knowledge-base page.

The original support-profile SOP generator produced the initial seven-section scaffold. Its generic engineering escalation, unfilled fields and bold step labels were replaced with the actual merchant workflow, named owners, complete recovery actions and Markdown step headings. The original Skill scripts were not changed.

## Final structural checks

| Delivered artifact | Parsed steps | Checks passed | Score |
|---|---:|---:|---:|
| Canonical runbook Markdown | 3 | 18 of 18 | 100/100 |
| Canonical SOP Markdown | 3 | 18 of 18 | 100/100 |
| Structured runbook JSON | 3 | 18 of 18 | 100/100 |

Each step passed owner, duration, observable success, observable failure, rollback and escalation checks. These are structural results, not merchant approval or proof that a live return completed.

Independent file checks confirmed all seven SOP sections, all canonical owner/review metadata, valid local links, at least two distinct inbound source pages per canonical Markdown page, and agreement between the ledger and its initial snapshot. Date arithmetic confirms 14 days; planning arithmetic confirms 10 active minutes, $5 labor per case and $260/year at 52 cases. The 16 [decision-table variations](decision-table.md) cover day 30/31, missing evidence, invalid dates, mismatched orders, condition/scope exceptions and blocked downstream gates.

## Interpretation limits

The final ingester still lists three glossary candidates: HM and BLUE are parts of the product code, and ID is already explicitly defined. Its acronym heuristic does not recognize every table definition. None is a conflicting definition; they were reviewed without inventing expansions. The original ingester's pre-repair CSM excerpts also span line breaks, so the conflicting terms were verified directly against the source pages.

The ingester counts inbound links and acronym patterns; it does not establish factual correctness, physical receipt or an actual approval. Content was therefore checked against the supplied merchant facts. No label, warehouse return address, return-fee decision, inspection result, approval reference or confirmed refund amount was supplied; A100 remains pending. No customer contact or payment was performed.