A feast-day date on an announcement may be treated as proof of worship. The event could be a lecture, concert or community meeting, and the calendar unspecified. Establish tradition, date convention and programme.
What needs to be clarified
Check calendar linkage and programme features relevant to religious function without classifying the event by date alone.
Materials to prepare
Complete announcement and programme with original date
Tradition-specific calendar and explanations
Recording or detailed account of actual content
What to compare
Check calendar, movable feasts and regional practices. Compare programme stages with primary tradition descriptions, distinguishing a festive lecture from ritual sequence. Compare recording and announcement, noting omissions and features allowing alternative interpretations.
Possible outcome of the analysis
A calendar comparison and content description may identify supported feast links, alternative functions and insufficient evidence for a ritual conclusion.
Limits of the conclusions
Coincidence proves no ritual or participant beliefs. One community's calendar does not automatically apply elsewhere; analysis is no legal classification.
Essential technologies keep the website working and save settings. Visitor analytics are used only with your consent.
What is stored and how to change your choice
You can allow visitor analytics using Yandex Metrica. The counter loads only after separate consent. Webvisor, click maps and outbound link tracking are disabled. Enquiry content, contact details and documents are not transmitted as analytics parameters. Declining does not prevent you from using the website or submitting enquiries.
Cookies are small browser records used by the website to save essential settings. Local storage (localStorage) saves data between visits.
FORMSESSID is a technical secure-form session lasting for the browser session. The cookie ee_analytics_choice and the entry analytics-choice-113740560 in local storage save your choice for 180 days. An expired local entry is deleted on your next visit or when its expiry is checked on an open page. These records are not used to analyse behaviour.
Analytics service cookies
When analytics are allowed, Yandex Metrica may use _ym_uid and _ym_d — 1 year; _ym_isad — 20 hours; _ym_metrika_enabled — 60 minutes. The cookie _ym_visorc_* relates to Webvisor and lasts for 30 minutes; Webvisor is disabled on this website.
You can change your choice here at any time by opening “Analytics settings” at the bottom of the page. You can delete cookies and local entries through your browser settings by choosing to delete website data for religio.moscow. Blocking essential technologies may prevent secure form submission and saving your setting.
