QA Results Curator
The auto-generated registry (Documents/RESULTS_REGISTRY.md) is a triage index.
This skill helps you produce curated, reproducible entries in Documents/RESULTS_CURATED.md.
Quick start
- •Refresh the triage signals:
- •
python tools/project_forensics.py --control-cutoff-utc-date 2026-01-10 - •
python tools/generate_results_registry.py --control-cutoff-utc-date 2026-01-10- •Anything with mtime before 2026-01-10 UTC is treated as legacy and must be re-vetted.
- •Build fast search (optional but recommended):
- •
python tools/qa_local_search.py --overwrite build
- •Pick candidates to curate:
- •
python tools/qa_forensics_cert_index.py view-get view:forensics/hotspot_top_k --limit 50 - •
python tools/qa_local_search.py search "witness pack" --top 20
- •Write curated entries (manual, not overwritten):
- •
Documents/RESULTS_CURATED.md
Curation workflow (claim → evidence → reproduce)
For each candidate “result node”:
- •Identify the claim
- •What is being asserted (1–3 sentences)?
- •Attach evidence
- •Prefer validator-verifiable artifacts (cert JSON, witness packs, bundles, logs with PASS markers).
- •Add reproduction commands
- •Exact command(s) + working directory.
- •If evidence is a QA cert family: run the family validator or
qa_meta_validator.py.
- •Mark status
- •
draftuntil you can reproduce. - •
verifiedonce reproduced and (where applicable) validated. - •
supersededif replaced by a newer, stronger, or corrected result.
Guardrails
- •Don’t manually edit
Documents/RESULTS_REGISTRY.md(it’s overwritten on regen). - •Prefer writing new execution artifacts under
_forensics/ortrace/(ledger them). - •Validation is part of the result: capture validator output (hashes/logs) as trace.
- •For pre-cutoff artifacts: mark entries
legacyuntil you have a post-cutoff reproduction run + evidence.