# Example: GitHub PR to engineering memory

> A merged PR tells you what changed. Ambience memory tells future agents why.

## Source to memory

Source artifact: GitHub PR #214.

Source excerpt: Public marketing route prefixes must be added to middleware and tests together so markdown discovery keeps working.

Ambience memory:

- Type: convention
- Title: Update route tests with public marketing prefixes
- Body: When adding public marketing pages, update middleware allowlists and route tests in the same change so crawlers and markdown mirrors stay reachable.
- Scope: team
- Tags: github, routing

Controls:

- Source: PR description and review comments attached.
- Audit: future route changes can cite the convention.
- Conflict: supersede only with a newer routing decision.

Future reuse:

- A future agent adds a route and checks middleware before build.
- The team avoids rediscovering the same localhost and public routing issue.

## Why Ambience

- PR descriptions and reviews often contain durable reasoning.
- Ambience captures the convention, failure, or decision.
- Future agents can retrieve it before touching the same code path.

## Related

- [GitHub connection](https://ambience.sh/connections/github)
- [Company context for Claude Code](https://ambience.sh/company-context/for-claude-code)