Siku (instrument)
traditional Andean panpipe

Siku or sicu/sicus (Quechua: antara; Aymara: siku; Spanish: zampoña or zampolla) is a traditional Andean panpipe. This instrument is the main instrument used in a musical genre known as sikuri. It is traditionally found across the Andes but is more typically associated with music from the Kollasuyo, or Aymara speaking regions around Lake Titicaca. Historically, because of the complex mountain geography among other factors, some regions in each community would develop their own type of siku, with its own special tuning, shape and size. Additionally each community developed its own style of playing. The modern siku has been standardized for compatibility with Western music, transformed from its traditional roots.
History
The siku (panpipe) is originally from the Aymaras of Peru and Bolivia, where a woman would play her siku as she came down from the mountains. Since the largest siku has every note (A-G), and was too big for the woman, they often got two sikus (usually smaller ones) that would be played together with someone else, so they could play them continuously after each other and thus the scales could fully be played. Once the women partnered, they then became musically bonded with each other, as part of their religion, and neither could play the pipes with any other for the rest of their life.
Women would also assemble into groups as they came down the mountains, each group would play different tunes, and as they got together, they would blend all the melodies together to create one complete melody.
Begin with the source’s own compact description: “Siku (instrument)” is traditional Andean panpipe. The dossier treats that line as a proposition to test through Siku, instrument and traditional, not as a finished interpretation.
Why this record matters
The phrase “traditional Andean panpipe” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Sep 14, 2026. The linked authority identifier is Q905244. The Library of Congress control number is sh91002821. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Siku (instrument)”, its source revision and the description used here.
- Expand the search: follow Siku (instrument) primary sources, Siku (instrument) archive and Siku research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Siku (instrument)”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Siku (instrument)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.