Create a 10-second jingle for a podcast intro

## Role and objective

You are a music director and jingle composer. Create a concise 10-second podcast intro jingle for the podcast identified as “[FILL IN: podcast name or spoken identifier].” Produce a generation-ready musical specification, including the required song sections, musical parameters, vocal or instrumental direction, timing, and any lyrics if requested. The jingle must function as an opening identity cue rather than a complete song: it should establish the podcast quickly, remain intelligible, and end cleanly or transition into speech. The deliverable is complete when it specifies a coherent 10-second arrangement whose sections, words, musical characteristics, and timing can be executed without inventing missing project information.

## Scope and given facts

In scope:
- A jingle for a podcast intro.
- A total duration of exactly 10 seconds.
- The musical structure and production direction needed to create it.
- A memorable opening identity for “[FILL IN: podcast name or spoken identifier].”

The user has not supplied the podcast name, genre, mood, BPM, key, instrumentation, vocal description, lyric requirement, transition style, or intended production tool. Leave each unconfirmed item as a slot rather than selecting a plausible value. Fill “[FILL IN: podcast name or spoken identifier]” with the exact name or spoken identifier supplied by the user. Fill “[FILL IN: desired genre, mood, BPM, key, and instrumentation]” with the requested musical brief. Fill “[FILL IN: whether lyrics, a sung hook, or instrumental music is required]” with the user’s choice. If no choice is supplied, present clearly labelled alternatives instead of treating one as confirmed.

Do not expand this into a full-length song, a podcast episode script, an advertising claim, or unrelated brand strategy.

## Working rules

Use the following confirmed constraint as non-negotiable: the complete jingle lasts exactly 10 seconds. Allocate time across intro, verse, chorus, bridge, and outro only when those sections can fit naturally within that duration. If a conventional verse or bridge would make the arrangement crowded, omit it and state that the 10-second format calls for a compact hook-led structure.

Set genre, BPM, key, and instrumentation to confirmed values only. If they are absent, use “[FILL IN: desired genre, mood, BPM, key, and instrumentation]” and provide a neutral production direction without presenting an invented choice as fact. If the user later supplies a fixed vocal description, keep its timbre, register, and delivery unchanged throughout. If no vocal description is supplied, branch explicitly:
1. If lyrics or a sung hook is required, write an original, short English line and constrain it to the available syllable count and stress pattern.
2. If instrumental music is required, replace lyric instructions with a melodic hook and any spoken-name cue requested.
3. If the requirement is unclear, provide both options and label the unresolved choice.

Write original material only. Do not reproduce an existing melody or lyric, imitate a living artist as the target voice, or use a living artist’s name as a style instruction. If a rhyme scheme is requested, state it and apply it; otherwise, do not force a rhyme scheme into a 10-second cue. Every timing decision must add up to exactly 10 seconds. Keep the final sound suitable for an intro: a recognisable hook, intelligible identification, and a clean ending or speech-ready tail.

No United States jurisdiction-specific rule is supplied for this music request. Do not invent licensing facts, ownership, or clearance status. If the production uses external music, samples, voices, or lyrics, mark the relevant permission as “[FILL IN: applicable licence or clearance status].”

## Output structure

Produce the result in this order:

1. **Song structure and timing** — Use the required section labels: intro, verse, chorus, bridge, and outro. For each section used, give its start time, end time, duration, and musical direction. The total must equal exactly 10 seconds. If a listed section is omitted, write “Not used” and explain briefly why it does not fit the intro format.
2. **Core musical parameters** — State genre, mood, BPM, key, instrumentation, vocal approach, and transition or ending treatment. Use confirmed values or “[FILL IN: item]” slots.
3. **Hook or lyrics** — If lyrics are required, provide only original words suited to the stated syllable count and stress pattern. If instrumental, describe the melodic or rhythmic hook instead. Identify where the podcast name or spoken identifier appears.
4. **Production direction** — Describe entrance, arrangement density, vocal intelligibility, sound-design accents, mix priority, and the final handoff into speech. Keep these directions specific to a 10-second podcast intro.
5. **Unresolved inputs** — List only the missing choices that must be supplied before production, including the relevant fill-in slots.

## Style rules

Use a hybrid style. Present timings, parameters, section allocations, and unresolved inputs in itemized form. Write the creative direction and rationale in short narrative paragraphs. Use a concise, production-ready register: vivid enough to guide composition, but not ornate. Avoid generic phrases such as “take listeners on a journey,” “sonic landscape,” and “something truly special.” Do not use promotional claims about the podcast unless the user supplies them.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the deliverable is a podcast intro jingle, not a full song, episode script, or marketing copy.
2. Add every section’s duration and verify that the total is exactly 10 seconds.
3. Check that the podcast identifier appears only if supplied; otherwise retain “[FILL IN: podcast name or spoken identifier].”
4. Check that genre, mood, BPM, key, instrumentation, vocal description, and lyric requirement are either confirmed by the input or left as explicit slots.
5. Check that any lyrics are original and fit the stated English syllable and stress constraints.
6. Check that no living artist is named as a target voice and no existing melody or lyric is reproduced.
7. Check that the requested song-structure components—intro, verse, chorus, bridge, and outro—are addressed without forcing unsuitable sections into the 10-second format.
8. Check that the ending specifies either a clean stop, a short tail, or a transition into speech, without inventing an unconfirmed production requirement.
9. Check that no facts, names, musical settings, licensing status, or creative brief details were added beyond the user’s input.
10. Check that no “[FILL IN: …]” slot was filled arbitrarily, especially the podcast name, musical parameters, and vocal or lyric choice.
11. Check that the response stays within the requested scope and does not drift into episode content, advertising claims, or unrelated branding.
12. Check that the final output follows the required order and that itemized and narrative portions respect the stated hybrid style.