> For the complete documentation index, see [llms.txt](https://getsquish.gitbook.io/squish/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://getsquish.gitbook.io/squish/recipes/build-week-audio-navigation.md).

# Build Week: audio-guided candidate selection

The Build Week extension gives the local CLI and MCP server a second mechanical signal: a normalized audio-activity band aligned to the same absolute source timeline as the visual cells. It answers one question—**when might a closer look be useful?**—without claiming to understand the sound.

## What existed before the event

Squish already produced timestamped contact sheets and supported iterative `start`/`end` zooms. Those absolute timecodes and the overview → zoom loop are the foundation, not Build Week work.

## What Build Week added

* a clip-wide `clip_peak` audio-activity band on local CLI/MCP sheets;
* additive absolute-time `audio.samples[]` metadata;
* preservation of short and high-frequency activity;
* tests, documentation, and an audio-guided candidate-selection workflow.

This is energy, not meaning. There is no transcript, sound-event label, diarization, or emotion inference. The public release uses one reference scale across a complete source clip; it does not compare separate files on a shared scale.

## Two proof layers

**Narrative proof.** The public demo uses owner-authorized camera footage: 22 visually repetitive one-minute clips, an audio-guided candidate range, and a dense visual zoom that confirms a person briefly appearing at a doorway edge. The footage is private and is not distributed.

**Reproducible proof.** The public repository contains a generated 24-second fixture under `examples/audio-navigation/`. It stays visually static in an ordinary overview, contains a short audio transient, and briefly shows a pink marker just afterward.

```bash
git clone https://github.com/getsquish/squish.git
cd squish
./examples/audio-navigation/generate-sample.sh

npx -y @getsquish/squish@0.3.1 \
  examples/audio-navigation/sample.mp4 \
  --json \
  --out /tmp/squish-audio-overview

npx -y @getsquish/squish@0.3.1 \
  examples/audio-navigation/sample.mp4 \
  --density 6x6 \
  --start 11.5 \
  --end 13.5 \
  --json \
  --out /tmp/squish-audio-zoom
```

Read the overview first. Use the audio activity only to propose the `11.5–13.5s` neighborhood, then inspect the dense visual sheet to confirm when the marker appears. The index proposes; the zoomed images prove.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://getsquish.gitbook.io/squish/recipes/build-week-audio-navigation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.