Editorial statement
About the Journal
A clear account of who makes the lessons, how claims are checked, and what happens when something needs correction.
Last updated:
Who makes the Journal
Alex, founder of Nisatsu, publishes and operates the Journal and owns its editorial direction. Nisatsu AI researches sources and drafts the lessons. The Journal is a sibling publication to Nisatsu, but every lesson is meant to stand on its own for readers who never use the app.
The disclosure lives here at publication level. Individual lessons do not carry an AI byline or imply that a person reviewed that particular lesson.
Editorial method
Each lesson starts with one narrow learner question. Research records named references, while the published explanation and examples are newly written rather than copied or lightly reworded from a source.
- Define the question and the learner level it serves.
- Research the claim against more than one suitable reference.
- Draft a structured lesson with natural examples and context.
- Run independent accuracy, naturalness, and source-integrity checks.
- Let those automated gates determine publication eligibility. Hold flagged work for Alex to review; publish passing work autonomously.
- Send a documented 10 percent sample of published passes to Alex for a spot check.
Alex reviews every flagged lesson and the sampled passes. Automated checks reduce risk, but they do not make a lesson infallible. The Journal does not claim that every published lesson was reviewed by a person before publication.
Corrections
Accuracy matters more than preserving an old version. A lesson may be corrected in place or withdrawn while a concern is investigated.
To report an error, email contact@nisatsu.com with the lesson URL, the passage at issue, and a source or explanation when available. Do not include private account or credential details.
Security reports
Send suspected vulnerabilities to contact@nisatsu.com. Include the affected URL, impact, and reproducible steps. Use the minimum access needed to demonstrate the issue, avoid disrupting the service or accessing another person's information, and allow time for investigation before public disclosure.
The machine-readable reporting contact is available at /.well-known/security.txt.