Authority and accountability

Kickopedia Editorial Team and Research Method

Meet the publishing and review function behind Kickopedia and see how sources, listening analysis, practical guidance, cultural credit and corrections are handled.

Published by Dystant Sounds · last reviewed 30 July 2026

Who is responsible

Kickopedia is published by Dystant Sounds and reviewed as a connected knowledge system

The byline “Kickopedia Editorial Team” identifies the publishing and review function without inventing a named expert or personal credential. Pages are designed to give a direct answer, explain the mechanism, state context, show source boundaries and provide a route to correction.

Editorial sequence

How a guide earns publication

  1. Answer the actual question. The first section must solve or frame the user’s question before mentioning a product.
  2. Identify the kind of claim. Technical mechanism, historical fact, cultural interpretation, listening analysis and production advice are not treated as interchangeable.
  3. Prefer primary sources. Manuals, patents, designer archives, credits, first-person interviews and institutional collections take priority where available.
  4. State the boundary. Undocumented equipment, disputed origin stories and listening inference must not be written as settled session fact.
  5. Make it testable. Technical advice should name what to change, why it changes the sound and what to listen for.
  6. Connect the page. Each guide should link to its mechanism, cultural context, relevant instrument and practical next question.
  7. Keep corrections visible. Meaningful factual changes should update the page date and source note rather than silently rewriting history.

Evidence labels

Four different kinds of confidence

A

Documented

Supported by a primary source, reliable credit, manual, archive or clearly attributable account.

B

Reported

Attributed to a source but not independently confirmed; wording keeps the attribution visible.

C

Listening analysis

An audible description or comparison that does not claim access to undocumented session settings.

D

Practical hypothesis

A production suggestion framed as a test, with the relevant context and listening result named.

Research tools and human responsibility

Assistance does not replace source judgement

Search, transcription, data tools and language models may help organise research, identify gaps and test whether a question routes to a useful page. They are not treated as evidence. Published claims still require an attributable source or a clear label such as listening analysis or practical hypothesis.

Policies and public routes

Inspect the system