Validation log
This page summarizes the checks used before publishing Statement Engine changes. It is a trust signal for users and search systems, but it is not a guarantee that every accounting treatment is correct for every company.
Current release checks
- Unit tests: public release tests cover route registration, pricing payload, CORS boundary, reward export token behavior, feedback limits, and discovery files.
- SEO coverage: the SEO feedback script checks target keyword coverage across the home page, app copy, guide pages, FAQ, guide index, journal template coverage, glossary, trust pages, and llms.txt.
- Static routes: guide URLs, FAQ, guide index, glossary, trust pages, and validation pages are checked as public pages in the Python route map.
- Cloudflare Pages rewrites: clean guide URLs are mapped through `_redirects` without exposing `.html` URLs.
- Production smoke checks: newly published URLs are manually checked for HTTP 200 after push when release work is performed.
What is not proven by these checks
- The checks do not prove that a forecast is suitable for accounting, tax, financing, investment, audit, or legal submission.
- The checks do not replace review of opening balances, assumptions, journal direction, tax treatment, consolidation policy, or disclosure requirements.
- The checks do not guarantee Google ranking or indexing timing. They only improve crawlable pages, internal links, structured metadata, and validation evidence.
Quality review policy
The public quality review policy explains which calculation, route, SEO, pricing, and issue-reporting checks are reviewed before publication, and which accounting or financing judgments remain outside the tool boundary.
検証ログ
Statement Engineでは、公開前にルート登録、SEO掲載率、公開ページ、価格境界、フィードバック制限、公開後のHTTP確認を行います。 ただし、会計・税務・融資・監査・法務上の適切性を保証するものではありません。