The thirteen Dionyas inquiries on production operations settle one thing in the design of their questions: the part of music-making worth asking about is the passage of work from one hand to another, and that passage should be carried by an object someone can check. They are far less sure that any single object tells the truth about the work behind it, and they reach the people doing the work only through agreement and refusal. The chapter that follows shows how, and adds to the two debates of the Introduction: the study of coordination, which argues over formal objects and local practice, and the study of creative labour, which asks what project work does to the people inside it.
1.1Data and method
The data are Dionyas's public list of inquiries, fetched by plain requests and kept as snapshots in the study's folder. The list holds 1,539 inquiries across 32 domains, of five kinds: 759 cases, 500 historical questions, 256 general designs, which the list calls foundations, 18 chart questions and 6 signal questions. Each sits in one of three lanes: 1,276 in the evidence lane, 250 in a qualitative lane and 13 in a symbolic lane. The list describes its own type as editorial question design and gives its count of generated judgments as 0. A record has six fields that this study reads: a title, a question, a scope that says what the inquiry covers, a list of the material it needs, a boundary that says what it may not claim, and a state.
The selection rule is one sentence: every inquiry whose leading domain is production operations and continuity, whose lane is evidence, which is a general design or a case, and whose scope names no artist, work or project. The domain holds 35 inquiries: 15 historical questions, 12 cases and 8 general designs, all but 1 of them in the evidence lane. Of the 19 general designs and cases in the evidence lane, the rule leaves out 6 whose scope is written with any Latin letters, a mechanical test that catches scopes carrying names in Latin script, and keeps 13. The rule was chosen so that the paper would read how the studio frames operations in general rather than what it says about named items, and the 6 were left out by the rule, not by reading them first. One kept case names a fan platform in its title, though not in its question or its scope; what it says of that platform is its framing, which this study has not checked.
The thirteen fall into two groups. Eight are general designs. They name no artist, work or market, and they say that these will be named when the inquiry is put to use. Five are cases, each with a scope of its own and with two questions in place of one. The appendix gives every record in full. The records are in Korean; every quoted sentence below is from one English translation made for this study, sentence by sentence, with nothing added. Dionyas does not say who drafted these thirteen, and no fact about the music business is drawn from them.
Two kinds of property have to be set aside before reading. The first is the studio's form: every inquiry has a scope, needs and a boundary, and every one of the thirteen ends its question with a question mark. None of this is a finding. The second is frame, wording copied from record to record. Frame is measured here by five-word runs, counting a run as frame when it recurs in at least 5% of a site's records and in at least 3. Across the whole list the titles and the questions hold no frame at all, 0% of their runs, while the scopes are 46% frame, the needs 30% and the boundaries 41%. Inside the thirteen, counting a run as frame when it recurs in at least 3 of them, the needs and the boundaries are 100% frame and the scopes 67%.
The reason is plain from the domain table. Every one of the 256 general designs in the list takes its boundary, word for word, from its domain's caution line and its first need from its domain's evidence line. For this domain the caution line reads:
Does not diagnose a person's state of health or mind from the amount of their public activity.
The five cases open their boundary with the same line and take the same first need. They then add a second need and two boundary sentences that the list repeats, word for word, in 628 inquiries across all 32 domains. In the thirteen, therefore, the needs and the boundaries are the studio's frame. This study quotes them to show the frame and does not read them as evidence. It reads as evidence the titles and the questions, which are each record's own, and the scopes of the five cases, which differ from one another. Every number in this paper comes from a script that reads only the snapshots, by simple word tests on the Korean original; the counts describe the records and nothing else.
1.2The handover as the object, and the doubted artefact
The first finding is that the inquiries make the handover, not the finished work, the thing to be examined. Seven of the thirteen questions name a handover, a delivery, a file, a version, an approval, a history, a list, a body of evidence or a hash, and five name outsourcing. The plainest case is the general design about a contractor who leaves.
When an outside producer is replaced, what handover list and what access rights are needed so that sessions, stems, fonts, licences and version information are not lost?
Files that carry on when the maker changes
The title puts continuity in the files, not in the people. The question asks for two things, a list and access rights, and names five kinds of material that a change of maker can lose. This study reads the handover list, in the terms of Star and Griesemer, Institutional Ecology, 'Translations' and Boundary Objects (1989), as a standardised form and the shared store of sessions and stems as a repository: objects that must keep their identity while passing between people who see the work differently. This study reads the question as adding something to those four types. A list is useless without the right to open what it lists, and the inquiry treats access as part of the object.
The general design about commissioning makes the same move earlier in the work, before anyone has delivered anything.
When mixing, video or design is outsourced, what repeated work can be reduced by spelling out the deliverables, the number of revisions, the rights, the schedule and who approves?
The cost the question has in mind is repeated work, the redoing that follows a vague request. The cure it proposes is specification: five items written down before the work starts. Malone and Crowston, The Interdisciplinary Study of Coordination (1994), treat coordination as the management of dependencies, and producer and consumer relationships are among those whose management processes they analyse. The commissioning inquiry is a question about exactly that dependency, and it puts the means of managing it in a document. The general design about a late vocal is the only one of the thirteen that treats time itself as a chain of dependencies:
When a vocal recording is late, how are the schedules for mixing, mastering, distribution and video linked, and slack at which stage reduces the overall delay?
It does not ask who is to blame for the delay or whether the date should move. It asks where in the chain spare time would do the most good, which is a question about the structure of the work and not about any person in it.
When a handover goes badly, the inquiries count it as cost. The general design on quotes asks:
Where an outsourcing quote is low but revisions, handover and the checking of rights are unclear, by what items should the total cost of production and the risk be compared again?
Revisions, handover and rights are named here as what a low price can leave unclear, and the question turns that unclarity into items on a list to be compared. The inquiry does not say which quote to prefer. It asks what a comparison would have to include for the price to mean anything.
The five cases go further, and in a consistent shape. Each asks a first question about what record or procedure would carry the work, and then a second question asking whether something may or can be done. All five end on that second question, and this study reads each as casting doubt on a single artefact. The case on mastering shows the shape most clearly.
If the mix, the AI candidates, a person's corrections and the final approved version are told apart by hash, time and the person responsible, how can errors just before distribution be traced? May approval status be decided from the file name alone?
The first question builds a log in which every version has a fingerprint, a time and a person. The second names the shortcut the log is meant to replace: a file called final. The case's own account of what it covers adds a condition of method, level matching and blind listening.
The same mix, with authorisation · level matching and blind listening · inquiry design · awaiting judgment
The same refusal of a single artefact runs through the case on what a distributor should receive:
When whether AI assisted, the extent of its use, the rights holders' consent and the human contribution are passed to the distributor, what evidence should be bundled together? Can the whole production history be reconstructed from the final audio file alone?
The finished file, the one thing every listener and every distributor actually receives, is named here as insufficient evidence of how it was made. Suchman, Making Work Visible (1995), sets a literature that represents work in order to transform it against the knowledge people have of their own work, which others placed differently do not share. This study reads the distributor case as asking a related question about a product: how much of the work a finished object can represent at all. The form of the question suggests, in this study's reading, that the object cannot carry its own history, and the question leaves open what a bundle would need to hold.
The case on delivery puts the doubt in terms of rights.
In outsourced mixing and video, how should the scope of delivery of final files, stems, sessions, fonts and sources be stated so that the work can be redone? May delivery and the transfer of rights of use be taken to mean the same thing?
Strauss, Work and the Division of Labor (1985), considers the division of rights as against the division of labour. This study reads the delivery case as asking whether those two divisions travel together when files change hands, and it leaves the answer open. This study does not answer it either; whether any delivery carries any right is a matter for the parties and their agreements, not for a reading of a question. What the reading can say is that the inquiry refuses to let the act of handing over a file settle what was handed over.
The case on corrected credits turns the doubt back on the record-keeping itself.
When an artist's name, a song title or a rights credit is corrected, which should be preserved, the original text of earlier observations or the current form? Can it be traced which version a past judgment relied on?
Here the artefact under suspicion is the current, corrected form of a name or credit. If it simply replaces the old one, any judgment made under the old form loses its footing. The question asks for a repository with a history. This study reads it as Star and Griesemer's boundary object extended through time, a reading beyond their note: an object that keeps its identity across versions as well as across viewpoints. The fifth case, on operation and trust, doubts a different kind of artefact, a written procedure.
If how fans understand the published procedures for operation, reporting and correction is surveyed, where do actual experience and the wording of the guidance diverge? Without operating authority, can collecting private posts be avoided?
The guidance is the written face of how something is run, and the question assumes that experience and wording may come apart. Carlile, A Pragmatic View of Knowledge and Boundaries (2002), describes boundary objects as means not only of representing knowledge but of learning about and transforming it at a boundary. Most of the thirteen inquiries ask for objects that represent and transfer: lists, logs, bundles, preserved texts. Only the case on operation and trust asks how an object, the published guidance, is understood on the far side of a boundary, which this study reads as closer to the learning and transforming Carlile describes.
Read together, the general designs and the cases lean toward formal objects in the debate the Introduction set out. They ask what list, log, bundle or comparison would carry the work, and none asks to leave a handover to local judgment. But this study reads the second questions of the cases as showing that the lean has a limit. Each can be read as naming an artefact that seems to settle a matter, a file name, a final audio file, a delivery, a current credit, a page of guidance, and as asking whether it may be trusted alone. On this reading the inquiries want the work written down, and they do not trust any one piece of writing to be the work.
1.3The worker behind the file
The second finding concerns the people. Where the inquiries move from files to the workers who make them, they change method: the object gives way to agreement, and to refusals of particular ways of knowing. The general design on condition shows the change.
Without concluding anything about a state of health or mind from public stages alone, how are the workload, safety and rest conditions agreed with the person concerned to be managed?
Operations that do not guess at a person's condition
The domain's caution line, which every one of the thirteen carries as its boundary, says the same thing in the studio's frame; this question is the one place where a record says it in its own words and builds a question on it. What it refuses is inference from what is visible: a performer's public stages are not to be read as evidence of their health. What it asks for instead is management of conditions agreed with the person concerned. Suchman holds that people should be able to shape how their work appears to others, and that self-representation is a form of empowerment. The condition inquiry reads as a design in that spirit, in this study's reading: it does not make the performer's state visible by observation, and it puts the terms of the work in an agreement the performer is party to. It is also, by its form, not health advice of any kind, and this study adds none.
The general design on rest frames the same person through the continuity of production.
When rest and time to switch between tasks are put into a schedule of activity, by what criteria centred on the people concerned should a short-term fall in exposure and the long-term continuity of production be weighed together?
Not seeing rest only as a cost
The title argues with an assumption, that rest is only a cost, and the question keeps the terms of that assumption: rest is weighed against exposure lost, and its gain is named as the continuity of production. The criteria are to be centred on the people concerned. Hesmondhalgh and Baker, 'A Very Complicated Version of Freedom' (2010), found creative workers' experience of hours and insecurity at best highly ambivalent, with pleasure and obligation blurred, and Watson, 'Running a Studio's a Silly Business' (2013), describes exhausting yet bulimic work regimes. The rest inquiry sits close to their subject and asks for a weighing, not a rule, and it names whose interests should be at the centre. Only these two questions, on rest and on condition, speak of the person concerned, and both leave open who that person is.
The case on operation and trust carries the same refusal into a fan community. Its second question, quoted above, asks whether, without operating authority, collecting private posts can be avoided, and the case's own account of what it covers names the means it would allow instead.
Permitted aggregates per artist and a voluntary survey · 90 days · inquiry design · awaiting judgment
Permitted counts, a survey people choose to answer, and a period of 90 days: the only figure in the scope of any of the thirteen records. The design asks to learn how fans experience a procedure while declining one way of seeing them. As with the condition inquiry, what it makes visible is limited by what the people seen have agreed to.
Two general designs concern the coordination among people rather than their condition. One asks:
When many stakeholders comment on every demo and the direction wavers, at what stage is whose feedback needed?
This study reads this as articulation work in the sense of Gerson and Star, Analyzing Due Process in the Workplace (1986): many people with different views, no globally correct answer, and a need for a local closure. The question does not propose a form. It asks for a sequence of whose voice counts when, which is a closure of the local kind Gerson and Star describe, reached by deciding who speaks rather than by writing a better document. Bechky's account of common ground built across occupational communities fits less well, since the inquiry asks to narrow who is heard, not to build a shared understanding among them. The other design asks where a team should draw its own edge:
In a team that means to bring repeated work in-house and leave distinctive expertise outside, by what criteria of expression, learning and schedule, and not only cost, should the line be drawn?
Leyshon, The Software Slump? (2009), traces how software first encouraged a vertical disintegration of recording production and later, through cheaper digital rigs, left the studio sector in crisis. This study reads the in-house inquiry as a small question about a related boundary, between the team and the outside. It counts the team's own expression and learning among the criteria. The learning of whoever works outside the line is not among them.
That is the outer edge of the design. Five of the thirteen questions concern outsourcing, and all five ask from the side of the one who commissions: what to spell out in a request, what a low quote leaves unclear, what list and access to ask for when a contractor is replaced, what the scope of delivery should be, where the line between inside and outside should fall. The outside worker appears as a source of files, revisions and quotes. Pay or fees appear in none of the thirteen records. The risk the quote inquiry names is the risk to the production. Watson describes freelance project work that shifts the pressure of finding work, and the financial risk of failing to, onto individual producers and engineers. Gill and Pratt, In the Social Factory? (2008), bring the study of precarious cultural work into dialogue around temporality, subjectivity and solidarity. Read beside them, the thirteen inquiries are written from the side of whoever commissions the work. They address the performer on the inside through agreement and refusal, and they address the worker on the outside through specification.
This is a finding about the design, not a fault in it. Dionyas's domain table gives this domain's focus as the conditions of production made by outsourcing, schedules, labour, health and handover, so labour is in view; but a question set has to choose a position to ask from. The position these records choose is the producer's, or the team's: someone deciding how to commission, receive, schedule and rest. The questions the creative labour literature puts at the centre, what the work pays and what it costs the person who does it, are not among those the thirteen ask.