For the drama carried by words and music
An early-access guide
Give the music
something to change.
A person needs an answer. A scene reaches its limit. The number begins, and the world cannot quite return to what it was.
Libretto.software explores the writing and handoffs behind opera and musical-theatre text: dramatic action, character language, musical relationships and a version the next collaborator can identify.
Read the working guideThe book
stays open.
Ivo
The register has
one empty line.
He turns the book toward Mara.
02What does
the silence keep?
A lyric possibility
One name waits
in the margin.
After the number, the question
has become public.
Shared Playscript and editorial foundations are described in their existing contexts. No dedicated libretto workspace, score engraving, audio generation or word-to-music synchronization is established here.
Eleven chapters of the work
The page.
The number.
The next decision.
Read the guide in order or begin with the relationship your piece needs to clarify. Every chapter distinguishes a human creative method from a demonstrated shared-tool result.
Libretto / The working guide
ContentsThe dramatic need
Begin where speaking alone leaves something unresolved.
A libretto gives people reasons to act, listen and sing. Find the pressure in the scene before deciding how many numbers the work should contain or what its most memorable line will be.
Start with a person who needs something from another person. The need may be practical, emotional or both, but it should be capable of producing an action. In our invented chamber piece, The Lantern Room, an archive keeper wants an apprentice to sign a register before the harbor ceremony begins. The apprentice has discovered an unexplained omission and refuses. A document, a deadline and two incompatible intentions are enough to begin a scene. Their relationship gives the words somewhere to go before music enters the discussion.
Ask what changes when the exchange becomes sung. Time might expand around a decision that would pass quickly in ordinary speech. Two people might reveal conflicting thoughts simultaneously. A repeated phrase might expose a feeling the speaker cannot yet name directly. These are possible dramatic functions, not rules that every work must follow. The useful question is what the musical treatment allows this particular scene to do. An attractive song placed beside an unchanged argument may interrupt the action rather than develop it.
Give the central conflict a concrete test
Write a brief account of the scene before drafting its lyric. Mara, the keeper, needs the register closed. Ivo, the apprentice, needs the missing name acknowledged. The Clerk needs the ceremony to proceed without public embarrassment. Now choose the decision that the scene must reach. Perhaps Ivo agrees to carry the book outside but leaves it open. That action can preserve the conflict while changing its location and audience. It gives the next scene an inherited problem rather than a fresh explanation of the same premise.
Distinguish the work's large question from the immediate task. The piece may explore whose labor a community remembers, but a character cannot perform the instruction explore collective memory. A character can conceal a page, ask for a signature, interrupt an announcement or return a book. Those actions provide material a performer can make legible. Keep the thematic question nearby, then write the pressure into things people actually attempt. The resulting brief should help collaborators understand both the human stakes and the next playable action.
Understand the starting record
The shared Playscript document flow can create a document record with a supplied title and an accepted text format for its authorized playwright roles. It returns document identity, author information, format, draft status and creation metadata. That action establishes a record; it does not author the libretto body, compose a musical number or create a score. An unavailable document store returns an explicit unavailable result. The existence of the source route does not establish a dedicated Libretto workspace accessible from this page.
Use that distinction when preparing an early-access inquiry. Bring the dramatic brief and explain what you need to retain with it: the current text, a scene question, a composer's reference or an agreed revision. Ask which actual object the proposed workflow creates and which material you must supply separately. A title in a document list is useful identification, but it cannot stand in for the written scene or a musical setting. The first meaningful result is something collaborators can read and discuss in relation to the intended action.
Must every sung moment justify itself with a plot event?
A number can change perception, relationship or emotional pressure without introducing a new incident. Let the test remain broad enough for those changes. What matters is that something in the experience becomes different because the moment exists. Read the scene before and after the number and describe that difference. The result is a dramatic reason for the music, with room for contemplation, contradiction and pleasure as well as decisive action.
Libretto / The working guide
ContentsScenes and numbers
Keep the dramatic map and the musical map in conversation.
A scene and a number can overlap without being the same unit. Make their relationship explicit so a cut, move or expansion does not quietly leave the surrounding drama behind.
Prepare two modest working lists. One follows the dramatic scenes and records who is present, what they want and what changes. The other follows the proposed musical numbers and records their function in the action. A number might occupy most of a scene, cross a transition or bring several locations into one musical experience. The lists should help collaborators discuss those relationships. They are human planning documents, not evidence that a specialized musical-number organizer is already implemented in the shared tools.
Give each entry a stable descriptive name while the order is changing. Register argument is easier to recognize during revision than number four when three new passages have just been inserted. You can still assign working numbers for rehearsal communication, but record what they identify. If a duet becomes two shorter numbers, explain which material moved and which references became obsolete. A useful map helps a collaborator find the actual text and musical context, rather than requiring them to infer it from the latest numbering scheme.
Make the transition part of the work
Inspect what happens immediately before and after a number. Who begins it? What prompts the first sung thought? What practical condition exists when it ends? In The Lantern Room, a duet about the missing entry might leave the book physically open between keeper and apprentice. If the following scene assumes it has been signed and removed, something necessary is absent. That missing action cannot be repaired by a heading alone. It needs to become legible in the text, performance plan or agreed musical treatment.
Look for work duplicated across the scene and number. A spoken exchange may explain the omission, followed by a lyric that explains it again without changing its meaning. Decide which portion should establish the fact and which should develop its consequences. Conversely, an overcompressed transition can make the audience miss the information needed to understand the music. Read or perform the sequence continuously before deciding whether an apparent repetition is redundant or provides the orientation the listener needs.
Read parsed structure at its actual scope
The shared Playscript parser can derive an ordered act-and-scene index from supplied text using its recognized format conventions. Plain text and the two DG formats use conservative act and scene headings. Fountain has its own section and scene-heading rules. When the supplied text yields no recognized structure, the helper returns a single Full script scene with a false parsed status. That fallback retains an honest whole-text view; it does not invent missing scene boundaries or identify musical numbers from their dramatic purpose.
The scene-navigation helper can project the parsed result into an ordered contents list. This is a shared computation, not proof of a dedicated libretto navigation interface or a clickable musical score. Ask to see the actual supplied text, recognized headings and returned structure when evaluating it. A musical-number heading may be useful to people while remaining outside the parser's recognized scene conventions. Keep that difference explicit instead of assuming every label in the manuscript becomes a structured object with its own behavior.
Will formal labels constrain a fluid piece?
The labels are working coordinates. A continuously sung work may need a different map from a piece with discrete spoken scenes and songs. Choose the least elaborate structure that lets collaborators locate material and discuss changes accurately. Do not force the piece into a template merely to make an index look complete. The useful result is a reliable relationship between the written sequence and the musical plan, with unrecognized or provisional structure described honestly and the artistic form still open to revision.
Libretto / The working guide
ContentsSpoken and sung text
Choose what the audience needs to hear once, and what can return.
Spoken dialogue and sung language can carry different kinds of attention. Decide what each passage asks of the listener before polishing its surface or assigning it a permanent label.
Write the scene's essential information in plain sentences. The register omits a name. The ceremony is about to begin. Mara wants Ivo's signature. This account is a working check of what the audience needs to understand. It is not necessarily language anyone should speak onstage. Once the information is clear to the collaborators, decide how the piece will reveal it. A glance, an interrupted request or a repeated refusal may do more dramatic work than a complete explanation of the situation.
Give sung language a purpose within that exchange. It may enlarge an image, expose an unstated desire or let several meanings accumulate around a phrase. It may also carry concrete information directly. Avoid assuming that spoken text must always explain while music only expresses feeling. The useful distinction is what the listener needs from this passage and how the chosen treatment helps them receive it. A crucial name heard once during a dense ensemble may need a different introduction from a phrase that returns clearly several times.
Test two treatments of the same thought
Consider the original spoken line, The register has one empty line. Beside it, place the invented lyric fragment, One name waits in the margin. The first identifies a practical fact; the second gives the absence a human pressure. Neither is a finished setting. Ask what becomes clearer or less clear when one replaces the other. You may need both at different moments, or neither in their present wording. The comparison is useful because it connects a language choice to the audience's understanding of the scene.
Read the surrounding exchange aloud without pretending it is a final musical performance. Mark where information arrives too quickly, where a speaker restates what the audience already knows and where a return changes the thought. Then discuss the intended musical treatment with the relevant collaborator. A spoken reading can expose verbal confusion, but it cannot establish the intelligibility, duration or expressive effect of a setting that has not yet been heard. Keep the uncertainty specific instead of calling the entire passage successful or unsuccessful.
Treat format as representation
The shared Playscript document create accepts plain text, Fountain and the two supported DG formats. It defaults to the modern DG format when one is omitted and rejects an unsupported format in that create input. These are text-format choices. Selecting one does not create separate spoken and sung text layers, a score relationship or an automatic conversion of dialogue into lyric. A manuscript convention still needs to be explained to its readers and checked in the actual representation they receive.
The shared HTML-to-Fountain converter handles a limited set of semantic inputs and is not a blanket lossless conversion of any rich document. For example, a character cue with no dialogue can produce literal placeholder dots. If conversion is part of a proposed workflow, inspect the result with your own difficult passage: a sung cue, an interruption, an incomplete entry or a note intended only for collaborators. The output needs to preserve the distinctions the next person requires, rather than merely exist as a text file.
Can a continuously sung work use this distinction?
Yes, as a distinction of dramatic function rather than a demand for spoken dialogue. A recitative-like exchange, an extended lyrical passage and a layered ensemble may ask for different kinds of verbal attention while all being sung. Describe the intended function in terms your collaborators share. The result should be a readable and discussable text whose informational load matches its dramatic purpose, with the eventual musical and performance questions left open until there is evidence to assess them.
Libretto / The working guide
ContentsCharacter language
Let each person reveal a different relationship to the words.
A libretto's voices need more than different names above the lines. Give each character a distinctive way of pursuing the same conflict, then hear what happens when those approaches meet.
Start with what each character is trying to accomplish in the exchange. Mara may speak in procedures because a completed register lets her preserve order. Ivo may ask concrete questions because the omission is something he cannot ignore. The Clerk may use collective language to make a disputed account sound settled. These are possible approaches within an invented scene, not fixed personality profiles. Their value is that they produce different verbal actions around the same object, giving performers something more useful than a general instruction to sound different.
Collect a small set of choices from the actual draft. How directly does the character ask for what they want? What do they avoid naming? Which images belong to their work or experience? How does their language change when they lose control of the exchange? A diction note should help collaborators understand deliberate differences without prescribing every future line. A person can surprise the audience, and a formal character can become suddenly plainspoken when the scene makes that change meaningful.
Distinguish a shared phrase from a shared voice
Let two people use the same words for different reasons. Close the book could be Mara's administrative instruction, Ivo's accusation or the Clerk's attempt to prevent a public argument. The phrase becomes theatrically useful when its action is clear in each context. Mark who hears it and how they respond. A repeated phrase does not automatically unify the drama; it can also expose the differences the work is trying to bring into contact.
For an ensemble, prepare a plain account of each participant's thought before considering simultaneous text. If everyone says a variation of the same sentence, the layering may add force but little dramatic distinction. If the thoughts differ, decide which information must remain intelligible and which can operate as texture or pressure. This is a collaborative artistic question. The shared tools do not analyze simultaneous lyrics, balance voices or guarantee that an audience can distinguish every verbal strand in performance.
Keep character cues legible to the tools you use
The shared parser extracts character cues for its Fountain handling. Its plain-text and DG paths can recognize act and scene structure without establishing the same cue extraction. A character name printed above a line therefore should not be assumed to produce identical structured results in every supported format. Inspect the returned cues in the actual example you intend to use, especially where names, extensions or unusual manuscript conventions make an entry ambiguous.
The sides helper uses supplied text and parsed cues to produce a selected role's text with other characters represented as cue names. It is a text computation, not a performer profile, vocal range assessment or musical part. Where no selected or speaking role is found, it returns an explanatory note rather than a fabricated selection of lines. A character's diction and musical requirements still need the relevant human review. Useful extraction depends on an accurate representation of the material supplied to the helper.
Does distinct diction mean an exaggerated verbal habit?
A repeated mannerism can help, but it can also become a substitute for characterization. Look for differences in what the person notices, assumes and is willing to ask. Let the language respond to changing relationships. The result of the pass should be a set of voices whose choices are recognizable in context, with enough flexibility for growth and contradiction. A cue name tells a reader who has the line; the written action and eventual performance make that person worth listening to.
Libretto / The working guide
ContentsProsody and intelligibility
Make room for the thought inside the musical phrase.
Words need a workable relationship with stress, duration and breath. Test the language in its intended context and distinguish what a reading reveals from what only a musical setting can answer.
Speak the passage naturally and mark the words that carry its main thought. Then consider where the intended musical phrase places emphasis, if a setting exists. A long note can enlarge a word; a fast sequence can hide one. The relationship may support the sentence or deliberately complicate it. What matters is that the choice can be heard and discussed. A neat syllable count alone cannot establish whether the audience will understand the accusation, question or qualification the character is making.
Look at the physical demands of the words. Dense consonants, a sequence of names or an awkward vowel on a sustained pitch can make a passage different to sing than to read. Work with the appropriate composer and performer when assessing that demand. The writer can suggest alternatives and clarify meaning, but should not treat a comfortable spoken reading as proof of singability. Keep a note of which conditions were actually tested and which remain hypothetical because the music or performer is not yet available.
Preserve the word that changes the action
In The Lantern Room, the difference between sign this line and sign his name may alter the conflict. The first can sound procedural; the second may expose whose identity is at stake. If the setting obscures the important word, the audience can miss the change in the scene even while hearing an expressive phrase. Try the alternative in the surrounding exchange and ask a listener what changed. The useful feedback concerns the dramatic information received, not only whether the line sounded attractive.
Treat breath and silence as part of the collaboration. A pause may give the other character an opening, delay an answer or allow the audience to recognize a reversal. An authored instruction in ordinary script text remains an instruction people must interpret. The established tools do not turn it into a timed cue, synchronize it with a score or ensure a performer follows it. Describe the intended action clearly and test it in the actual reading or rehearsal process the team uses.
Use theoretical vocabulary within its limits
The adjacent Musique core supports deterministic work with spelled pitches, simple intervals, key signatures, scale notes and triads. Its education route can generate theory worksheets from supplied specifications and reproducible seeds. Those exercises can support a shared vocabulary, but they do not scan libretto meter, set a line to music or save a score. A correct interval answer is a result of a bounded instructional computation. It is not an assessment of whether Ivo's question reaches the audience during a duet.
If a proposed workflow includes musical support, ask which material is supplied and which result is returned. A worksheet document, a lyric reference and a musical performance are different objects. No engraving, piano accompaniment, audio generation or word-to-note synchronization is established for this guide. Bring a difficult line and identify what you need to assess: stress, breath, comprehension or the relationship to a particular setting. That makes it possible to evaluate an actual capability without allowing a general music label to imply the missing work.
Must every line be immediately understandable?
A passage can use deliberate ambiguity or dense simultaneous language. Decide what kind of uncertainty serves the work and what the audience still needs to follow. It may be enough to hear the conflict while individual phrases become clearer on return. The result of an intelligibility pass is a set of chosen priorities and inspected passages, with their performance conditions stated. It is not a universal clarity score or a guarantee that every listener hears every word in the same way.
Libretto / The working guide
ContentsRepetition and reprise
Bring the words back after the world has changed.
A returning number can remind an audience and revise what the memory means. Identify the change that makes the return necessary, then inspect the old words against the new dramatic situation.
Write down what the first appearance of the material establishes. Perhaps Mara's opening instruction to close the register expresses confidence that order protects everyone. By the time that phrase returns, the apprentice has shown what the official account leaves out. The same words can now sound defensive, exhausted or newly understood. The reprise earns its place through that changed context. It does not need an entirely new lyric to have a different dramatic function, but the function should be recognizable in the sequence the audience experiences.
Identify whose memory the return activates. A character may knowingly repeat an earlier phrase, or the audience may recognize a musical relationship that the character does not acknowledge. These choices create different effects. Keep them clear in discussion with the composer and director. A note saying reprise tells collaborators that material returns; it does not explain whether the return is deliberate within the fictional world, an external dramatic comment or a mixture the production intends to explore.
Revise the surrounding action first
Before rewriting the returning lyric, read the scene that now leads into it. What has the character learned? What can they still plausibly ask? Who is present to hear the words this time? If Mara sings an earlier assurance while Ivo holds the open register, the physical and relational context can supply the contradiction. If the necessary change is invisible, a revised final line may have to carry too much explanation. Make the scene support the return instead of asking the reprise to repair every missing step.
Compare an exact return with a changed one. A single altered pronoun can transfer responsibility; a removed qualification can make an admission more direct. Hear what the change costs as well as what it gains. Familiar wording can let an audience notice a transformed intention, while too much new text may erase the recognition the reprise depends on. There is no automatic rule for the correct balance. The collaborators need a shared account of the change they want the audience to experience.
Keep repeated material related without assuming synchronization
No dedicated reprise tracker, musical-theme database or lyric-to-score synchronization is established in the shared tools. A writer can retain explicit textual references through their working process, but a change to one occurrence should not be assumed to update all related passages. If a recurring phrase changes, inspect each place that uses it. Some may require the revision; others may need the older wording precisely because the dramatic comparison depends on it.
Adjacent Playscript version records can retain supplied snapshot identifiers and references. They do not identify every occurrence of a musical idea across the libretto and score. A version list tells you which snapshot records exist, not which reprises remain consistent with the current composition. In an early-access inquiry, bring a paired example where the first appearance changes and the return must preserve one deliberate difference. Ask what actual record or review process makes that relationship intelligible to the next collaborator.
Is repetition always supposed to reveal a new meaning?
A return can also sustain ritual, establish a collective rhythm or offer recognition and pleasure. Describe that function honestly instead of forcing every repetition into a reversal. The important question is whether its presence and duration serve the piece. Try a shortened return or a continuous reading without it, then compare the experience. The result is a deliberate relationship between remembered material and present action, with necessary textual changes inspected and the musical consequences discussed through the actual creative process.
Libretto / The working guide
ContentsBook, lyric and music
Make the creative handoffs as clear as the scene's intentions.
A libretto can involve several writers and a composer, with directors and performers entering at different stages. Agree on which decisions each handoff needs, and what material carries those decisions forward.
Describe the collaboration through actions. One person may shape the dramatic sequence, another may draft the lyric, and another may set it musically. Those responsibilities may overlap or belong to a single person. The useful question is who proposes a change, who decides the current wording and who inspects its consequences elsewhere. A line cut from the book can remove the setup for a number. A musical expansion can change how long a practical action must remain unresolved. The team needs a way to discuss those connections without assuming every contributor sees the same version.
Give a handoff a specific question. Can this exchange support the duet's entrance? Does the new lyric retain the information the scene requires? Which words can change without losing the setting's intended emphasis? Supply the material needed to answer the question, including any known gaps. A composer receiving a lyric after a major scene revision should know what changed around it. A writer reviewing a setting should know whether the current performance includes the latest text or an earlier working copy.
Separate offered material from accepted material
A collaborative session produces possibilities as well as decisions. Preserve promising alternatives without letting them masquerade as the current libretto. At the close of the session, identify the text the group intends to continue and the questions still open. Read the relevant join between scene and number. That small check can reveal that one collaborator accepted a change to the lyric while another assumed it remained an experiment. The result should be a shared starting point for the next piece of work.
The shared editorial assignment and selection flows can retain contributions, review decisions and passage references in their publication context. Their combine action does not merge or generate the resulting prose. Someone still has to reconcile the chosen material into a readable libretto passage and consider its musical relationship. A selection record can document a decision; it cannot replace the creative work between selecting useful lines and making them function together in the scene.
Read access as an actual permission record
The adjacent Playscript access-grant flow can add, list and revoke co-writer access records under its applicable author, management, membership and consent conditions. These are specific shared records, not a general promise of a public Libretto collaboration room. A saved grant does not establish that an active editing connection has synchronized the text. Ask which actual surface a participant can use and which actions the arrangement permits before treating a contributor's name as evidence that they can see or edit the manuscript.
Keep contribution context separate from agreements about the work. A record that someone supplied a passage can help the team understand its history. It does not by itself determine credit, ownership or terms for a production. Where collaborators need an agreement, handle that through the relevant people and documents rather than inferring it from an editorial role or saved access grant. This guide describes writing and shared-tool boundaries; it does not create a commission, rights deal or commercial arrangement for an opera or musical.
Will explicit responsibilities make collaboration rigid?
They can make experimentation easier when people know which choices remain provisional. Agree on the immediate decision without trying to fix every future responsibility in advance. Update the working arrangement when the piece or team changes. The useful result is a creative process in which a proposal can be explored, a decision can be identified and its consequences can reach the relevant collaborator. The software should be evaluated against those concrete tasks, rather than credited with automatically creating artistic agreement or trust.
Libretto / The working guide
ContentsReadings and workshops
Ask the room to reveal a particular uncertainty.
A workshop becomes more useful when the team knows what it is testing. Prepare the text, references and questions so observations can lead to a specific next revision.
Choose the scope of the reading before circulating material. You might need to hear the book without music, a single scene and number, or the dramatic sequence around a reprise. Each reveals different information. A plain reading can expose unclear relationships and overloaded sentences, while a musical workshop can test questions that depend on duration, setting and performance. Neither should be asked to establish an outcome the available materials cannot support. State the unresolved question and the kind of observation the session can reasonably provide.
Identify the working version and the participants' roles. A reader may need the full scene, while someone testing a particular entry may need a narrower extract with enough context to understand the cue. Make clear whether bracketed material is a direction, an optional text or a note for discussion. In The Lantern Room, the instruction to carry the open register changes the scene's public meaning. If a reader mistakes it for dialogue or omits it without explanation, the group's reaction may concern a different sequence from the one the writer intended to test.
Inspect sides before depending on them
The shared sides helper computes text for a selected role from supplied script and parsed cues. It retains that role's dialogue while representing other characters with cue names rather than their full speech. Relevant directions or neutral text can remain. This can support a limited text-preparation discussion, but it is not a vocal score, accompaniment part or complete account of what another performer will sing. Check the actual output and decide whether its omissions are appropriate for the workshop task.
Cue recognition matters. The parser's Fountain handling extracts cues; other supported formats do not establish the same role-cue structure. If no selected or speaking role is found, the sides helper returns an explanatory note. Do not turn that result into a claim that the character has no material in the authored work. Inspect the supplied format and parsed representation. A limited parser result can describe what the helper recognized without settling what is actually present or dramatically important in the full text.
Collect observations before prescriptions
Ask a listener when they understood what Ivo wanted, what changed when the book moved outside or whether the returning phrase acquired a new meaning. Let the person describe their experience before explaining the intended design. A proposal to cut a passage may point to redundant information, unclear staging or a musical question the reading could not answer. Keep those possible causes separate. The team can then choose a revision that addresses the actual uncertainty rather than implementing the first suggested solution.
Shared editorial comments can retain discussions and resolution records on their defined targets. A resolved thread does not apply a libretto edit, confirm a performer's understanding or produce a rehearsal recording. The established toolset does not time a workshop, transcribe the room, synchronize observations to audio or generate piano accompaniment. Use the real process and tools available to the group, then identify which observations belong to which text and performance conditions. A human timing note describes the session someone measured, not a software-derived score duration.
What if the available performers cannot show the final effect?
Use a narrower question and record the limitation. A preliminary reading may still reveal the scene's basic action even when it cannot show the final ensemble texture. Do not confuse uncertainty about the demonstration with a verdict on the piece. The useful result is a set of observations tied to identifiable materials, followed by a chosen revision or a better-defined next test. A workshop earns its time by clarifying the work, not by producing an indiscriminate list of compliments and corrections.
Libretto / The working guide
ContentsVersions and language
Keep the words, their references and their variants distinguishable.
A libretto can exist as a working text, a setting reference, a translation and a workshop copy. Name the relationship between them before a familiar title makes different materials appear identical.
Prepare a short version note when the text changes hands. Identify the current libretto, the score or performance reference supplied separately and any known differences. The words in scene two have changed; the musical reference still uses the earlier ending is useful information. A recipient can then assess the intended question without discovering the mismatch by accident. The title and date help locate material, but the note explains which representations belong together and which relationship still needs work.
Treat a translation as a particular text with a particular purpose. A literal working translation can help collaborators discuss meaning, while a singable adaptation must address the demands of a musical phrase. A reader-facing translation may have another job again. Do not assume that improving one automatically improves the others. Identify the source version and who reviewed the relationship. This is a human editorial method; no translation engine, subtitle timing or automatic synchronization between languages is established in the shared capabilities described here.
Inspect what the version record contains
The adjacent Playscript version action appends a supplied version number, snapshot hash and optional reference, along with the supplied creator reference. It returns identifying information about that version record. Listing versions provides records and snapshot handles rather than the libretto body itself. These distinctions matter when a collaborator asks which text was retained. A record can identify a snapshot without proving that its referenced content is currently accessible or that it includes every musical and translation artifact the team associates with the piece.
The restore action looks up the selected earlier version and appends a new head carrying its hash and reference. It checks that the new stored hash matches the target hash. The resulting verified flag concerns that stored comparison. It does not freshly hash retrieved editor text, push restored prose into a live editing surface or update the document's current-version pointer. A missing target is refused, and duplicate version numbers are refused during append. Those are concrete record behaviors, not a complete recovery demonstration of a libretto and score.
Compare the changed meaning, not only the changed file
When a source line changes, identify any dependent translation, adaptation or workshop copy that the team needs to inspect. A change from our name to his name can alter responsibility and emphasis even if the sentence length barely changes. The source text and its adaptation may require different revisions to preserve the intended action. Check the line in context, including who speaks it and what follows. A matching file label cannot establish that the dramatic relationship survived the change.
If conversion is part of the handoff, examine the actual output. The shared semantic-HTML conversion is intentionally limited and can emit placeholder dots for a cue without dialogue. Such output may be understandable in one working context and misleading in another. No lossless all-format libretto exchange is promised here. Bring an example with a translation note, an empty cue and a reprise reference to an early-access discussion, then ask what the proposed process retains, omits or requires a person to repair.
Is a reference enough if everyone knows the piece?
Familiarity can conceal differences because collaborators fill gaps from memory. Keep the note concise, but make the current relationship explicit. Open the material the recipient is meant to use and check the changed passage before relying on a stored reference. The useful result is an identifiable set of texts and supporting materials with understood limits. A successful version operation is one part of that result; it does not certify a translation, synchronize a score or prove the next person received the intended copy.
Libretto / The working guide
ContentsReview and proposed use
Keep acceptance, permission and an actual production separate.
A completed text can enter several kinds of review. Identify the action being taken and the object it concerns before treating a saved status as evidence that the whole work is cleared or delivered.
Begin a proposed-use conversation with the material and context. Is the team sharing a private working extract, discussing a staged reading or preparing a particular publication? Which text version is involved, and which music or other material accompanies it? The writing records can help establish what the collaborators are discussing. They do not by themselves establish every agreement required for a production. Keep the actual arrangement with its responsible people and documents rather than allowing a convenient status label to answer a broader question.
The shared Playscript marketplace is an adjacent moderation and licensing flow with specific conditions. It is not evidence of an opera-company submission portal, a theatrical booking service or a completed commission. A submission requires an authorized author, a caller-matching author identity, the applicable minor-author consent and an affirmative authorship declaration. It scans supplied text and records submission metadata and status. That stored submission is not the full authored libretto body or proof that a producing organization has received the work.
Read a refusal according to its actual effects
Some conditions are checked before a submission record is created. A missing required minor-author consent is one such refusal. A content-blocked submission, however, can be saved with blocked and pending status before the response refuses it. A blanket statement that every refusal saves nothing would be inaccurate. Inspect the specific result and record when evaluating the workflow. The useful question is what happened to this request, not whether the interface displayed a generally reassuring success or failure message.
Moderator acceptance has its own checks. Blocked content cannot be accepted through the described action, and the combined author and ticket percentage cannot exceed the permitted total. The accepted catalog input is metadata with an empty script body. A returned catalog or license identifier therefore should not be presented as proof that a complete libretto, musical score or production package is publicly available. The actual content and its intended use need to be inspected through the relevant process.
Keep the money statement exact
The described acceptance response reports a payout status of queued_not_charged with a zero amount. That response does not collect a charge or pay an author. It is a specific boundary of this Playscript action, not a general claim about every financial system or every possible agreement. This page does not sell performance rights, administer royalties or establish a payment arrangement for the fictional work. An editorial or catalog record cannot be treated as evidence of money received or a production commitment completed.
For a real handoff, identify what the next person is expected to review and what remains unresolved. A producer may need a particular text and separate musical materials; a workshop participant may need a narrower extract; a publication may need its own presentation checks. Use the actual agreed process for that destination. No score engraving, audio export, accompaniment delivery or performance scheduling is established by the flows described in this guide. Source implementation alone does not prove a configured service for the visitor's intended use.
Does this mean the writing process needs a legal decision at every turn?
The working draft can remain exploratory. The important distinction is when material moves into a use that the participants need to agree on explicitly. Preserve the contribution and version context while writing, then review the actual arrangement at the appropriate handoff. This guide does not provide a legal opinion or manufacture permission from metadata. Its practical aim is to keep the text, the recorded review and the real-world next step understandable as related but separate results.
Libretto / The working guide
ContentsAn early-access inquiry
Bring the passage where the handoff gets difficult.
A useful conversation starts with the work you need to accomplish. Show the scene, the number and the relationship between them, then ask for evidence of the particular support you require.
Libretto.software is presented here as an early-access product guide grounded in shared Playscript and editorial foundations. Those include document metadata, bounded text formats and parsing, cue-based sides computation, access records and snapshot-reference version actions. Adjacent Musique work is deterministic theory instruction. None of those facts establishes a dedicated deployed libretto workspace, a saved score or automatic synchronization between words and music. The contact link opens an inquiry about fit; it does not provision a production environment or promise future activation.
Choose a small example you are comfortable discussing. A scene leading into a number, a changed reprise or a translation that no longer matches its source can make the requirements clear. Include the current text, the relevant separately held reference and a short explanation of the unresolved relationship. You do not need to expose a complete unpublished work to describe a problem. A compact case gives everyone a fair chance to inspect the same material and understand what a successful result would mean.
Ask to see the actual inputs and outcomes
For a document record, identify the supplied title and format and inspect what the created record contains. For parsing, compare recognized headings and cues with the manuscript. Include an example that should remain a single unparsed text rather than receiving invented structure. For sides, inspect the selected role's text and the omitted dialogue. For a version action, distinguish stored snapshot information from retrieved content. Each demonstration should end with an understandable result and a clearly stated limit, including any refusal or unavailable condition encountered.
Bring essential requirements that the evidence does not establish. You may need a score editor, musical exchange format, audio player, subtitle workflow, language alignment or dependable recovery of a whole set of creative materials. Name those functions directly and ask for concrete proof of any proposed support. A parsed scene list cannot substitute for a score, and a snapshot hash cannot substitute for a demonstrated recovery of the actual words. Your existing tools may need to remain central while a narrower editorial handoff is evaluated.
Define a trial around a creative task
Choose an outcome with a clear stopping point. One possibility is a workshop extract whose recognized cues and omitted dialogue have been checked. Another is a corrected scene-and-number handoff with the current text and older musical reference clearly distinguished. A third is a version-reference operation whose exact stored result is understood. Identify who will inspect the outcome and what would prevent broader reliance. The goal is to establish whether the proposed workflow resolves the problem you brought, not merely whether a demonstration can create several records.
Ask which surface is actually available in the proposed context, which roles can use it and what material can be retained at the end of the evaluation. The shared document store can return an explicit unavailable result, and authorized routes have their own role and consent conditions. A polished guide does not remove those conditions or prove a deployed configuration. This page does not offer a price, checkout, rights purchase or activation date. Any particular arrangement needs its real scope established in the conversation.
What if the work does not fit a conventional libretto?
Describe the actual relationship between text, music and performance instead of forcing it into familiar labels. A chamber piece, a work with extensive dialogue and a continuously sung drama may require different representations and review methods. The guide is useful when it helps you make those differences concrete and evaluate the support honestly. The creative decisions remain with the people making the work: when to sing, what to repeat and what changes because the number happened. A worthwhile process should make those decisions easier to inspect and carry forward.
A concrete next conversation
Bring the scene
that needs another ear.
Describe the relationship between your text, musical materials and collaborators. Identify the difficult handoff and the result you need to inspect. Start with a small example you are comfortable discussing.
Inquire about Libretto.softwareAn early-access inquiry. No account, purchase, rights agreement or activation date is created by this action.