# Example: Linear ticket to project context

> A Linear ticket can become a project-scoped decision memory.

## Source to memory

Source artifact: Linear issue AMB-184.

Source excerpt: Use WorkOS org membership as the access boundary for the new connections surface.

Ambience memory:

- Type: decision
- Title: Use WorkOS membership for connections access
- Body: The connections surface uses WorkOS org membership as its access boundary unless an admin access decision supersedes it.
- Scope: project
- Tags: linear, permissions

Controls:

- Source: Linear ticket remains the planning record.
- Scope: project scoped to avoid turning a product constraint into an org rule.
- Freshness: review when the admin model changes.

Future reuse:

- A coding agent retrieves the access decision before editing the route.
- A PM can inspect the source ticket when revisiting the connections roadmap.

## Why Ambience

- The ticket remains the source of record.
- Ambience stores the implementation constraint.
- Project scope prevents accidental org-wide generalization.

## Related

- [Linear connection](https://ambience.sh/connections/linear)
- [Company context from Linear](https://ambience.sh/company-context/from-linear)
