{ "format": "driftproof-answers/2", "receipt_hash": "ceb928044061eeaec1f43472344257829307fb4785f57a754ca5a7c1937d35f1", "model_id": "claude-opus-5-5", "answers": { "8600118b8821c087f0808ec385cf897ded386a5df9fa9185f1f54d2c9ec85362": "The candidate has cleared license and duration, but it still needs a fit check. A chime that is legal and the right length can still be wrong for the cue. Here is the workflow:\n\n**1. List reusable candidates first**\n\n```bash\nnpx hyperframes media-use resolve --type sfx --intent \"short chime\" --project --candidates\n```\n\nThis shows the local candidate, plus any others, without resolving anything new. The judgment step is yours, not the tool's.\n\n**2. Judge fit against the actual cue**\n\nCheck the candidate against what the moment needs:\n- **Character:** bright or soft, musical or UI-like, and whether it matches the piece's tone and any music bed.\n- **Envelope:** a quick attack that lands on the visual beat, and a tail that doesn't spill into the next scene or voiceover.\n- **Level:** it shouldn't clip or bury dialogue.\n- **Placement:** it should line up with the cut, reveal, or text entrance it accents.\n\n**3a. If it fits, adopt it**\n\nAdopting it into the project freezes it as a local file and writes a ledger record. That makes the reuse traceable and reproducible, with no fresh search.\n\n**3b. If it doesn't fit, resolve fresh**\n\n```bash\nnpx hyperframes media-use resolve --type sfx --intent \"short bright notification chime, quick decay\" --project \n```\n\n- The result is one line, `resolved → (sfx, …)`, plus a ledger entry.\n- The bundled 19-file sfx library always answers.\n- The wider catalog needs either the signed-in `heygen` CLI or `HEYGEN_API_BASE` set by a host app.\n- If the host app provides its own sound-effect tools, use those instead.\n\n**4. Verify in context**\n\nPreview the chime at its timestamp in the composition before calling it done.\n\n**Caveat:** the exact reuse rules and adopt/ingest flags are in `references/resolve.md`, which I haven't read in this session. Check that file before running the adopt step.", "13a142f6a09e882368065955907c228aeac5eaa6887072996c2d8c8b8ff72b49": "# Next step for the chime: check fit before reusing or resolving fresh\n\nLicense and duration are only eligibility checks. The open question is whether this chime actually suits the moment it's for. So the next step is to judge fit, not to resolve something new.\n\n## 1. List reusable candidates\n\n```bash\nnpx hyperframes media-use resolve --type sfx --intent \"short chime\" --candidates --project \n```\n\nThis shows the existing local candidate next to any other reusable ones. You can then compare them before fetching anything new.\n\n## 2. Judge fit yourself\n\nThe tool doesn't decide this. You do, against the actual use:\n\n- **Character:** Is the tone right? For example, bright and clean versus warm and soft, or playful versus corporate.\n- **Shape:** Does it start crisply enough to land on the cue? Does the tail ring past the beat or clash with the next sound?\n- **Context:** Does it sit well with any music or voiceover? Watch for loudness, frequency clashes, and key or pitch against the bed.\n- **Consistency:** Does it match the other sound effects already in the piece?\n\n## 3. Branch on the result\n\n- **It fits:** Adopt it into the project. That freezes it as a local file and records it in the ledger, which gives you full provenance without a new search.\n- **It doesn't fit:** Resolve a fresh one with a sharper intent that names what was wrong. For example: `--type sfx --intent \"soft single-note chime, short tail, warm\"`. The `sfx` type answers from the bundled 19-file library even without the `heygen` CLI, and searches the HeyGen catalog when the CLI is available. If the host app has its own sound-effect tools, use those instead.\n\n## 4. Confirm in place\n\nWhichever file you pick, preview it at its cue in the composition before treating the job as done.\n\nThe exact adopt syntax and reuse rules are in `references/resolve.md`. I haven't read that file here, so check it for the precise adopt command rather than relying on my wording.", "f49694424ac81095447d2c1407a95ecfcd6f7647fdf2df55270e445da10feefd": "# Next steps for the chime\n\nThe candidate passes on license and duration, but those only make it eligible. Media-use requires you to **judge fit yourself** before reusing anything. So the next step is a fit check, not a fresh resolve.\n\n## 1. Check the existing candidate's fit\n\nList the reusable candidates for this intent:\n\n```bash\nnpx hyperframes media-use resolve --type sfx --intent \"short chime\" --project --candidates\n```\n\nThen judge the local candidate against what the project actually needs:\n\n- **Character:** Is it actually a chime (bright, bell-like, tonal)? Or is it a ding, whoosh or click that only matches loosely?\n- **Context:** Does it suit the composition's tone (playful, corporate, calm) and its moment (notification, reveal, transition)?\n- **Technical cleanliness:** Does it start cleanly, with no clipping, and does its tail fit the edit?\n- **Mix fit:** Will it sit well against any voiceover or background music, or clash with them?\n\n## 2. Branch on the result\n\n**If it fits:** reuse or adopt it rather than resolving something new. That records it in the project's ledger as a frozen local file. The exact adopt and reuse rules and flags are in `references/resolve.md`. I'd read that before running the command; I haven't seen it here, so I won't guess the flag names.\n\n**If it doesn't fit:** resolve fresh.\n\n```bash\nnpx hyperframes media-use resolve --type sfx --intent \"short bright chime, \" --project \n```\n\n- `sfx` still answers from the **bundled 19-file library** even without the `heygen` CLI.\n- The wider catalog search needs the `heygen` CLI. The exception is when `HEYGEN_API_BASE` is set, in which case the host handles it with no sign-in.\n- If the host app provides its own sound-effect tools, use those instead of `resolve --type sfx`.\n\n## 3. Output\n\nEither path ends with one line, `resolved → (sfx, )`. That gives you a frozen local file and a ledger record, so the chime can be reused later in this project and in others.", "cb417da1fc2411c7e34588ccb13fa6a4ecf80f7f83b0ace5d673cbce08bad9ec": "# Workflow for the chime\n\nThe candidate's license and duration are already fine, so the only open question is **fit**. Check fit before you reuse it or search for something new.\n\n**1. Surface it as a reuse candidate.**\nList existing assets first instead of resolving fresh:\n\n```bash\nnpx hyperframes media-use resolve --type sfx --intent \"short chime\" --project --candidates\n```\n\nThe candidate list leaves the fit judgment to you. The tool won't decide it.\n\n**2. Judge fit against the actual moment in the composition.**\n- **Character:** Is the tone right for the piece, e.g. bright, soft, playful, or corporate?\n- **Envelope:** Is the attack crisp, and does the tail decay cleanly without running into the next beat?\n- **Level and mix:** Does it sit under or with any voiceover or BGM without clashing in pitch or key?\n- **Sync:** Does its onset line up with the visual hit it marks?\n\n**3a. If it fits: adopt it.**\nAdopting freezes the file into the project and writes a ledger record. The asset is then pinned and traceable, and other projects can reuse it later. The exact adopt and reuse flags are documented in `references/resolve.md`, which I haven't read here, so check that file for the syntax.\n\n**3b. If it doesn't fit: resolve fresh.**\n- If the host app provides its own sound-effect tools, use those.\n- Otherwise, run `resolve --type sfx --intent \"short soft chime, quick decay\"`. Make the intent specific about what the candidate got wrong.\n- `sfx` still answers from the bundled 19-file library even without the `heygen` CLI. Searching the larger catalog needs the CLI, unless `HEYGEN_API_BASE` is set, in which case the host handles it with no sign-in.\n- The command returns one line, `resolved → (sfx, …)`, and the result is recorded in the ledger the same way.\n\n**4. Wire it in and verify.**\nPlace it at the transition or hit point, then preview it in context to confirm timing and level.\n\nThe key rule is that license and duration only make a file eligible. A deliberate fit check against the real composition decides whether you adopt it or resolve a new one.", "a7b411510799f088ea906ec90816ea0777cccc2796eea5d1c4b2a81956e71b73": "# Next step: judge fit, then adopt or resolve fresh\n\nThe candidate has passed license and duration, but those are only eligibility checks. Reuse depends on whether it actually suits this project, so fit comes next.\n\n## 1. Judge fit yourself\n\nThe workflow is: list reusable candidates with `--candidates`, then judge fit before resolving anything new.\n\n```bash\nnpx hyperframes media-use resolve --type sfx --intent \"short chime\" --project --candidates\n```\n\nCheck the candidate against the project's intent:\n- **Character:** Does the timbre and mood match the piece (bright, soft, playful, corporate)?\n- **Shape:** Does it have a clean attack and a tail that ends where the cue needs to resolve, without clipping into the next beat?\n- **Placement:** Does it land well on the moment it accompanies, such as a transition, reveal, or notification beat?\n- **Mix:** Does its loudness and frequency range sit well with any music bed or voiceover?\n\n## 2. Branch on the result\n\n**If it fits, adopt it.** Bring the local file into the project as a frozen local asset with a ledger record. Use ingest with `--from` or the adopt flow. This avoids another search and keeps reuse traceable.\n\n**If it doesn't fit, resolve fresh:**\n```bash\nnpx hyperframes media-use resolve --type sfx --intent \"short bright chime, quick decay\" --project \n```\n- If the host app provides its own sound-effect tools, use those first.\n- Without `HEYGEN_API_BASE` or the `heygen` CLI, `sfx` still answers from the bundled 19-file library, but catalog search fails and says so.\n- Either way, the result is one line, `resolved → (sfx, …)`, with the search details kept on disk.\n\n## 3. Then place and verify\n\nPut the chime on its cue in the composition and check it in context. Once it is a frozen ledger asset, it can be reused across projects later.\n\n**Caveat:** The exact adopt syntax, reuse rules, and full flag list are in `references/resolve.md`. I haven't read that file here, so confirm the precise adopt or `--from` invocation there before running it.", "112ea8ec16403b7e1dbe1227b43a11b110b7e00651574094bbe14eddf575b7a3": "The candidate has cleared licensing and duration. The open question is fit, so the next step is to evaluate that before adopting the file or searching for another one.\n\n**1. Audition it in context**\n- Play the chime where it will actually fire, such as a notification, success state, or UI event, alongside the project's existing sounds.\n- Check tone and timbre against the project's sonic identity. Is it playful or neutral? Synthetic or organic?\n- Check perceived loudness relative to other assets. Matching file duration doesn't mean matching loudness.\n- Listen on the target playback devices, like laptop speakers, phone speakers, and headphones. Chimes often sound harsh or thin on small speakers.\n\n**2. Check technical fit**\n- Confirm the format, sample rate, bit depth, and channel count match what the project expects. For example, mono may be required for UI sounds.\n- Look for clean edges: no clicks at the start or end, minimal leading silence so it feels responsive, and a natural decay rather than a hard cut.\n- Make sure it doesn't clash with or mask other sounds that might play at the same time.\n\n**3. Decide**\n- **Fits:** adopt it.\n- **Close but not right:** make light edits if the license allows modification. Trimming silence, adding fades, normalizing loudness, or applying gentle EQ are typical. Re-audition after editing.\n- **Doesn't fit:** reject it and source another candidate. Apply the same filters in order: license first, then duration, then fit.\n\n**4. Integrate and record**\n- Name and place the file according to project conventions.\n- Record provenance next to it, in an asset manifest or credits file. Include the source, license, any attribution required, and any modifications you made. This keeps the license check auditable later.\n- Wire it in and verify it triggers correctly in the build. Doing this in the real build matters because it catches issues like gaps caused by decoding latency.\n\n**5. Get sign-off**\n- If someone owns the project's audio or UX, have them approve the final pick. Fit is partly subjective, so a second listen is worth it before you commit.\n\nIn short: audition in context, check technical fit, then adopt, edit, or replace. Document provenance, integrate, and get sign-off.", "e789b1605bbc9a8ae30ba70fe645a859c3ede8b281da5eda1096697f9ba5aaae": "The license and duration checks are done, so the remaining question is whether the chime actually fits the project. That is the next gate, and nothing should be integrated until it passes.\n\n## 1. Define what \"fit\" means\nWrite down the acceptance criteria before you listen, so the review isn't purely subjective:\n- **Purpose:** what event the chime signals (success, notification, startup) and the emotional tone it should carry.\n- **Context:** where it plays (UI, game, video) and alongside what other audio.\n- **Technical targets:** format, sample rate, bit depth, channels, and loudness relative to the project's other sounds.\n\n## 2. Check fit\n- **Audition in context.** Play it at the actual trigger point or against a mock of it, not in isolation. Compare it with neighboring sounds for tone, pitch, and timbre.\n- **Technical inspection.** Confirm the format and specs match the targets. Check for clipping, noise, clicks at the start or end, and leading or trailing silence. Make sure the tail decays cleanly within the duration you already approved.\n- **Edge cases.** Test repeated or rapid triggering, low or high volume settings, and small speakers or headphones if those apply.\n\n## 3. Decide\n- **Pass:** proceed to integration.\n- **Minor issues** (level, trim, fade): make light edits, but first confirm the license permits modification. Some licenses forbid derivatives or require noting changes. Keep the original file untouched.\n- **Fail:** record why, and return to sourcing using the same order of checks: license, then duration, then fit.\n\n## 4. Integrate\n- Add the file, or the edited version, using the project's naming and directory conventions.\n- Wire it into the trigger point and verify it plays correctly in the real build or environment.\n\n## 5. Record provenance\nKeep a short asset record with:\n- source and original filename\n- license, plus any attribution text required\n- any edits made\n- date and who approved it\n\nSatisfy any attribution requirement in the project's credits or notices file.\n\n## 6. Final sign-off\nHave whoever owns the audio or UX experience confirm the chime in context. After that, mark the asset as approved.\n\n**In short:** the asset is legally and technically eligible but not yet accepted. Run a fit review against written criteria and decide whether to accept, edit, or reject. Then integrate it, record where it came from, and get sign-off.", "1feb24cd7846006864b806ec3954dcfae49fea09864e540f44bf83117d3204cd": "The candidate has cleared two of the three gates, license and duration. Fit is the one still open, so it decides what happens next.\n\n**1. Check fit (the open gate)**\n- **Audition in context.** Play it where it will actually fire, next to the project's other sounds and any background audio. A chime that sounds fine on its own can clash in place.\n- **Check tone and character.** Does it match the project's style (playful, neutral or alert-like)? Does it feel right for the event it signals, such as success, notification or error?\n- **Check technical fit.** Look at format, sample rate, channels and loudness compared with existing assets. Listen for clipping, leading or trailing silence, clicks at the start or end, and how it sounds through small speakers or at low volume.\n- **Check repetition.** If users will hear it often, play it many times in a row. Short chimes that grate on repeat are a common failure.\n\n**2. Decide**\n- **Fits:** move on to integration.\n- **Fits with minor issues** (trim, fade, loudness normalization): make the edits, keeping the original. Then re-confirm that the license allows modification and that the edited duration still meets the requirement.\n- **Doesn't fit:** reject it, note why, and go back to sourcing. Reuse the same license and duration filters, plus whatever the fit check taught you.\n\n**3. Integrate**\n- Convert to the project's standard format and naming convention, then place it in the expected asset location.\n- Wire it to the triggering event and test it in the real build or flow.\n\n**4. Record provenance**\n- Write down the source, author, license (with a link or a copy of the text), any attribution requirement, and the edits you made.\n- Add attribution to the project's credits or notices file if the license requires it.\n\n**5. Final verification**\n- Get a quick listen from whoever owns the project's sound or UX, if that's someone other than you.\n- Commit the asset and its provenance notes together, so the license record travels with the file.\n\nIn short: audition it in context next. Integration and commit only happen after it passes, and any edits mean re-checking license and duration.", "03ec20f1b92d91d74b7ce7a05369c49c81537b5d207b14160f10fa909596a607": "The candidate has cleared two of the three gates: license and duration are confirmed, but fit isn't. Don't commit it yet. Treat it as a provisional pick and run a fit check before anything references it.\n\n## 1. Define \"fit\" for this chime\nWrite down the criteria first so the check isn't just a gut call:\n- **Purpose:** notification, success, error, UI feedback, or brand sting. Each implies a different tone.\n- **Tonal match:** pitch, timbre (bell, synth, marimba) and mood that suit the project's existing sound palette or visual style.\n- **Technical specs:** format, sample rate, bit depth, mono or stereo, and the target loudness the project uses.\n- **Clean edges:** no clicks, tails cut cleanly, minimal silence at the start so playback feels instant.\n- **Repetition tolerance:** if it plays often, it shouldn't grate on the tenth hearing.\n\n## 2. Check the candidate against those criteria\n- Listen in context: play it where it will actually fire, on the speakers or headphones users will likely have.\n- Compare it to adjacent sounds in the project for loudness and character.\n- Check the technical properties (format, levels, leading silence) against the spec.\n- If possible, get one other person to hear it.\n\n## 3. Decide\n- **Fits:** go to step 4.\n- **Fits with minor tweaks** (trim, fade, normalize, convert): make the edits on a copy, keep the original untouched, and confirm the license allows modification. Then go to step 4.\n- **Doesn't fit:** record why (for example \"too bright\" or \"tail too long\") and use that to narrow the search for the next candidate. Its license and duration passing doesn't earn it a spot.\n\n## 4. Integrate and record provenance\n- Add the final file under the project's asset conventions (naming, directory).\n- Record the source, license, attribution text if required, any modifications, and the date. Put this in a credits or asset manifest file next to the asset.\n- Wire it up and test it in the build. Then commit the asset and its provenance record together so the license trail travels with the file.\n\nThe key point is that fit is still unchecked, so the candidate stays provisional until step 2 is done. Until then, nothing should depend on it.", "4a4bde0f3536decc57eb3b99f436642ab22ef29e4bb7aec402f2e43cee486725": "The candidate has cleared the two objective gates, license and duration, so the remaining step is the subjective one: **does it actually fit?** Don't integrate it until that's confirmed.\n\n## Next workflow\n\n**1. Define \"fit\" before listening**\nWrite down what the chime has to do, so the check isn't just gut feel:\n- **Purpose:** success, notification, error, or ambient cue\n- **Tone:** playful, neutral, premium, calm, urgent\n- **Context:** how often it plays, what plays alongside it (music, other SFX, voice), and what devices it plays on (phone speaker, headphones, desktop)\n\n**2. Audition in context, not in isolation**\n- Play it at the actual moment it fires in the product, or in a mock of that moment.\n- Listen next to the project's other sounds. Check that it matches in timbre, key or pitch range, and perceived loudness.\n- Test on the worst likely output device. Small speakers often lose low-end chimes completely.\n- Play it 10 or more times in a row. A chime that's pleasant once can become grating when repeated.\n\n**3. Check technical fit**\n- Clean start and end, with no clicks, leading silence, or abrupt cutoff in the tail\n- Loudness that's consistent with the other assets, or that can be normalized to the project's target\n- A format, sample rate, and channel count that meet the project's requirements, or can be converted without artifacts\n\n**4. Decide**\n- **Fits:** move to integration.\n- **Close:** make light edits (trim, fade, gain, EQ, pitch shift) and re-audition. Confirm the license permits modification first.\n- **Doesn't fit:** reject it, record why, and use that reason to narrow the search for the next candidate.\n\n**5. Integrate and record provenance**\n- Convert or normalize to project specs and add it under the project's asset naming convention.\n- Record the source, license, any attribution requirement, and edits made, wherever the project tracks assets (a manifest, credits file, or README).\n- Give credit in the UI or docs if the license requires it.\n\n**6. Get sign-off**\nIf someone else owns the product's sound or brand, have them hear it in context before it ships.\n\n**In short:** audition it in context, check the technical details, decide, integrate with provenance recorded, then get sign-off.", "d383f8f8525d7ef3524299f3ad0d4308d1b0714e9bacdc8b2baa2e5f9933a4a2": "# Logo Sourcing Plan\n\nI haven't run anything. This is the plan I'd follow once you approve it.\n\n## 1. Confirm the brand first\nI need the exact company name and, ideally, its official domain or GitHub org. Many brands share similar names, and a lookup on an ambiguous name can return the wrong company's mark.\n\n## 2. Check for reuse\nBefore fetching anything new, I'd list existing candidates:\n\n```bash\nnpx hyperframes media-use resolve --type logo --intent \" official logo\" --project --candidates\n```\n\nIf an earlier project already froze the official mark for this brand, I'd reuse it after checking it's the same company and a current version.\n\n## 3. Resolve through the official-mark cascade\n```bash\nnpx hyperframes media-use resolve --type logo --intent \" official logo\" --project \n```\n\nThe `logo` type tries sources in this order and stops at the first hit:\n\n1. **theSVG**: a curated library of official brand SVGs. This is the best result because it's a vector of the real mark.\n2. **GitHub avatar**: the company's official org avatar.\n3. **Favicon**: taken from the company's own domain. It's usually small and raster, so it suits small placements, not hero use.\n\nThe result is a frozen local file plus a ledger record, so the source of the mark can be traced. If you later supply an official file, I can ingest it with `--from ` and it will take precedence.\n\n## 4. Check the result\n- Confirm it's the right company, not a namesake.\n- Check that the resolution fits the intended size. A favicon scaled up to a full-screen title card will look bad.\n- If only a low-resolution fallback was found, tell you so rather than hiding it.\n\n## What I must not fabricate\n- **No redrawn or traced logo.** No hand-written SVG or CSS that imitates the mark. Logos are \"never redrawn.\"\n- **No AI-generated logo** presented as the company's mark.\n- **No guessed brand colors, fonts, or wordmark** standing in for the real logo.\n- **No edits to the official mark.** That means no recoloring, re-proportioning, cropping into a new shape, or adding effects that change its identity, unless the brand's own guidelines provide such a variant.\n- **No mark from an unverified third party** passed off as official.\n\n## If the cascade finds nothing usable\nI'd stop and tell you. Then I'd ask for the official file (SVG preferred, or a high-resolution transparent PNG) or a link to the company's press or brand kit. Until then, the composition gets a clearly labeled placeholder or plain-text company name, not an invented logo.", "e91802bdb6d58b3c59a48daada795e6295882fdb6308e67c9df56930d5cd2027": "# Logo sourcing plan\n\nNo official file has been supplied, so the logo has to come from a real published source. Nothing gets drawn, generated, or approximated.\n\n## 1. Confirm the identity first\nI need the **exact company name and its primary domain** (for example `acme.com`). Brand marks are easy to confuse: similar names, regional subsidiaries, and rebrands all cause mix-ups. If you have a preferred variant (full wordmark or symbol only, light or dark background), say so now.\n\n## 2. Check for reuse before fetching\nList existing candidates (`resolve --type logo --candidates`). If a frozen copy of this brand's mark is already in the ledger from an earlier project, I'll reuse it, as long as it's the right variant and still current.\n\n## 3. Resolve through the official-source cascade\n`npx hyperframes media-use resolve --type logo --intent \" logo\" --project ` tries these sources in order:\n\n1. **theSVG**: a curated vector brand mark. This is the preferred result because it's scalable and clean.\n2. **GitHub organization avatar**: the company's own published image, usually square and raster.\n3. **Site favicon**: taken from the company's domain. This is the last resort and is often low-resolution.\n\nThe result is frozen into a local file with a ledger record that notes where it came from. If it falls back to the avatar or favicon, I'll tell you, because those may be too small or too square for hero placement.\n\n## 4. Verify before placing\n- Check that it really is this company's mark and the current version, not a pre-rebrand one.\n- Check transparency, aspect ratio, and whether the resolution holds up at the size it will be displayed.\n- Check contrast against the composition background. If it's poor, choose an official alternate variant rather than altering the mark.\n\n## 5. If the cascade misses\nI'll stop and ask you for an official asset, such as a press or brand kit, an SVG from the company's site, or a file from their design team. I won't fill the gap myself.\n\n## What not to fabricate\n- **No redrawing or tracing.** I won't hand-build an SVG or recreate the mark in CSS.\n- **No AI-generated logos.** Image models can't produce a real trademark faithfully, and an approximation is a misrepresentation.\n- **No modifications.** That means no recoloring, recropping, restyling, adding effects, or re-typesetting the wordmark in a lookalike font.\n- **No guessed URLs or invented sources.** Provenance comes only from what the resolver actually returned.\n- **No placeholder passed off as the logo.** If something has to hold the slot temporarily, it will be clearly marked as a placeholder (for example, a labeled box), not styled text pretending to be the brand.\n- **No substitutes.** I won't use a similar-looking company's mark, a generic icon, or an outdated logo without telling you.\n\nTo start, send me the company name and domain.", "3c3d2613ffea2208a8193df4145749543f359e1612a2eaf5d9036c2fc1c2a282": "# Logo Sourcing Plan\n\nPer your constraints, I haven't run anything. This is the plan I'd follow once tools are allowed.\n\n## 0. Confirm the company first\nI don't know which company this is. Before resolving, I'd confirm the exact brand name and, ideally, its domain or GitHub org. A wrong match, like a similarly named company, is the most common way a logo ends up wrong.\n\n## 1. Check for reuse\nList assets the project or earlier projects already hold:\n\n```bash\nnpx hyperframes media-use resolve --type logo --intent \" official logo\" --project --candidates\n```\n\nI'd judge fit myself and reuse a candidate only if it is clearly the same brand's official mark.\n\n## 2. Resolve through the official-mark cascade\nIf nothing reusable fits:\n\n```bash\nnpx hyperframes media-use resolve --type logo --intent \" official logo\" --project \n```\n\nThe `logo` type only sources real brand marks, in this order:\n1. **theSVG**, a library of official vector brand marks (preferred, because vectors scale cleanly).\n2. **GitHub avatar** of the company's organization.\n3. **Favicon** from the company's own site, as a last resort. It is often small and may only be a glyph.\n\nThe result is a single line, `resolved → (logo, …)`. It is frozen to a local file and recorded in the ledger, so later projects can reuse it.\n\n## 3. If you have the file later\nIf you or the client provide the official asset (a brand kit or press page download), I'd ingest it with `--from` instead of using the cascade. A supplied file always takes priority.\n\n## 4. If the cascade misses or the result is poor\nI'd stop and tell you rather than improvise. If only a low-resolution favicon turns up, I'd flag it as a quality risk and ask for the brand kit.\n\n## What not to fabricate\n- **No redrawn or traced logos.** That includes no SVG paths or CSS shapes that imitate the mark (\"never redrawn\" is a hard rule for this type).\n- **No AI-generated logos.** Image models are for photos and backgrounds, not brand marks.\n- **No text in a lookalike font** presented as the logo.\n- **No edits to the official mark.** No recoloring, cropping out elements, stretching, or adding effects or treatments, unless the brand's own guidelines provide that variant (for example, an official monochrome version).\n- **No substitutes.** No similar-looking icon, generic emblem, or another company's mark used as a placeholder that might ship.\n- **No guessing the brand.** If the identity is ambiguous, I'd ask instead of picking the closest match.\n\nIf a placeholder is needed while you wait, it should be clearly labeled, such as a neutral box reading \"LOGO\", so it can't be mistaken for the real mark.", "b4e857452e3c6c5aed7e9b912334ed493728e23e8e35e56767f995489f528625": "## Logo Sourcing Plan\n\nNo official logo file has been supplied, and I don't know which company this is for. Here's how I'd handle it.\n\n### 1. Get the real asset from an authoritative source (in order of preference)\n1. **Ask the company directly.** Brand, marketing, or design owners usually keep a master file, ideally SVG plus PNG exports, and a brand guidelines PDF.\n2. **The company's official press or brand kit page.** Many companies publish one at `/press`, `/brand`, or `/media-kit`, along with usage rules.\n3. **Existing internal repos or design tools** such as Figma, a shared drive, or the DAM. These count only if you can confirm they hold the current, approved version.\n4. **Avoid third-party logo aggregator sites** unless you check them against an official source. They are often outdated, traced, or altered.\n\n### 2. Confirm before use\n- The **current version**, since logos get rebranded.\n- **Usage rights and guidelines**: clear space, minimum size, allowed color variants (full-color, mono, reversed), and backgrounds.\n- **File formats needed**: SVG for UI, PNG at 1x/2x/3x, favicon or ICO if relevant.\n- **Exact brand color values** from the guidelines. Don't sample them from a screenshot.\n\n### 3. Until the real file arrives, use a clearly marked placeholder\n- A neutral box or text label reading something like `LOGO PLACEHOLDER – replace with official asset`.\n- Keep the slot's size and aspect ratio flexible so the real logo drops in cleanly.\n- Track the swap as an open TODO or issue so it isn't forgotten before release.\n\n### What not to fabricate\n- **No invented or \"approximated\" logo.** That means no recreated wordmark, no guessed icon, and no AI-generated look-alike presented as the company's mark.\n- **No guessed brand colors, typefaces, or taglines** passed off as official.\n- **No tracing or redrawing** of a low-res logo found online and treating it as the master.\n- **No claims of approval or licensing** that haven't actually been confirmed.\n- **No file named something like `logo-official.svg`** unless it really came from the company.\n\nIf you tell me the company name and where the brand assets live, I can help you write the request to the brand team or set up the placeholder and asset structure.", "27d4cdf9468196aca1eaed41f1f61365a525fe6e6276985985e6b672b7c2ac10": "# Logo Sourcing Plan\n\nNo official logo file has been supplied, and the company hasn't been named, so there's nothing yet to verify against. Here's how I'd get a real asset into the project.\n\n## 1. Get the official asset from the owner (preferred)\n\nAsk the project owner or the company's brand/marketing contact for:\n- **The official logo files**: ideally SVG (vector), plus PNG at 1x/2x/3x, and light/dark or monochrome variants if they exist.\n- **Brand guidelines**: clear-space rules, minimum size, approved color values (hex/RGB/CMYK), allowed backgrounds, and prohibited modifications.\n- **Usage confirmation**: written confirmation that this project may use the mark, plus any required trademark notice or attribution.\n\n## 2. If the owner points to a public source\n\n- Use the company's **official press kit or brand page** on its own verified domain.\n- Record the exact source URL, retrieval date, version, and license or usage terms alongside the file, e.g. in `assets/brand/SOURCE.md`.\n- Don't use third-party logo aggregators, search-engine image results, Wikipedia/Wikimedia copies, or screenshots. They are often outdated, recolored, low-resolution, or carry different licensing.\n\n## 3. Until the real asset arrives\n\n- Use a **clearly labeled placeholder**, such as a neutral gray box reading \"LOGO PLACEHOLDER\", or the company name in plain system text.\n- Reference it through one path or config key (e.g. `assets/brand/logo.svg`) so swapping in the real file is a single change.\n- Track the gap as an open TODO or issue so it isn't shipped by accident.\n\n## What not to fabricate\n\n- **No invented or AI-generated logo** presented as the company's mark, even as a \"close approximation.\"\n- **No recreation or tracing** of a logo from memory, screenshots, or low-res images.\n- **No guessed brand colors, fonts, or taglines** passed off as official.\n- **No made-up source URLs, press-kit links, license terms, or trademark notices.**\n- **No claims of approval or authorization** that haven't actually been given.\n- **No edits to an official mark**, such as recoloring, stretching, cropping, or adding effects, unless the brand guidelines allow it.\n\n## What I need from you\n\n1. The company name and the official logo file(s), or a contact who can provide them.\n2. Any brand guidelines and confirmation of usage rights.\n3. Your preferred placeholder style in the meantime.", "e4132a8bbf2f6a99e8485fd59676b44a24a4bfaec2a25e974f3eff1aa564b047": "## Logo sourcing plan\n\n**Current state:** No official logo has been supplied, and I haven't been told which company this is. So there is nothing yet to place in the project.\n\n### Sourcing plan (in order of preference)\n\n1. **Ask the company directly.** Request the official asset from you or the brand owner (marketing, design, or legal). Ask for:\n - A vector master (SVG, or EPS/AI/PDF), plus PNG exports at 1x/2x/3x with transparent backgrounds\n - Variants: full-color, monochrome/reversed (light and dark backgrounds), and icon-only or wordmark-only if they exist\n - The brand guidelines: clear-space, minimum size, approved colors (hex/RGB), and prohibited uses\n2. **Use the official press or media kit.** If the company publishes a brand or press page, download from there. Record the URL and date retrieved.\n3. **Confirm usage rights.** Check that this project's use (internal tool, public site, partner listing) is allowed. A logo being publicly visible doesn't make it licensed for your use, and third-party logo sites often carry outdated or altered versions.\n4. **Use a placeholder until then.** Put in a clearly labeled neutral placeholder, such as a gray box reading \"LOGO PLACEHOLDER\" or the company name in plain text. Size it to the expected aspect ratio so the layout doesn't shift when the real asset arrives. Mark it with a TODO so it can't ship by accident.\n5. **Document provenance.** When the real file arrives, note its source, version or date, and license or approval in the repo (for example, next to the asset or in a brand README).\n\n### What not to fabricate\n\n- **No invented logo.** No drawn, AI-generated, or \"approximated\" mark presented as the company's logo.\n- **No recreation from memory or screenshots.** Don't trace or rebuild it from a low-res image and pass it off as official.\n- **No guessed brand details.** Don't make up colors, fonts, taglines, or the company name and its styling.\n- **No unverified downloads treated as official.** Don't pull a file from a random logo aggregator or image search and treat it as authoritative.\n- **No fake provenance.** Don't write metadata, filenames, or comments implying an asset is official or approved when it isn't.\n- **No unapproved changes.** Once you have the real logo, don't recolor, stretch, crop, or add effects beyond what the brand guidelines allow.\n\n### What I need from you\n- The company name, and whether you can provide the logo files or a contact who can\n- Where the logo will appear, so we know which formats and variants are required", "70ca1a86b038f9845b109a21853df218e570f6f8e38d25c71054babc59c473df": "## Logo sourcing plan\n\n**Current state:** No official logo file has been supplied, and the repo has no commits, so there's nothing in the project to draw from either.\n\n### How to get the real logo\n\n1. **Ask the owner first.** Request the official asset from whoever owns the brand (marketing, design, or the company contact). Ask specifically for:\n - Vector source (SVG, or AI/EPS/PDF) plus any raster exports (PNG at 1x/2x/3x)\n - Variants: full-color, monochrome, light-on-dark, icon/mark-only, wordmark\n - Brand guidelines: exact color values (hex/RGB/CMYK), clear-space and minimum-size rules, usage do's and don'ts\n2. **Confirm usage rights.** Make sure the project is allowed to use the mark, and in which contexts (internal tool, public site, app store, print).\n3. **Record provenance.** When it arrives, note in the repo (e.g. `assets/brand/README`) where it came from, who supplied it, the date, and the version.\n4. **Fallback if the company publishes a press/media kit.** Downloading from the company's own official brand page is acceptable, but someone should confirm it's current. Third-party logo aggregator sites, search-engine image results, and favicon scraping are not substitutes. They're often outdated, altered, or low resolution.\n\n### Until the real file arrives\n\n- Use an **obviously generic placeholder**: a neutral box or text reading \"LOGO\" or \"Company Logo – placeholder\", sized to the expected slot.\n- Keep it in one swappable location (a single asset path or component) so the real file can be dropped in without code changes.\n- Track it as an open item (TODO or issue) so it doesn't ship by accident.\n\n### What not to fabricate\n\n- **No invented logo.** Don't design, generate (including with AI image tools), or trace a mark meant to look like the company's.\n- **No recreating it from memory or descriptions.** Don't approximate the shape, typography, or layout.\n- **No guessed brand colors or fonts.** Don't pick \"close enough\" hex values or typefaces and present them as official.\n- **No fake asset metadata.** Don't create files named like official deliverables (e.g. `acme-official-logo.svg`) or write docs implying an approved logo exists.\n- **No invented brand guidelines.** Don't make up clear-space rules, taglines, or trademark symbols (™/®) unless the owner supplies them.\n- **No claims of approval.** Don't say the logo is final or approved until the owner has confirmed it.\n\nThe core principle is that a placeholder should look like a placeholder. Anything that could pass for the real brand creates legal and trust risk if it ships.", "14f4b956b519fd00877829f0903654db1251da178a02807586f7df1fe69d4c37": "# Logo Sourcing Plan\n\nNo official logo file has been supplied, so I won't create or approximate one. Here's how to get the real asset and what to do until it arrives.\n\n## Sourcing plan (in priority order)\n\n1. **Ask the company directly.** Request the official file from the brand owner, marketing team, or project stakeholder. Ask for:\n - Vector master (SVG, or AI/EPS/PDF)\n - Raster exports (PNG with transparent background, at 1x/2x/3x or ≥1024px)\n - Variants: full-color, monochrome, reversed (light-on-dark), icon/mark-only, wordmark-only\n - Brand guidelines: exact color values (HEX/RGB/CMYK), clear-space rules, minimum size, prohibited uses\n2. **Check official brand channels** if the company has them: a press kit, media/brand page, or published brand guidelines. These are company-sanctioned sources.\n3. **Confirm usage rights** in writing: who approved it, what contexts it may appear in, and any trademark attribution requirements.\n4. **Record provenance** in the repo: source, date received, approver, and the license or permission terms, stored alongside the asset (e.g., `assets/brand/README.md`).\n\n## Interim approach\n\n- Use a **clearly labeled placeholder**, such as a neutral gray box with the text \"LOGO PLACEHOLDER\", sized to the expected dimensions.\n- Make it easy to swap: reference the logo through a single path or constant, so the real file drops in without code changes.\n- Track the missing asset as an open item (an issue or TODO) so it isn't forgotten before release.\n\n## What not to fabricate\n\n- **No invented logo.** That means no hand-drawn SVG, AI-generated mark, or \"inspired by\" design presented as the company's logo.\n- **No recreation from memory or from a low-res screenshot**, even if it seems close. Traced or redrawn versions drift in shape, proportions, and color.\n- **No guessed brand colors or fonts.** Don't pick hex values or typefaces that \"look right.\" Use only values from official guidelines.\n- **No unofficial sources treated as authoritative.** Logo aggregator sites, search-engine image results, Wikipedia/Wikimedia uploads, and favicons scraped from the website may be outdated, altered, or unlicensed.\n- **No placeholder that could pass for the real thing.** A stylized wordmark in the company name could ship by accident. Keep placeholders obviously temporary.\n- **No assumed permissions.** Don't claim the logo is licensed or approved without confirmation.\n\nOnce the official files and guidelines arrive, they replace the placeholder, and provenance is documented with the asset.", "d1aa24aa2d6935d9e6f800c72164042d0da0167b2d8ff186f18a4bbb59909345": "## Logo sourcing plan\n\nNo official logo file has been supplied, so the logo has to be **obtained from an authoritative source**, not created or approximated.\n\n### 1. Ask the owner first (preferred)\n- Request the official asset from the company's brand, marketing, or design team, or from whoever owns the project relationship.\n- Ask for:\n - **Vector master**: SVG, or AI/EPS/PDF.\n - **Raster exports**: PNG with transparency at 1x/2x/3x.\n - **Variants**: full-color, monochrome, reversed/dark-background, and icon-only/wordmark.\n - **Brand guidelines**: clear space, minimum size, exact color values (HEX/RGB/CMYK/Pantone), approved typefaces, and prohibited uses.\n- Confirm the **usage rights** for this project in writing, especially if the project is public-facing or commercial.\n\n### 2. Official public sources (if the owner points you there or is unresponsive)\n- The company's own **press kit, media, or brand page**, downloaded from their domain.\n- Their official, verified repositories or package listings, if they publish assets there.\n- Record the source URL, download date, and any license or terms text alongside the file.\n\n### 3. Sources to avoid as the source of truth\n- Google Images results, logo aggregator sites, Wikipedia/Wikimedia uploads, scraped favicons, and screenshots.\n- These are often outdated, recolored, low-resolution, or carry unclear licensing.\n- At most, use them to recognize what the real logo looks like, never as the shipped asset.\n\n### 4. Until the real file arrives\n- Use a **clearly labeled placeholder**, such as a neutral box reading \"LOGO – pending official asset\" or the company name in plain system text.\n- Track the gap as an open item with an owner and due date so it isn't forgotten before release.\n\n### 5. Integration once received\n- Commit the vector master plus required exports into a dedicated assets directory.\n- Add a short README or provenance note covering the source, date, who provided it, and the license or permission.\n- Follow the brand guidelines for sizing, spacing, and color, and don't modify the mark.\n\n---\n\n## What not to fabricate\n\n- **The logo itself.** Don't recreate it from memory, trace it, generate it with AI, or approximate it with fonts and shapes.\n- **Brand colors.** Don't guess HEX or Pantone values or pull them from a compressed image and present them as official.\n- **Typography.** Don't claim a specific brand typeface without confirmation.\n- **Variants that don't exist.** Don't invent a monochrome, dark-mode, or icon-only version the company hasn't approved.\n- **Guidelines.** Don't invent clear-space rules, minimum sizes, or usage restrictions.\n- **Provenance or permission.** Don't state that an asset is \"official,\" \"approved,\" or \"licensed\" unless that has actually been confirmed.\n- **Placeholder realism.** Don't make the placeholder look like a plausible real logo, since it could be mistaken for the real thing and shipped.\n\nBottom line: request the official files and usage terms from the owner, use a clearly marked placeholder meanwhile, and document the provenance once the real asset is in hand.", "9d040494d3f1ffa2a357e7dc2eae9852125076cc943483af733792f5aa89f85b": "# Proposed workflow: ordinary exposure correction (no LUT)\n\nSince the frames are **uniformly** too dark and no LUT was supplied, this is a plain correction. It should stay a small, bounded adjustment, persisted as treatment JSON.\n\n## 1. Inspect the real media\n- Find the actual ``/`