1. Project at a Glance
MK Music Archive is creating a durable digital foundation for documenting, connecting, researching, and preserving Macedonian music heritage.
It belongs to the broader Macedonian Center for Contemporary Music Heritage initiative. The first concrete system being developed is MK Music Registry — a curated, evidence-based registry connecting music releases, recordings, artists, contributors, labels, credits, sources, and historical context.
The Registry is not intended merely as a discography database or website. Its purpose is to create durable, traceable knowledge: what is known, where information came from, where uncertainty remains, and how the historical account develops when new evidence appears.
2. Why It Is Needed
Macedonian music history is distributed across physical releases, private collections, catalogues, photographs, printed material, interviews, testimony, media archives, and institutional collections.
Sources can be inaccessible, incomplete, or contradictory. Collections can become unavailable, websites can disappear, and knowledge held by individuals can be lost.
MK Music Archive is being developed so this knowledge does not remain isolated in a single source, collection, or memory. The goal is not an illusion of absolute certainty, but preservation of context, evidence, uncertainty, and historical continuity.
3. Initiative → Archive → Registry
Macedonian Center for Contemporary Music Heritage is the broader long-term initiative for documenting, preserving, researching, and publicly presenting Macedonian music heritage.
MK Music Archive is the concrete cultural and digital project through which that vision can gradually become sustainable cultural-memory infrastructure.
MK Music Registry is the structured knowledge foundation connecting releases, recordings, artists, contributors, labels, credits, sources, evidence, and historical context.
The Registry is the first practical step. Broader archival, research, educational, and public possibilities remain future potential rather than claims about capabilities that already exist.
4. Core Principles
- Identity: stable Registry identities help recognize the same subject across sources and later corrections.
- Provenance: where information came from matters, as does what a source actually supports.
- Source fidelity: original names, titles, scripts, credited wording, and historical terminology are preserved.
- Uncertainty: incomplete or conflicting evidence is documented instead of converted into invented precision.
- Continuity: corrections and new discoveries extend the history of knowledge rather than silently erasing it.
5. Core Model
A Release is a particular edition or distribution package, such as vinyl, cassette, CD, digital single, or reissue.
A Recording is a particular captured performance or produced audio identity, independent of the releases on which it appears.
A Track is an appearance of a Recording on a particular Release.
The same Recording can therefore appear on multiple Releases without becoming a new Recording each time.
The Registry also distinguishes an Artist, a public artistic identity, from a Contributor, a real person or organization involved in creation, production, documentation, or preservation.
These distinctions prevent historical information from being simplified in ways that change its meaning.
6. From Research to Public Knowledge
The simplified model is:
Research and discovery → Sources and observations → Evidence and uncertainty → Structured knowledge → Review → Approved knowledge → Deliberate public presentation
The process can be iterative. New evidence can reopen an existing question.
Approval preserves an accepted version of knowledge; it does not claim perfect certainty. Approved does not automatically mean published — public presentation is a separate decision.
8. Technology Foundation
MK Music Registry is being built as a modular monolith with clear Domain, Application, Infrastructure, and presentation responsibilities. It uses PostgreSQL for durable structured persistence, a controlled migration stream, and a layered .NET/ASP.NET Core architecture with Blazor presentation.
The architecture is deliberately pragmatic: strong transactional consistency, one codebase, and a system that can remain understandable and maintainable for a small team without unnecessary distributed-system complexity.
Detailed engineering specifications remain internal.
9. Who It Is For
The project is relevant to researchers, historians, artists, music professionals, collectors, archivists, labels, museums, libraries, cultural institutions, journalists, authors, universities, the Macedonian diaspora, and music enthusiasts.
Different audiences do not receive the same access to the internal Registry. Public experiences should use only approved and appropriate public knowledge.
10. Team and Collaboration
Tosho Filipovski — Initiative Visionary & Program Coordinator
Shapes the initiative's vision and coordinates its program.
Contact: [email protected]
Vasil Buraliev — Product Designer, Project Manager, Registry & Technology Consultant
Works on product design, project management, the Registry concept, information model, and technology/system direction.
Contact: [email protected]
MK Music Archive welcomes conversations with people and organizations whose work, knowledge, or materials intersect with Macedonian music heritage. Potential collaboration may include knowledge exchange, research cooperation, contextualization of historical material, and cross-referencing relevant sources and collections.
11. What the Project Is Not
MK Music Archive and MK Music Registry:
- are not merely a music website, CMS, spreadsheet, or discography catalogue;
- are not an uncontrolled crowd-edited database;
- do not promise that every historical question can be resolved with absolute certainty;
- do not currently claim official state-registry status;
- do not present future archive, museum, educational, or institutional possibilities as capabilities that already exist.
The project's intended credibility comes from method, evidence, explicit uncertainty, and continuity of knowledge.
Document Governance
This public overview is derived from approved project specifications, approved orientation material, project-owner decisions, and current implementation evidence.
Implementation-status rule: repository reality and approved Linear completion evidence determine implementation claims; specification completeness alone does not prove implementation.
This document is informational. For implementation and governance decisions, the approved numbered specifications remain authoritative.