Example: GitHub PR to engineering memory.
Updated 2026-06-07 · Agent-readable markdown available
How pull request reasoning becomes source-linked engineering context for agents.
A merged PR tells you what changed. An Ambience memory tells future agents why it changed and what rule to preserve.
- 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.
Source to memory
Source artifact
GitHub PR #214
Public marketing route prefixes must be added to middleware and tests together so markdown discovery keeps working.
Update route tests with public marketing prefixes
When adding public marketing pages, update middleware allowlists and route tests in the same change so crawlers and markdown mirrors stay reachable.
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.
Source
GitHub PR: middleware public routes for new marketing pages were covered by route tests to prevent apex redirects from breaking discovery.
Memory
Convention: Public marketing route prefixes must be added to middleware and route tests together. Scope: project. Source: GitHub PR.