Content workflows produce a lot of advice. Some of it is grounded. Some of it is weak. Some depends on missing data, partial retrieval or assumptions that need manual verification. Kenji reviews the evidence behind the findings. He checks support strength, unsupported recommendations, provenance and limitations.
For content audits, approval workflows, evidence gap review, risk checks and any recommendation that needs to be defensible.
A recommendation can sound confident while resting on thin evidence. It may overreach from limited page signals, rely on missing retrieval, or imply certainty the workflow does not have. Kenji protects editors from false confidence.
↘ separate what is proven from what is assumedA recommendation reads as settled fact, but it actually rests on a single partial signal with no retrieval to back it up.
Kenji separates the supported findings from the weak ones and lists exactly what still needs manual verification.
Kenji reviews whether findings are supported by available source material, page signals, standards or retrieved context. He does not invent missing proof.
KENJI → Kenji checks what actually supports it before it reaches approval.
He reviews whether those claims have adequate support behind them.
Kenji checks the provenance of that context before it is relied on.
He gives Dana an evidence bundle to weigh as part of the readiness review.
Kenji reviews the support behind each finding to help editors judge which to trust.
He works alongside Vera to flag where evidence and compliance risk overlap.
Kenji does not certify truth, compliance or ranking impact. If evidence is missing, he says it is missing.
Kenji helps editors see which findings are grounded, which are weak and which need more evidence before approval.
