Skip to content

Content methodology

What is sourced, what is generated, and what still needs review.

This page describes the workflow implemented in the repository today. It is not a claim that every topic is complete or has a named technical reviewer.

Current workflow

From content record to maintained page

Independent technical review pending

1. Define the public record

A public topic or explainer is a source-controlled record with an explicit publication state. Public explainers live separately from the protected practice bank and carry no private question ID.

2. Attach sources to claims

Exam-owner facts and technical concepts list source IDs that resolve to visible source records. Product status and our own study advice are labeled separately from official exam facts.

3. Show the real review state

Current pages are publisher source-checked or marked technical review pending. No named specialist, credential, or independent-review claim is shown until a real reviewer record exists.

4. Recheck and correct

Each content record has a last source-check date, a next review date, and maintenance notes. Correction reports carry the page path into the server-handled contact workflow.

AI tutor boundary

Tutor responses are generated on request and may be incorrect. They are not publisher-reviewed study pages, official exam guidance, or a substitute for the cited source material. The workspace labels generated output and lets the learner choose which current context is sent.

Not official exam material

Keiko Study is independent and is not affiliated with or endorsed by an exam owner. Source links support stated facts; they do not turn our notes or original public questions into official test material.

Current source register

These are the source records currently used by published content. The license note describes how each record may be referenced; it is not a blanket license for exam-owner material.

Corrections and update policy

Use the correction form to identify the page and explain the issue. The server validates the public page path, applies length limits and a honeypot check, then stores the report in the server-only contact inbox when configured; an owner notification is best-effort. A report does not silently change published content. The source record and page are rechecked before an edit is shipped.