One page owns one learner task
A lesson owns one primary search question, one observable Can-do, one slug, and one distinct practice scene. Hubs organize routes, Stories provide recall and transfer, and glossary entries provide short lookup answers. We do not create another URL when an existing page can answer the same question.
The live copy and the inventory have different jobs
Lesson and Story MDX files are the source for the wording you read and the publication status used by the build. The lesson inventory assigns intent, Can-do, scene, links, review, and media metadata. An older status label in that planning inventory does not publish or hide a page. Historical generators are records, not the source used to rebuild current lesson copy.
Evidence follows the claim
We do not add citations to stable, low-risk learning explanations merely to look authoritative. Claims that are high-risk or likely to change are checked against appropriate current primary or official sources, with their scope, check date, and limitations kept clear. Current professional, institutional, or local instructions take priority, and a language example never replaces professional advice. The medical and emergency policy states the practical safety boundary.
Automated checks are not qualified review
Automated checks can find schema, ownership, heading, link, and media problems. They cannot certify Japanese naturalness, politeness, regional fit, safety, factual currency, or artistic quality. “Verified automated” is not human approval. We use “reviewed” only when the appropriate human has completed the review and their name and date are recorded. Publication status and review status are separate, so a visible page can still state that review is required. The Japanese review policy defines those states.
Story approval applies to one exact version
An outline, batch plan, prompt, automated assessment, or general permission to continue is not approval of future wording. Before a rewritten Story is treated as approved, the exact text version is reviewed with its payoff, continuity, Japanese, safety boundaries, and matching images. A material text or scene change makes the dependent Story and visual reviews stale until they are checked again.
Publication status controls public discovery
For lessons, Stories, and glossary entries, the status in the live source controls routing. Draft and review items are excluded from normal public routes. Preview items can be opened directly but are noindex and excluded from public lists and discovery files. Published items can appear in their relevant indexes and sitemap; the current RSS feed contains published lessons only. Archived items are not routed or listed by the current build.
Images follow the final text
An image file being present, or a media field saying ready, does not prove that the image still matches revised prose. When lesson wording, panel actions, character or setting references, or the image-making rules change, we compare the image instructions and every retained or replacement image with the final text before treating the visual work as ready for release.
Corrections update every affected surface
When we confirm an error or material change, we update the authoritative source and the smallest set of affected descriptions, FAQs, structured data, links, and related passages. Material changes receive a new updated date. High-risk or changeable claims also receive a new source check and a recheck trigger. Automated screening can raise a candidate; it does not by itself declare a claim wrong. The About page provides the correction and contact route.