> ## Documentation Index
> Fetch the complete documentation index at: https://hyperlocalise.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Local generation workflow

> Run draft generation safely and make lock-file behavior predictable.

## Recommended loop

1. `hyperlocalise run --dry-run`
2. inspect task list and counts
3. `hyperlocalise run`
4. review failures and rerun if needed

## Lock-file behavior

`.hyperlocalise.lock.json` tracks completed tasks to avoid repeated work.

When you change source content or config mappings, re-run and verify whether new tasks are planned.

Use [Lockfile contract](/reference/lockfile-contract) for schema details and reset guidance.

## Good practice

* keep dry-run in CI for visibility
* use deterministic file mappings
* avoid manual edits to lock state

## Markdown in local workflows

If your bucket mappings point to `.md` or `.mdx` files, `hyperlocalise run --dry-run` still plans tasks from Markdown sources.

When you run without `--dry-run`, output keeps Markdown and MDX layout stable while translating extracted prose nodes.