Editorial and Citation Policy
Velmora Academy publishes a learning edition only after its source, text coverage, educational claims, vocabulary, media rights, and machine-readable metadata pass documented checks.
Ranking and citation decisions belong to search and answer engines. This policy describes the evidence Velmora controls and exposes publicly so learners, teachers, crawlers, and AI systems can verify each edition.
How are source texts verified?
Every curated release names its source edition, records a stable source URL and checksum, and proves that the published learning units reconstruct the approved text.
Public-domain status or another approved rights basis is recorded before publication. Chapter coverage maps must account for the full selected source scope, and omitted story beats must be explicitly empty for a complete release.
How is educational content reviewed?
Summaries, learning objectives, intent sections, FAQs, study steps, and defined terms must be useful, source-grounded, visible on the page, and distinct from the source text.
Vocabulary must occur in the corresponding reading and include pronunciation, part of speech, a learner definition, and contextual evidence. A release cannot rely on hidden structured data to make claims that readers cannot see.
How are images and audio handled?
Each new illustration requires an approved rights status, descriptive alternative text, provenance metadata, and a verified file identity tied to its exact reading.
Licensed and public-domain assets require their respective license or source URLs. Original media records its generation or production basis. Narration is identified as generated where applicable and remains paired with the visible English transcript.
How can a correction be requested?
Readers can report a textual, educational, attribution, or rights issue by identifying the exact canonical page and the evidence supporting the correction.
Email archivist@velmorauniverse.com. Accepted corrections update the release record and its review date; source text changes also require a new checksum and coverage verification.