Prove scale before attention
Early work can be judged by format, reach or commercial familiarity before its creative proposition is understood.

04 / About
BCMC is a self-funded, independent underground music label, with minimal constraints on publishing.
Burnt Chapati exists to help music happen. We bring voices and musicians together, develop songs, and make space for work outside the commercial mainstream.
You can begin with a rough voice recording. We connect the people who can help it become a song. When a demo is ready to be shared, BCMC publishes it for everyone to hear.
Bring us your first idea →A little more about the music
Burnt Chapati is a creator-first alternative to production systems that ask original work to meet legacy thresholds before giving its people a serious place at the table.
Our reason
A powerful song can exist before there is scale, certainty, a familiar format or a conventional production route.
Burnt Chapati exists to meet that work with rigour rather than ask it to imitate the conditions of a legacy deal. We begin with the creator's intent, then identify the people, knowledge and resources the project genuinely needs.
The purpose is neither independence as isolation nor collaboration as vagueness. It is a working structure where distinct contributions can meet, decisions remain visible and the resulting agreement belongs to the actual project.
A different premise
Legacy structures often begin by asking whether work fits a pre-existing gate. Burnt Chapati begins by asking what would make the work complete on its own terms.
Early work can be judged by format, reach or commercial familiarity before its creative proposition is understood.
The song, present evidence and unresolved decisions define the first serious conversation.
A standing structure can make roles and deal assumptions appear inevitable even when the work needs something else.
Creators, specialists, institutions and resources enter through a defined contribution, not a generic hierarchy.
Precise participation
Fractional ownership is a contractually defined share in a specifically identified project asset or right, assigned to named parties in signed project-specific terms. The same agreement may separately define related revenue participation, accounting and decision rights. Credit, fees and composition authorship remain distinct; nothing is automatic and no income or return is guaranteed.
The public website defines the idea, not the deal. Only project documents create enforceable rights or obligations.
The project network
Bring the authorship, voice, repertoire, performance language or first musical proposition.
Transform the premise through arrangement, interpretation, instrumentation and recorded performance.
Give the work technical form through recording, editing, mixing, mastering and reliable delivery.
Keep traditional knowledge, language, method and context connected where the work calls for them.
Bring an appropriate programme, room, audience or public context into a defined collaboration.
May propose resources for a specific project, subject to separate diligence and written terms; this page is not an investment offer.
Operating principles
Burnt Chapati gives every project room to be different without making its working relationships unreadable.
Language, form and experiment are heard before a standard format or market category is imposed.
Creative, technical, research, operational and support roles remain visible to the people relying on them.
Important approvals belong to named people under the project terms rather than to an implied hierarchy.
Open questions about scope, resources, rights or release are surfaced instead of converted into premature promises.
These principles describe the working intent. The agreement for each project defines the binding relationship.
Collaboration lifecycle
The process gives a creative proposition several clear moments to become more precise—or to stop without false momentum.
A creator or partner introduces the work, contribution or context they want considered.
No commitmentThe first review identifies the creative premise, present evidence and the decision that matters next.
FitThe project names the smallest complete network of people, knowledge and resources it requires.
TeamScope, roles, approvals, credits, permissions and any participation are set in project-specific terms.
ContractThe network produces and reviews the work against the agreed creative premise.
ProductionThe approved recording, performance or output reaches its intended public or restricted context.
If confirmedProject framework
A project does not need identical terms; it needs enough definition for every participant to understand the exchange.
| Area | Question | Project record |
|---|---|---|
| Intent | What are we making, and what must remain true? | Creative brief |
| Contributions | Who is bringing which work, knowledge or resource? | Role and deliverable map |
| Credits | How will accepted contributions be publicly named? | Approved credit record |
| Participation | Is a fee, ownership interest or continuing economic share agreed? | Written project terms |
| Authority | Who decides at each material review point? | Decision map |
| Release | Which public or restricted route is approved? | Release or presentation plan |
The framework makes questions visible; it does not supply a universal contract or ownership split.
Rights + credits
Credit, fee, ownership, permission and approval can sit beside one another without meaning the same thing. Burnt Chapati's model asks the project to state each instrument directly so no participant has to infer it from a title or conversation.
Participants should seek independent professional advice where the project's rights or economics require it.
Decision gates
The work has a clear premise that Burnt Chapati and the proposed creators can understand without flattening it.
The necessary contributions and decision owners are visible, even when some people remain to be confirmed.
Outputs, dependencies, resources and open questions can be expressed honestly enough to plan.
The parties have accepted the terms they need before production relies on them.
The work, credits, permissions and release context are approved for the intended audience.
A positive conversation is not a release commitment; each gate is a separate project decision.
The wider practice
They can strengthen one another without turning participation in one area into automatic access to another.
A creator-first path from musical premise to an approved recording and public catalogue entry.
Developing formats that place performance, playback, research or conversation inside a deliberate audience experience.
Artist-led sets, ensembles and bills considered through a grounded booking and production brief.
A Centre in development for practitioner-led archives, fieldwork, residencies and commissions.
Model questions
No. The project may agree a fee, credit, ownership interest, another economic participation or a combination. Nothing is automatic.
No. An introduction or project discussion creates context for review; the relevant written agreement creates the relationship.
No. The website offers no security or return. Any project support requires separate assessment and appropriate terms.
No. It means the network and operating structure answer the creative premise instead of displacing it.
No. Creative approval, scope, resources, permissions and final readiness still determine whether work becomes public.
Continue
Listen, introduce yourself, study the developing research framework or bring a project-specific proposal.
Keep exploring
Open a topic to read more.
Burnt Chapati is developing the Centre for Advanced Research and Development of Traditional Music and Arts because tradition should be studied with the people who carry it—not separated from lineage, place or consent.
Why the Centre
A practice is more than the sound, image or object that can be captured from it.
Traditional music and arts live through people: through memory, repetition, teaching, place, language, ceremony, experiment and change. Burnt Chapati is developing the Centre to explore how research can remain connected to those relationships while creating useful records and new creative possibilities.
The Centre is not presented as an operating archive, institute or announced programme. Its purpose is being shaped around a simple responsibility: inquiry should deepen understanding without turning practitioners or inherited knowledge into anonymous source material.
Living research
Research here means a structured inquiry developed with relevant practitioners and context. Documentation may support learning or creative work, but recording something does not by itself create permission to publish, adapt or commercialise it.
The Centre's programme, methods and governance remain in development.
Relational archives
Any future archive work would begin by asking why a record should exist and who should shape its life.
Record performance, conversation or process only where the purpose and participants are clear.
Keep names, language, place, lineage, date and method connected to each accepted record.
Identify who can speak for a contribution and how practitioners wish to be represented.
Treat public, restricted, delayed and closed access as meaningful project decisions.
Fieldwork
Fieldwork is a capability in development, not a currently announced expedition or programme.
Clarify the question, why lived context matters and who should help shape the inquiry.
Before contactDiscuss recording, attribution, access, review, withdrawal and possible outputs in understandable terms.
Purpose-specificGather only what serves the agreed inquiry and keep contextual notes with the material.
During workCreate agreed opportunities to question descriptions, translations, edits or interpretation before release.
Before releaseApply the agreed attribution, access and use conditions to every retained output.
Continuing dutyResidency ideas
Residency formats are open to proposals; no standing programme, place, duration or funding offer is announced.
A practitioner explores repertoire, method, instrument or transmission within an agreed support frame.
Open to proposalsPractitioners or disciplines work reciprocally, with authorship and adaptation discussed before making.
Open to proposalsA host brings a research purpose, relevant relationships and realistic operational responsibility.
Open to proposalsA demonstration, recording or publication would need its own scope, permissions and approval.
In developmentResearch commissions
Burnt Chapati is open to proposals, but no standing fund, schedule or guaranteed production route is claimed.
Explain the inquiry, relevant practitioners, intended audience and reason the work should exist.
Open inquiryIdentify whose knowledge, permission and participation the proposed method would require.
No presumptionSet authorship, compensation, resources, outputs, review points and access conditions in writing.
If agreedCarry out the inquiry while preserving provenance and responding to material changes.
Documented processPublish, perform, restrict or retain results according to the agreed purpose and permissions.
Output decisionResearch record
A file becomes more responsible—and more useful—when its origin, method and permissions remain visible.
| Layer | Question | Record |
|---|---|---|
| Identity | Who contributed, and how should they be named? | Contributor and credit record |
| Provenance | Where, when and through which relationship was it made? | Context and source note |
| Method | How was it recorded, selected or interpreted? | Method statement |
| Consent | Which collection, access and uses were agreed? | Permission record |
| Version | Which edit, translation or description is current? | Version history |
| Access | Who may hear, cite, adapt or publish it? | Access condition |
This is a developing framework, not a claim that an archive system is operational.
Consent in practice
Consent is a continuing relationship between a stated purpose, the people involved and the uses that follow.
Explain who is asking, what may be recorded, who may encounter it and which outputs are possible.
Do not collapse study, documentation, performance, adaptation and publication into one permission.
Discuss how practitioners, translators, researchers and communities should be represented in the record.
Where agreed, return descriptions, edits or translations when meaning or circumstances may have changed.
Respect material that should remain restricted, delayed, unadapted or outside the project altogether.
Each project needs a protocol suited to its people and context; these principles are not a complete ethics policy.
Against extraction
A visible or audible practice can still carry individual, collective, inherited or restricted relationships.
Online, public or recordable material is not automatically available for adaptation or commercial use.
Ask who can speak for a contribution and which other permissions or relationships are relevant.
Keep names, language, place, purpose and transmission history connected wherever permission allows.
Permission to study or document does not by itself authorise sampling, adaptation or release.
Rights, restrictions, credits and any participation must be assessed for the particular project and recorded in separate terms.
Possible outcomes
These are possible forms, not announced projects. Every outcome depends on authorship, review, permission and resources.
Audio, image, text or metadata retained under conditions agreed for the project.
A recording or performance developed only where source relationships support that creative use.
An essay, learning resource, workshop or demonstration prepared for a defined audience.
Material retained privately, under embargo or for a named community instead of open publication.
Proposal path
The Centre is open to proposals while its programme remains in development; an enquiry begins review, not a commitment.
Explain the question, why it matters and why the proposed method is appropriate.
PurposeIdentify practitioners, communities, archives or institutions already involved or still to be approached.
No presumed consentState the intended audience, access level and what should remain conditional on review.
ProvisionalSet out time, expertise, access, travel, production and funding available or requested.
No standing fundBurnt Chapati may ask questions, suggest another frame, decline or explore separate project terms.
Review onlyQuestions and next step
A strong first note makes the inquiry, relationships and unknowns visible without overstating permission or readiness.
No active archive or standing residency programme is claimed. The Centre and its capabilities are in development, while relevant proposals may be considered.
Only describe or share material you are authorised to provide. Possession, public performance or online availability does not establish permission for a new research use.
No. There is no standing fund or automatic output stated here. Resources, responsibilities and any publication would need separate assessment and agreement.
Potentially, when the method, source relationships, authorship, permissions and production scope support that outcome. Research access alone does not authorise creative reuse.
Email hello@burntchapati.com with the question, relevant people and relationships, proposed method, possible audience, current permissions, resources and the next decision you need.
Burnt Chapati is developing authored show formats because some music asks for more than a stage slot: it asks for a room, sequence and audience experience shaped around how the work should be heard.
Why a Show
The format begins with what the artist wants an audience to notice, feel or understand.
Within this developing framework, a Show is a deliberately framed live encounter. Performance, playback, conversation or demonstration may work together, but only when each element serves the music and the agreed audience experience.
A format becomes real only through an agreed artist, host, room, scope and date.
Choosing the format
The distinction helps artists and hosts begin with the right production question, not a hierarchy of scale.
Build an intimate or specialist encounter around attention, process, dialogue or demonstration.
Build an artist-led set, ensemble or bill for a broader public booking context.
Room layout, playback, silence, facilitation and context may shape the central experience.
Set length, stage, sound, lighting, access, travel and presenter operations lead planning.
Burnt Sessions
Burnt Sessions is a developing format, not an announced recurring series or schedule.
A song can hold decisions that disappear in a conventional set: a changed lyric, an arrangement built through rehearsal, a production intervention or the sound of one musician listening to another. A proposed Burnt Session would bring selected parts of that making into the same frame as the performance.
The artist and relevant contributors would decide what belongs in the room. Context should sharpen attention, not explain the music away, and any recording or later publication would require its own permissions and terms.
Listening rooms
Listening rooms are in development and would be designed project by project, not sold as a fixed technical package.
Identify the approved master, work-in-progress, stems or references and who may present them.
Permission firstDecide whether the room supports a first hearing, close comparison, conversation or research context.
One clear frameAssess noise, playback, seating, sightlines, access, power and audience movement with the host.
Place-specificArrange playback, silence, speech and any live element around the intended arc of attention.
Authored experienceConfirm what, if anything, may be recorded, shared or developed after the room ends.
Separate useLiving archives
Living Archives is a proposed format connected to an R&D initiative that is itself in development.
Where possible, relevant practitioners, researchers or interpreters should shape how material is presented.
Language, place, lineage, function and change should precede easy contemporary analogy.
Demonstration, recording, adaptation and publication are different activities with different consequences.
Keep practitioners, translators, researchers, performers and production contributors visible in the event record.
No Living Archives event is confirmed here. A proposal would require appropriate relationships, consent, scope and resources.
Collaborative showcases
Artists, venues, institutions and curators may propose a coherent idea; no standing showcase series is announced.
Connect released or approved work through contributors, process or one clear listening proposition.
Open to proposalsTrace how an artist, producer, musician or engineer shapes more than one work.
Open to proposalsConnect a research question to contemporary practice, subject to the developing R&D framework.
In developmentBring a room and curatorial question without presuming a programme commitment.
Open to proposalsAudience and room
There is no universal specification; a feasible Show would resolve these conditions with its host.
| System | Question | Why it matters |
|---|---|---|
| Audience | How will people gather and move? | Shapes intimacy, access and attention |
| Acoustics | What noise and room character are present? | Affects music, playback and speech |
| Playback | Which system, inputs and operator are available? | Determines responsible presentation |
| Performance | What space, instruments and changeovers are needed? | Connects sequence to safe delivery |
| Access | Which physical and communication barriers remain? | Supports informed invitation and planning |
| Documentation | What capture is requested and why? | Separates attendance from recording permission |
Technical, safety and accessibility responsibilities belong in project-specific production documents.
Curatorial principles
Curation should create a clear encounter without turning artists or audiences into supporting material for a concept.
Performance, playback and conversation should answer a shared question rather than accumulate features.
Artists and relevant contributors decide which process, context or unfinished material may enter the room.
Name creative, technical, research, facilitation and host roles in an agreed event record.
Duration, pauses and transitions should protect the audience experience instead of filling arbitrary time.
These developing principles guide proposal review; they do not accept a proposal or establish a fixed format.
Production exchange
Technical exchange can begin with a proposal, but a Show exists only after the creative and operating conditions align.
Share the room, audience, access, equipment, staffing, schedule and operating constraints.
Proposal inputIdentify a feasible sequence, proposed contributors and the questions still preventing confirmation.
ExploratoryAllocate production, safety, hospitality, access, transport, ticketing and documentation duties.
Project-specificRecord systems, operators, timings, approvals, terms and contingencies before public announcement.
If proceedingPresent the Show, then reconcile credits, recordings and follow-up uses against the agreement.
No automatic publicationDocumentation
Admission to a live event does not by itself authorise photography, multitrack recording, streaming or later publication.
Specify stills, video, audio, stream or audience material rather than requesting blanket recording rights.
Consider performance, composition, voice, image, research and traditional knowledge in the proposed record.
Separate archive, editorial, promotional, broadcast and commercial uses, including channels and duration.
Record attribution and any project-specific approval step before documentation becomes public.
Permissions, ownership, fees and any participation connected to documentation require separate terms for the specific Show.
Host proposal
The strongest proposal makes the desired audience experience and the host's actual capabilities equally clear.
| Area | Include | Current position |
|---|---|---|
| Purpose | Why this work and audience belong together | Open to proposals |
| Venue | Location, layout, access and constraints | No preferred venue claimed |
| Format | Proposed Show type or an explained alternative | Subject to development |
| People | Confirmed, proposed and uncontacted contributors | Do not imply consent |
| Production | Systems, staff, schedule, budget and capture request | Requires review |
| Public status | Timing and announcement dependencies | No date confirmed by enquiry |
A proposal does not create a booking, reserve a date or approve publicity.
Questions and next step
A concise first note should explain why this work, room and audience belong together.
No standing programme or confirmed date is claimed. These formats are in development and may be explored through suitable proposals.
A Show foregrounds close attention, context or demonstration; a concert foregrounds public performance. The actual brief determines the appropriate format.
Not automatically. Capture, rights, credits, review, fees and later use would require separate project-specific permission.
No standing facility or inventory is claimed. Available and required resources would be identified with the proposed host during review.
Email hello@burntchapati.com with the artistic purpose, proposed participants, venue and audience, preferred timing, available resources, documentation request and next decision needed.
Burnt Chapati approaches concerts as artist-led encounters: the song, performers and audience gathered under conditions that protect the work. Proposals are open; no confirmed public concert dates are currently listed.
Public performance
A Burnt Chapati concert begins with repertoire, performers and the kind of attention the music asks from a room.
A concert is a proposed public performance by a defined artist or ensemble in a described presenting context. It becomes confirmed only when artistic fit, availability, delivery responsibilities and applicable terms have been agreed through the appropriate written process.
Artistic purpose
Capacity, stage size and publicity are production choices. The first question is what the performance is trying to make possible.
Burnt Chapati welcomes proposals that can articulate why a particular artist, repertoire and audience belong together. The room may be intimate or large; its value lies in supporting the musical encounter rather than signalling importance by size alone.
Independent music. Shared participation. Live, that means creators remain visible in the way the event is framed, credited and delivered, while every fee, right, permission and continuing interest remains project-specific and separately documented.
Presenting contexts
The setting changes the brief. It never removes the need to explain the artistic reason, accountable presenter and conditions of delivery.
Place the proposed performance within the programme's artistic frame, timetable, stage conditions and audience journey.
Describe capacity, access, curfew, installed systems, local team and the listening conditions the venue can support.
Explain the cultural programme, communities involved, learning context and any documentation expected beyond the performance.
Show the audience case, intended room, local delivery capacity and why the proposed artist belongs in that context.
Public concert status
No confirmed public concert date is listed today. A truthful empty state protects audiences and artists from acting on a possibility as if it were a commitment.
The website currently publishes no confirmed Burnt Chapati concert date.
CurrentFestivals, venues, institutions and promoters may submit a specific presenting proposition for review.
Open to proposalsEvery proposal requires a fresh check of people, repertoire, routing, preparation and technical feasibility.
CurrentA concert should enter the Calendar only after its essential public information has been verified.
In developmentConfirmation path
Separating enquiry, assessment, scope and confirmation lets all parties know when a conversation has—and has not—become a commitment.
Name the artist or format, the audience, the presenter, the room and why this performance belongs there.
ProposalReview availability, repertoire, ensemble, travel, lead time, venue systems and the care the performance requires.
Fit reviewAssign accountable owners for technical delivery, hospitality, travel, access, marketing, ticketing, permissions and documentation.
ScopeResolve commercial, operational and rights terms in the documents appropriate to this specific concert.
Separate agreementPublish only approved information and maintain one accurate event record if material facts later change.
Public recordProposal anatomy
A proposal does not need to answer every production question. It does need to distinguish known facts, working assumptions and decisions still required.
| Proposal element | Minimum useful signal | Decision it enables |
|---|---|---|
| Presenter | Accountable organisation or individual and a working contact | Establish who owns the proposal and local delivery |
| Artistic case | Proposed artist or format, programme context and reason for the invitation | Assess whether the performance belongs in the room |
| Date window | Proposed date or range, local time zone and decision deadline | Review availability, routing and preparation |
| Place | City, country, venue, room and capacity where known | Understand travel, access and production scale |
| Technical conditions | Known PA, monitoring, stage, power, crew and changeover constraints | Identify feasibility questions before a rider is developed |
| Audience route | Ticketed, invited, free, institutional, streamed or another access model | Clarify public communication and operating responsibilities |
| Capture and reuse | Any proposed photography, recording, broadcast, stream or archive purpose | Surface permissions that presentation alone does not grant |
This brief opens an assessment. It is not a booking, technical rider, fee quote, rights licence or authority to announce.
Concert or Show
Burnt Chapati uses two live routes so that a repertoire-led performance is not confused with a deliberately authored room format.
An artist set, ensemble or bill begins with performance, musical configuration and a presenting context.
A session, listening room, demonstration or collaborative showcase begins with a designed audience experience.
When performance meets conversation, capture, research or demonstration, each element and permission should be made explicit.
Delivery discipline
Good production is a form of care: critical information has an owner, a current version and a route for resolving change.
Audio, stage, venue operations, artist liaison and show calling need named people authorised to make relevant decisions.
Schedules, input lists, stage plans and contact sheets should identify their approved version and distribution.
Permission to present a concert does not automatically permit recording, broadcast, photography or later reuse.
A changed room, date, running order or technical condition should reach affected teams while a responsible decision is still possible.
Safety, technical, commercial, legal and rights requirements are specific to the event and exist only in the applicable agreed documents.
Live interfaces
Many parties can make a concert possible. Visibility means describing the contribution; it does not automatically create ownership, income or approval rights.
Defines the proposed configuration, creative requirements and people authorised to make artist-side decisions.
Owns the local venue relationship, access model, public information and presenter obligations agreed for the event.
Connects performance requirements to audio, stage, schedule, crew, rehearsal and changeover realities.
Plans arrival, accommodation, meals, access and on-site support around the actual touring party.
Uses approved names, credits, images, billing, links and event status across public channels.
Defines what may be recorded, who can use it, for which purpose and under which separate permission.
Planning boundaries
A public framework can improve a proposal without pretending that different artists and rooms require the same deal.
Lead time depends on the people involved, repertoire, ensemble size, travel, location, permissions, venue systems and new production work. A nearby date is not automatically impossible; a distant one is not automatically available.
Fees, expenses, taxes, ticketing, cancellation, credits, capture and reuse also belong to the specific proposal. Nothing on this page assigns a share, guarantees a return or substitutes for the written terms of a concert that advances.
Sending a proposal does not place a hold, reserve an artist, confirm availability, create exclusivity or authorise an announcement.
Concert answers
No. There are currently no confirmed public concert dates listed. A future verified date would be published through the Calendar.
A festival, venue, cultural institution, promoter or other accountable presenter may send a specific artistic and production proposition for review.
No. It begins a review only; it creates no hold, booking, exclusivity, announcement authority or artist commitment.
The performance configuration has not been standardised on this page. Technical requirements are developed for the artists, repertoire and room involved in a proposal that advances.
Not by default. Capture, broadcast, photography, streaming and reuse must be raised explicitly and agreed through the applicable separate permission.
Concert proposal
A strong enquiry connects an artistic proposition to a real presenter, place, audience and delivery path.
Share the presenter, programme context, city and venue, date window and time zone, intended audience, known production conditions, capture expectations and decision deadline. Keep the date private until every party authorised to confirm it has done so.
This calendar is for confirmed Burnt Chapati releases, live work and public programmes—not possibilities in discussion. No public events are currently listed.
Current public position
The live status below is the website's present statement about public Burnt Chapati dates. It does not reveal tentative holds or private planning.
No confirmed public dates are currently listed. The Songs page remains available for recorded work, and specific event proposals may still be submitted for review.
Operating state
Burnt Chapati would rather publish no date than ask an audience, artist or partner to organise around an unverified one.
No release event, Show, Concert, residency or research date is currently published on this website.
CurrentThe Songs page is the listening destination for demos explicitly published by BCMC.
CurrentAn accountable presenter may send a real place, purpose and date window for review.
Open to proposalsThe site presently offers no iCal feed, email alert list or automated calendar subscription.
In developmentPublic vocabulary
The status language below describes the publication standard being developed. It does not imply that any event currently exists.
A public calendar record is verified event information approved for publication by the parties responsible for it. A proposal, working date, enquiry or tentative hold remains outside the public calendar.
None of these states converts a private proposal or provisional hold into a public event.
Public activity types
These categories define a possible information architecture, not a promise that each programme exists or that dates will be published for it.
A verified public release date connected to an official listening destination where one is available.
A confirmed session, listening room, demonstration or showcase with sufficient information for public attendance.
A confirmed artist or ensemble appearance naming its presenter, place, time and access route.
A confirmed talk, workshop, fieldwork output or other research-facing activity cleared for public participation.
A residency only where its timing and public relevance are authorised for disclosure.
A published application or proposal deadline with accountable ownership, eligibility context and a destination.
Verification path
The proposed control path keeps announcement pressure from outrunning the people, permissions and operational facts behind an event.
Identify the accountable presenter or project owner, activity type, location, date window and source material.
ReceiveCheck local date and time, time zone, venue, artist or programme, access model and authoritative contacts.
VerifyConfirm that the relevant parties approve the exact public wording, links and supplied assets.
ApproveCreate one stable record with an explicit status and a visible last-updated date.
PublishMaintain the record when a material fact changes and distinguish postponement, cancellation and archive states.
MaintainInformation standard
The following fields describe the event record under development. Private operational contacts and speculative details remain outside the public view.
| Public field | What it must communicate | Publication boundary |
|---|---|---|
| Name | The approved event, release or programme title | Use confirmed naming and billing |
| Start | Local date, local time and time zone | Do not infer a time zone from location alone |
| End or duration | A known finish, duration or multi-day range | Omit an unknown value instead of inventing one |
| Activity type | Release, Show, Concert, research, residency or deadline | Choose the category that matches the public action |
| Place | Public venue and locality, or an identified online context | Publish only location information cleared for use |
| Access | The ticket, registration, invitation, free-entry or other public route | Point to the accountable access source when one exists |
| Status | Whether the record is confirmed, changed, postponed, cancelled or retained as history | Update the state whenever a material fact moves |
| Last updated | When the public record was most recently checked | Do not expose private verification contacts |
A responsible internal owner may be required to maintain the record without becoming a public contact.
Calendar principles
People may spend time, money and trust after reading a date. The information standard should respect that consequence.
A listing should be supported by an artist, presenter, venue or project contact authorised to confirm it.
An international audience should never have to guess which clock governs the event.
Material changes should update the existing event rather than leave competing versions in circulation.
Travel, security, personal contacts and internal schedules do not become public merely because an event does.
Past, postponed and cancelled records can remain legible when they help audiences understand what happened.
The responsible presenter, venue, registration or ticketing service retains authority over its own access terms, refunds and day-of operational notices.
Catalogue and calendar
Burnt Chapati uses different evidence for music that is already public and a future commitment that asks people to attend or act.
BCMC publishes original demo audio with its title and original publication date. Private project audio stays outside the public catalogue.
A future event requires verified context, explicit status and authority to publish; it is never generated from a song publication date.
A presenter, venue, registration or ticketing page may remain authoritative for admission terms and day-of changes.
Correction standard
Removing a record without explanation can strand the audience with an older link and no authoritative account of what changed.
If a confirmed event changes, the existing public record should state the new condition plainly. A postponement carries no implied replacement date; a cancellation carries no implied alternative performance; an archive should not continue to look bookable.
Where another party controls tickets, registration or venue operations, Burnt Chapati should direct audiences to that accountable source rather than inventing or paraphrasing refund, access or local safety instructions.
Available channels
Additional alert formats should not be described as available until they exist and can carry corrections reliably.
This Calendar section is the current on-site location for any verified public Burnt Chapati date.
CurrentThere is no public calendar-alert mailing list on the website today.
In developmentBurnt Chapati does not currently publish a machine-readable calendar feed.
In developmentA specific proposal may be routed through Shows, Concerts, R&D or Contact according to its purpose.
Open to proposalsCalendar answers
No. The website currently lists no confirmed release event, Show, Concert, residency or public research date.
No. A proposal, conversation or hold remains private and unconfirmed until the responsible parties approve a public record.
No. Publishing a demo on Songs does not create an event. Calendar information requires separate human verification of a public commitment.
Not currently. The website offers neither an email calendar-alert list nor an iCal subscription.
Check this page and the responsible presenter, venue, registration or ticketing source. That external source may control admission, refund and day-of instructions.
Event proposal
A useful proposal identifies who is accountable and separates confirmed inputs from open production questions.
Share the event purpose, responsible presenter, proposed date window and time zone, location, format, audience route, known production context and decision deadline. Submission creates no booking, public date or authority to announce.
Burnt Chapati needs art, judgment and infrastructure to reinforce one another. This page describes the capabilities that matter to that work. It is not a vacancy notice: no roles are currently open.
Current hiring position
The rest of this page is a capability manifesto and an invitation to introduce relevant work—not evidence of an active recruitment process.
Burnt Chapati currently has no role description accepting formal employment applications.
CurrentA concise professional introduction may be sent for future context without implying a role or recruitment process.
Open to proposalsThe website provides no applicant account, dashboard or application-status tracker.
CurrentNo review, reply, interview or hiring timeline is currently committed.
CurrentA capability map
Burnt Chapati can state what excellent practice looks like while remaining precise about the absence of current openings.
Careers describes the capabilities that can support Burnt Chapati's music, production, rights, research and live work. A formal opening exists only when the label publishes a defined role, scope, selection process and active application route.
Nothing elsewhere on this page changes the current count of zero published vacancies.
Working conviction
Independent music. Shared participation. The phrase asks for people who can protect creative intent while making contribution and responsibility legible.
Burnt Chapati is creator-first, but never craft-alone. Composition, performance, production, engineering, rights, operations, research and live delivery may meet where the work requires them. The quality of their interfaces shapes the quality and durability of the work.
Shared participation is not an automatic share. It is a discipline of identifying contribution before any project-specific fee, credit, right, approval or continuing interest is separately discussed and documented.
Work around the work
These domains describe capabilities Burnt Chapati may need as projects develop. They are not advertised job titles and do not imply that every system is currently staffed or operating.
Composition, arrangement, performance context, artist development and the judgment to strengthen work without normalising it.
Producing, recording, editing, mixing, mastering, session design and the technical records that let collaborators work clearly.
Contributor records, clearances, ownership context, permissions and decision trails grounded in applicable agreements.
Project coordination, catalogue operations, schedules, budgets, version control and responsible hand-offs across teams.
Archives, fieldwork, oral history, traditional arts context, ethical inquiry and public outputs made with accountable practitioners.
Curation, booking context, artist liaison, technical production, access, audience care and boundaries around documentation.
Evidence of practice
A useful introduction makes contribution visible without claiming the work of a team as the achievement of one person.
Explain a consequential choice, the constraints around it and how it served the artist, audience or source.
Share authorised evidence and identify exactly which part of the outcome you made, shaped or maintained.
Show how you organise quality, information, risk or hand-offs so the work can survive more than one intense moment.
Name the other contributors, what you owned, what you did not own and how decisions moved between people.
Demonstrate attention to credit, consent, accessibility, cultural context or practitioner welfare where the work required it.
Describe what you revised after feedback, failure or new knowledge rather than presenting every decision as inevitable.
Different intentions
Use the route that describes what you want Burnt Chapati to understand now; each route creates a different kind of review and no automatic engagement.
Use this page to introduce a durable area of practice for possible future context when no vacancy is open.
Use your creator profile to describe your roles and skills. A creator account does not grant membership, employment or access to other projects.
Use Partner when you bring a defined creative, technical, institutional, promotional or capital resource to a specific proposition.
Professional signal
Because no formal application is open, an introduction should provide context without collecting unnecessary personal data or confidential work.
| Signal | What helps | What does not belong |
|---|---|---|
| Identity | Name, location or time zone and a monitored reply address | Government identity records or sensitive personal documents |
| Practice | One or two capability domains that best explain your current work | A catalogue of every title you could plausibly claim |
| Evidence | A small set of relevant links you are authorised to share | Confidential files, unreleased masters or inaccessible drives |
| Contribution | Your exact role, decisions and outputs within the linked work | Sole-credit language for a collective outcome |
| Relevance | Why Burnt Chapati is a meaningful context for this introduction now | A generic mass application sent without a proposition |
| Constraints | Material location, timing or engagement boundaries | Promises of unlimited availability or unsupported certainty |
Do not send passwords, access tokens, bank details, health data, confidential third-party material or irreplaceable source files in an initial email.
Introduction lifecycle
With no active opening, there is no recruitment queue, guaranteed review window or implied next stage.
Use the careers subject and include only the evidence needed to understand your practice and relevance.
IntroductionThe note may be considered against future creative, studio, rights, research, operations or live needs.
No timetableReceipt does not establish candidate status, an interview, a role, a response obligation or a hiring process.
BoundaryBurnt Chapati may request current availability and additional evidence if a relevant conversation later emerges.
Possible contactAn eventual engagement requires its own role, scope, authority, outputs, compensation and other applicable terms.
Project-specificHiring standard
These principles state an intended standard for a future formal process; no such process is currently active.
Separate essential responsibilities from preferences and show how the role interacts with creators and other systems.
Interviews or exercises should test capabilities the work actually needs, not unrelated stamina, social access or performance theatre.
Prior roles and institutions can add context but cannot replace demonstrated judgment, craft and contribution.
Applicants should know which stage they are in, what it evaluates and what decision can follow.
An assessment should not obtain publishable creative or operational work without an appropriate agreement.
This is a future-facing evaluation standard, not an offer of employment, active selection process or promise that a role will be created.
Introduction boundaries
Speculative introductions currently travel by email rather than through a dedicated applicant system.
Keep the first note to professional identity, reply details, relevant context and authorised evidence.
Do not disclose client, collaborator, employer or knowledge-holder material you are not permitted to share.
Passwords, tokens, banking details, private keys and account recovery information never belong in a careers email.
Check the audience, expiry and download permissions of every portfolio link before sending it.
Burnt Chapati currently provides no careers account, formal applicant record, self-service status view or automated deletion control.
Careers answers
No. There are zero published vacancies and no active formal employment application route on this website.
Yes. A concise, relevant introduction may be useful for future context, but it does not create candidate status or imply a reply, interview, timeline or role.
Use You for your creator profile and private music projects. Use Careers for a professional capability introduction and Partner for a defined collaboration proposition.
Prefer a small number of authorised links and name your precise contribution. Do not send confidential files, unreleased masters, identity documents, passwords or financial information.
No sample-work request is published here. Any future assessment should test relevant capability and must not be used to obtain publishable work without an appropriate agreement.
Future context
No role is open. A precise introduction can still help Burnt Chapati understand a capability that may matter to future work.
Name your discipline, share a small amount of authorised evidence, state your exact contribution and explain why this label is relevant to your practice. Treat the note as context only—not an application, confidential submission or expectation of engagement.
Burnt Chapati brings people, capabilities, rooms and resources around defined music projects so creators can move the work forward without disappearing inside a generic partnership model.
Why partnership
A useful partnership gives a project something it genuinely needs without making the creator secondary to the arrangement.
Independent music rarely moves through one person alone. A song may need composition, performance, arrangement, production, engineering, research, a room, an audience or carefully scoped resources. Burnt Chapati exists to bring those contributions together around the work rather than around a fixed institutional threshold.
The first question is therefore not how large a partnership can become. It is what the project is trying to make, who is already responsible for it and which contribution would meaningfully change its next stage.
If a proposal advances, roles, permissions, credits, resources and any ownership or revenue participation are established only through project-specific written terms.
Working vocabulary
The words used for a relationship should describe what a party actually contributes and receives.
A Burnt Chapati partnership is a collaboration evaluated for one defined project. Creative, technical, institutional, live and resource contributions may sit beside one another, but none creates automatic rights or a commitment to proceed.
The same agreement may separately define related revenue participation, accounting and decision rights. Credit, fees and composition authorship remain distinct; nothing is automatic and no income or return is guaranteed. Nothing on this page offers a token, security or public investment product.
Ways into the work
Choose the closest starting point and describe connected disciplines in the proposal itself.
Bring original songs, lyrics, repertoire, voice, interpretation or a clear artistic proposition.
↗MakeDevelop arrangement, performance, instrumentation, sessions and the production language of the work.
↗ResolveOffer recording, editing, mixing, mastering, systems, space or technical quality control.
↗InvestigateBring field knowledge, language, archives, method, consent practice or contextual interpretation.
↗HostPropose access, a programme context, venue, audience, operational capability or public encounter.
↗ResourceExplore support for a defined purpose after the work, people, use and accountability are understood.
↗Forms of collaboration
These are proposal frames, not standard packages or pre-agreed commercial terms.
A creator brings source material and seeks the right team, production frame or release path.
A person, team or facility answers a specific creative, technical or operational requirement.
A practitioner or institution brings context, relationships, access and an accountable programme purpose.
A promoter, venue or curator proposes a room, audience and feasible production context.
A funding party identifies a specific project use, subject to diligence and written terms.
First proposal
A strong first note makes the work, present reality and next decision easy to understand.
Describe the recording, programme, live engagement, research output or other result you want to create.
PurposeShare a concise brief and only the links needed to understand the present work.
EvidenceIdentify current contributors, decision-makers and third parties whose permission may matter.
ParticipantsState the capability, resource, introduction or decision you want Burnt Chapati to consider.
ContributionInclude material timing, location, access, budget or technical constraints without overstating certainty.
RealityFeasibility
An unresolved question is workable when it is visible; an invisible dependency is not.
| Area | Question | Useful input |
|---|---|---|
| Creative fit | Is the intended work clear? | Brief, demo or programme idea |
| People | Who contributes and decides? | Roles and named contacts |
| Rights | Which material or access needs permission? | Known rights and open clearances |
| Delivery | What must be made and when? | Outputs, milestones and dependencies |
| Resources | What is available or still needed? | People, facilities and indicative budget |
| Audience | Who is the work for? | Release, venue or access assumptions |
Review is exploratory; it does not reserve capacity or create an obligation to proceed.
Project circle
The right team is not the largest one; it is the one that gives every necessary responsibility a visible owner.
Own the source material, interpretation, artistic direction and agreed creative decisions.
Own sessions, schedule, files, vendors, technical quality and final assets.
Own known rights questions, releases, clearances, attribution and project records.
Where relevant, own method, knowledge-holder relationships, provenance and access boundaries.
Own venue coordination, production advance, safety, access and audience information.
Own approved resources, decision records and reporting defined for the project.
Written terms
Clear terms let creative trust grow without asking memory or assumption to carry the project.
Define the contribution, output, timing and review process before other work relies on it.
Identify the asset, permitted uses, outstanding permissions, decision rights and approved changes.
If agreed for a specific project asset, state each contractual share, party and applicable control; composition authorship remains a separate question.
State which receipts, costs, accounting method and distributions apply; ownership alone does not promise revenue.
Keep attribution, approvals and material revisions connected to the current project record.
Any fractional ownership or revenue participation exists only under signed project terms. It is not a token, security, public offering or guaranteed return.
Project resources
Burnt Chapati may consider support conversations when a creative, research or live project has a reviewable scope and accountable use.
A first proposal should identify the work, responsible people, form and amount of support being explored, intended use, dependencies and the evidence the project can reasonably maintain. Resources might address production, access, research, presentation or another stated need.
Any further discussion remains subject to project-specific review, diligence, permissions and written terms. Support does not automatically create ownership; where a contract separately allocates fractional ownership of a named project asset, it must also identify the parties, shares and related rights.
This page does not offer securities or tokens, solicit public investment, or promise repayment, profit, income or return. A party considering a material commitment should obtain independent advice appropriate to its circumstances.
Do not send banking details, identity documents or highly sensitive records in an initial email.
Accountability
Updates should follow the real decisions and evidence of the project, not an abstract partnership label.
Record scope, approved resources, responsible people, milestones and known dependencies.
BaselineReport changes affecting delivery, permission, cost, timing or intended public use.
ExceptionUse the agreed acceptance process for creative, technical, research or live outputs.
DecisionRetain approved outputs, credits, permissions, decisions and any agreed final reporting.
CloseBoundaries
These distinctions keep the creator, proposed partner and work clear of premature assumptions.
No. Submission invites review only. A partnership begins only when the relevant parties agree its scope and sign appropriate project terms.
No. Contributions do not trigger a universal allocation. Any ownership must identify the project asset, parties, contractual shares and associated rights in writing.
Only a specifically identified project asset where legally and contractually appropriate—for example, a particular master recording. Composition authorship and other rights require their own analysis and records.
No. A project may earn nothing. Any related revenue definition, accounting, costs and distribution must be stated in the agreement, without a guaranteed return.
Yes, for a defined project purpose. Further discussion requires separate diligence and terms; this page is not an offer of securities, tokens or a public investment product.
Proposal route
Send the intended outcome, present stage, relevant links, current team, requested contribution, material constraints and the next decision you need.