PROOF · Basis for a public claim

Public source extract

Project state and acceptance boundaries · 29 September 2026

Prepared on 1 October 2026 from the project document. This is a curated public extract; the English version is translated. The original document is not open for anonymous access. This extract is not an independent audit or a new production check.

Source document

CURRENT_STATE.md

Document checksum

af52289711921d8cb4f28844de6431ca3c484de76b85e1b2a310936127bf9972

The checksum identifies the exact bytes of the document read. It does not prove that its claims are correct.

1. An editorial product with member access

   Themed issues, a journal, registration and sign-in are available on the website. Its author creates the product and leads the music editing.

   Boundary: The public surface establishes public functions; member-only access and real payments require separate checks.

2. Deployed code and accepted functionality are distinct

   The project record separates deployment of the cover editor code from the still pending acceptance of public use.

   Boundary: A version number and a healthy server do not establish completion of every user workflow.

3. Data outlives application replacement

   Persistent data resides in a separate PostgreSQL database; the application is deployed separately.

   Boundary: This separation alone does not prove backup recovery or continuous availability.