Part 6. Practice F. Validation Checklist

This checklist is the minimum bar to verify before handing a Vault to the next task. Rate each item PASS / WARN / FAIL. Do not make an operational handoff while any FAIL remains.

Rating criteria

Rating	Meaning	Action
PASS	Meets the standard	Continue to the next stage
WARN	Usable, but needs a record and follow-up	Note it in the handoff memo
FAIL	High risk of error if passed to a consuming task	Fix and validate again

Stage 1: Automated checks

Item	Standard	Rating	Notes
Stage-1 input coverage	Sources exist from the beginning, middle, and end of all key input documents
Stage-1 nine-category coverage	Every category has at least one item; document exceptions in the profile
Stage-2 canonical-key duplicates	0
Stage-2 required English-name omissions	0 for projects to be translated
Stage-2 unspecified version-status rate	5% or less
Stage-2 unspecified worldbuilding-axis rate	10% or less
Enum violations	0 violations of allowed values for category, worldbuilding_axis, or version
Stage-3 file count	Stage-2 CSV headword rows equal the number of `.md` headword files
YAML parsing	0 frontmatter parse failures
Filename conflicts	0 canonical-keyword filename conflicts
Broken links	0 missing wikilink targets, or a stub exists
Self-links	0 links that point to themselves
LLM completion rate	95% or above for operational handoff
Manifest consistency	Manifest progress agrees with actual file state

Stage 2: Manual sampling

Sample at least 30 items. Select a mix of hubs, middle-level entries, leaves, all nine categories, and every worldbuilding axis.

Item	Standard	Rating	Notes
Synonym groups	Canonical keywords and aliases refer to the same entity
Category fit	Each of the nine categories suits its narrative function
Worldbuilding-axis fit	The axis fits the IP structure
Definition quality	Gives self-contained meaning in one or two sentences
Detailed-description quality	Shows related headwords and operating context
LLM prose quality	Does not conflict with the hub tone standard
Translation notes	Entries with translation risk have adequate guidance
Source traceability	Can return to the original text or Stage-1 source
Over-linking	Related keywords are not inflated without meaning
Sensitive conflicts	No conflict with published LOREBOOKs or official text

Stage 3: Integration build checks

Item	Standard	Rating	Notes
Obsidian access	Vault opens normally
Graph display	Key hubs and link networks are not abnormally isolated
Consuming-skill reading	Headwords can be referenced in writing, lorebook, and translation work
Supporting documents	Required `aux_docs` registered in the manifest exist
Index	The complete headword list or index is current
Handoff record	The next worker can understand the status

Handoff checklist

## Handoff Checklist

- [ ] 0 FAILs in automated checks
- [ ] 0 FAILs in manual sampling
- [ ] Reasons and follow-up actions recorded for WARN items
- [ ] LLM completion rate of 95% or more
- [ ] Required supporting documents exist
- [ ] Confirm manifest `ready_for_consumption`
- [ ] No conflict with published LOREBOOKs or official text
- [ ] Share the version number with the next consuming task

handoff_status: ready_for_consumption / ready_with_warnings / not_ready
handoff_date:
handoff_owner:
handoff_note:

Operational decision

A Vault for personal practice may be used for learning even with WARN items or some incompleteness. An operational Vault handed to consuming skills, however, must pass this checklist. Loose standards save time early and repay the cost many times over in downstream errors.